Events
Posting an event is what makes Raven send. Types come from the Subscription business pack and from your instance; GET /event-types is the truth for your instance.
POSTRecord an event
Requires events:write. Records the event and judges it: every rule that names the type answers in the same transaction. Send Idempotency-Key or event_ref so a retry records once.
- subject_id
- Forbidden
- group_id
- Forbidden
- date_field
- —
- dedupe_fields
- ref, status
201 with the event as stored, one fire per rule judged, and sends: how many messages that made. A type nobody defined is a 400 that lists the ones that are; a broken scope rule or payload is a 400 that names the field. Naming the subscription both ways is a 400, “Name the subject by subject_id or by subject_ref, not both.”, and a subject_ref nothing here holds is a 404. Everything after the reference is resolved is the same either way — the dedupe, the Idempotency-Key, the verdicts — and the event that comes back carries subject_id, so the answer tells you Raven's id.
One object: the same fields in every pack. Press Response on the sample to see one whole.
On failure the body is { error, code } instead.