Events

Bearer API key required

Lists only ready business events for one event schema. Results are ordered by occurredAt descending, then id descending. The time filter is inclusive from and exclusive to; defaults are the seven days before now. A range wider than 90 days is clamped with a warning. Uses cursor pagination: no offset and no totalCount. Pending, failed, and outcome_unknown acceptances are absent; use events.status to inspect them. Invalid times return 400 invalid_time_range; malformed cursors return 400 invalid_cursor. Events are read from the operational event store, not the analytics archive.

Bearer API key required

Durably accepts one business event and returns 202 with its immutable acceptance receipt. Missing AI auto-fill fields are prepared asynchronously; readinessAtAcceptance is pending or ready. An accepted event is visible to event lists and consumers only once ready. Supply a stable eventId and retry the same normalized payload and occurredAt to recover the original receipt with isDuplicate=true. Changed input under the same eventId returns 409 event_id_conflict; erased occurrences return 409 event_erased. Idempotency-Key is not used. The normalized event input is limited to 256 KiB. occurredAt must be within the previous 366 days or five minutes into the future. contactId and objectId are optional, mutually exclusive explicit subjects in this space. Event admission has separate rate, backlog, and receipt-storage limits in addition to the API write bucket.

Bearer API key required

Accepts 1–500 events of one schema. With onError=continue (default), each event commits independently; inspect every result, including failures, even on HTTP 200. Accepted items include their immutable receipt. Admission failures include retryAfterMilliseconds. With onError=abort, a validation or admission failure rolls back new acceptances in that transaction, marks earlier accepted results rolled_back, and returns HTTP 422 with data.results, data.summary, and data.failedIndex. Later items are not attempted. Existing receipts encountered as duplicates remain existing occurrences. A 422 abort response is a business-result data envelope, not the standard error envelope. Each item uses eventId deduplication; Idempotency-Key is not used. Individual events retain the 256 KiB and occurredAt limits, and the whole HTTP body remains limited to 10 MB.

Bearer API key required

Read the current readiness of an accepted event by its maxclicks event id, including pending, ready, failed, and outcome_unknown states. This is distinct from the immutable readinessAtAcceptance returned when firing or retrying the event. data contains raw acceptance values until preparation is ready. A missing event or event schema returns 404. Acceptance and readiness do not prove that a downstream workflow, webhook, or email completed.

Bearer API key required

Binds or unbinds an anonymous browser identity to a contact using a server-held API key with write permission. An enabled contact track definition must match sourceId and subjectSchemaId in the space. Send contactId=null to remove the binding. All six body fields are required and unknown fields are rejected. Use a UUID operationId for replay of the same input; a changed body under that operationId returns 409. expectedAliasRevision is the last revision of this specific alias as a decimal string, or "0" for a new alias. Keep the returned identityRevision for the next change to that alias. Revision conflicts and erased aliases return 409; an unavailable source returns 403. Capacity is bounded at 100,000 aliases and 1,000,000 changes per space; exhausted capacity returns 429 without promising automatic recovery. Idempotency-Key is not used.