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.
POST /api/bookings
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.
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.
Must be unique in II. If this email already belongs to another requestor, create fails with 409 — use a different email/username.
Optional. If blank, II description is left empty; the street address is not copied into description.
Whether that gender is a requirement rather than a preference. The gender is set on the job either way; the answer is written into the interpreter notes as “Preferred Gender: Female - Mandatory”.
One per line, most preferred first. The API sets the first one II holds on the job and writes them all into the interpreter notes.
Whether the preferred interpreter has to be the one who attends. Either answer is written into the interpreter notes; Yes also keeps the job in the offer pool so nobody is assigned automatically.
One per line. All of them go to II Notes about Interpreter(s) and the job stays in the offer pool; each name that matches a contact also adds a consumer Manage Exclusion so they are not offered.
Enter an API key to submit.
Submit a booking to see the API response here.
