Events
Send behavioural events server-side. Use this when capture happens outside a SDK runtime — backend services, batch loaders, server-rendered web, or third-party webhooks you want to relay into Appice.
Endpoint
⚠ TODO — Engineering
Document the HTTP method and path of the events endpoint (e.g.
POST /v1/events). Include the full URL with the base.Request body
⚠ TODO — Engineering
Schema of the request body. Field-by-field: name, type, required, description, constraints. Use a JSON example. Cover: event name, user identifier, properties map, timestamp, idempotency key.
Response
⚠ TODO — Engineering
Schema of the success response. Include the status code, response body fields, and what 'accepted' vs 'enqueued' vs 'processed' means in the context of the decisioning pipeline.
Batching
⚠ TODO — Engineering
Document the batch endpoint (if separate). Include the maximum batch size, payload size limit, and recommended batching strategy for high-volume backends.
Idempotency
⚠ TODO — Engineering
Document how idempotency works for events. Is there an
Idempotency-Key header? How long are idempotency keys remembered? What happens on conflict?Errors
See Errors for the full status-code reference and error response format.