Batch and size limits
POST /v2/events accepts a batch inside three bounds:
- 1 to 500 events per request.
- A request body of at most 5 MiB.
- An individual event of at most 256 KiB.
request_too_large and gets split before it goes
back out.
Pagination
Event and issue list routes page through a cursor, using two parameters.
A response carries
next_cursor while more records remain. The cursor is opaque, so it
passes through your code untouched, never parsed and never constructed.
When Reconify is overloaded
A503 means durable ingestion or a public-data dependency is unavailable. It deserves a
retry with exponential backoff and jitter, bounded concurrency so recovery does not meet a
retry surge, and the same event IDs as the original request. The current contract promises
no 429 response and no Retry-After header, which is why the backoff lives in your
client. Errors covers the statuses that no retry can fix.