Booking API test

Test POST /api/bookings with plain-text entity names — either fill the form or paste a full request JSON. The API resolves names to Interpreter Intelligence IDs before creating the booking.

Connection

Enter entity names exactly as provided — no lookup autocomplete. Client and requestor names are required (customer name is recommended). Appendix field labels match the II UI names where possible.

Reference

Client, customer & consumer

Inline create (optional)

When an entity does not exist in II, fill the create fields below instead of relying on name matching. Validate uses dry-run — resolution shows "(would create)" without calling II create APIs.

Appointment details

Assignment & appendix

Notes

Enter an API key to submit.

Response

Submit a booking to see the API response here.