Match a conversation

Link an existing conversation to an appointment in your organization.

POST/custom/appointment/match

Authentication

x-api-key: YOUR_API_KEY

Base URL: https://api.apirilla.com

Body parameters

event_idstringrequired

The external ID of an existing calendar event in your organization.

conversation_idstring · uuidrequired

The Rilla conversation ID. Its recording will be linked to the event.

Matching replaces any previous appointment link for this conversation’s recording. Both records must already exist; this does not create an appointment.

Responses

200Success · text/plain.

403Missing or invalid API key.

400Invalid request parameters.

404Record not found or outside your key’s scope.

422Invalid linked record or organization.

Error reference

Common problems

400 · Invalid request

Send a JSON object containing event_id and conversation_id. Both records must already exist in your organization.

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.

Request example

curl --request POST \
  --url 'https://api.apirilla.com/custom/appointment/match' \
  --header 'x-api-key: YOUR_API_KEY' \
  --header 'Content-Type: application/json' \
  --data '{
  "event_id": "appt-1234",
  "conversation_id": "11111111-1111-4111-8111-111111111111"
}'

Example response · text/plain

Successfully matched conversation to event

Check your JSON before sending

Paste the JSON body only. This checker runs in your browser; nothing is uploaded.

Request body

← Delete an appointment Upload recordings