Update Appointment
Custom fields can be written as additional top-level properties using each custom field key. Values are validated against the field definitions returned by List Custom Fields.
Authorization
bearerAuth In: header
Path Parameters
Unique identifier for the resource.
uuidQuery Parameters
Dynamic detail fields to include. Use repeated query syntax: include_details=foo&include_details=bar.
items <= 10Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Human-readable name of the resource.
1 <= lengthRaw Description value for this resource.
Identifier assigned by an external system.
Status Key value for this resource.
1 <= lengthType Key value for this resource.
1 <= lengthUnique identifier of the related contact.
uuidStart Time value for this resource.
date-timeEnd Time value for this resource.
Timestamp for confirmed at.
Timestamp for cancelled at.
Calendar for the appointment. When omitted during appointment creation, the organisation default calendar is used.
uuidResponse Body
application/json
curl -X PATCH "https://api.getmateo.com/v1/appointments/497f6eca-6276-4993-bfeb-53cbbbba6f08" \ -H "Content-Type: application/json" \ -d '{ "property1": null, "property2": null }'{ "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "name": "string", "raw_description": "string", "external_id": "string", "status_key": "string", "type_key": "string", "contact_id": "f245e2a3-e141-4d41-912c-b1c1f5bd5598", "start_time": "2019-08-24T14:15:22Z", "end_time": "2019-08-24T14:15:22Z", "confirmed_at": "2019-08-24T14:15:22Z", "cancelled_at": "2019-08-24T14:15:22Z", "calendar_id": "c828ce68-4c5a-4491-b76a-af3d888d3f97", "created_at": "2019-08-24T14:15:22Z", "updated_at": "2019-08-24T14:15:22Z", "property1": null, "property2": null}Update Appointment By Locator PATCH
Custom fields can be written as additional top-level properties using each custom field `key`. Values are validated against the field definitions returned by List Custom Fields.
List Audit Logs GET
Lists audit logs for the API token organisation in descending occurred_at order. Every valid API token may read these logs, and entity permissions do not filter events. Queries for one subject require both subject_type and subject_id; all other queries require an RFC 3339 time range in occurred_at[gte] and occurred_at[lte]. Follow next_page_url until it is null and treat event IDs as stable deduplication keys.