Skip to main content
Use this checklist to confirm an integration is protocol-compliant before going live.

​
Envelope

  • Every event carries all required envelope fields (reference).
  • schema_version is "1.0".
  • eot is the occurrence time, with a timezone offset.
  • event_id is unique and stable across resends.

​
Delivery

  • Resends reuse the same event_id (idempotency).
  • Batches contain at most 500 events.
  • Preliminary detections use revision: 0; confirmations reuse the event_id with a higher revision.
  • eot reflects when the event happened, not when it was sent.

​
Responses

  • 202 is treated as success; accepted / duplicates are read from the body.
  • 400 and 401 are treated as permanent — the request is fixed, not blindly retried.
  • 429, 503, and 500 are retried with backoff; the 503 Retry-After is honored.
This is the engineering checklist. The full partner specification — batch-atomicity guarantees, retry rules by error class, endpoint provisioning, and the formal conformance suite — is shared during integration.