Create or update an appointment
Create an appointment or update one using the same event_id.
/custom/appointmentx-api-key: YOUR_API_KEYBase URL: https://api.apirilla.com
Body parameters
event_idstringrequiredStable appointment ID from your system. Send the same ID to update an existing appointment.
user_emailstringrequiredAppointment owner's email. Required even when attendee_emails is supplied; at least one supplied person must resolve in your organization.
attendee_emailsstring[]Optional additional reps, as non-empty email strings. A non-empty list resolves active, visible users in your organization; duplicates are combined and unresolved addresses are skipped. No resolved attendees returns 422. Cannot be combined with media_url (400).
start_timestringRequired on create. UTC date and time, for example 2026-09-20 14:00:00.
end_timestringRequired on create. UTC date and time.
titlestringA descriptive appointment title. Include it when creating an appointment.
customerobjectRequired on create. Include id and name; email, phone, and address are optional.
resultstringAppointment outcome from your CRM, such as won or lost.
pricenumberThe price quoted for the appointment.
custom_fieldsobjectAdditional CRM context. See the full reference for supported optional fields.
Every update replaces the attendees: re-send the full attendee_emails list, even for outcome-only or time-only changes. Omitting it or sending [] leaves only the resolved user_email; other omitted fields remain unchanged. Send appointments before reps record—adding attendees does not rematch existing recordings.
Responses
200Success · text/plain.403Missing or invalid API key.400Invalid request parameters.422Invalid linked record or organization.Common problems
400 · Invalid request
Send valid JSON and the required fields. For creates include event_id, user_email, start_time, end_time, title and customer. Use UTC times. A non-empty attendee_emails list cannot be combined with media_url.
403 · Forbidden
Use x-api-key: YOUR_API_KEY at api.apirilla.com. Do not use the Data Export host or Authorization header.
422 · Linked user or record not found
Read the response text. Check that the user, appointment and conversation belong to your key's organization. Keep the full attendee list on every appointment update.