POST /events/scrape,
GET /events/platforms and GET /events/ping combined.
The limit is keyed on your authenticated identity, not on your IP address, so
several machines sharing one key share one budget. It is a token bucket: you can
send a burst of up to 30 requests at once, and capacity then refills at one request
every two seconds.
Exceeding it returns
429 with the gateway error envelope:
Retry-After or X-RateLimit-* headers are sent, so pace yourself with the
backoff below.
Rate-limited requests are not billed. The check runs after authentication and
before metering.
Endpoints without a rate limit are still bounded by your credits: paid Market Data
requests draw down your balance, and a runaway loop spends it. See
Credits & access.
For the WebSocket stream
The stream is not rate limited, but always reconnect with exponential backoff anyway. A tight reconnect loop gains nothing and hammers the service while it recovers. See Connecting to the stream.Handling a 429
- Wait before retrying. Start at one second and double on each consecutive
429, capping at 30 seconds. - Do not retry in a loop without a delay; each attempt counts.
- If you legitimately need more than 30 Live Availability requests per minute, contact Eventory. Higher limits are configured per account.
Timeouts
Live Availability scrapes can take up to 60 seconds and return408 when the
platform does not answer in time. Set your client timeout to 65 seconds for
POST /events/scrape. Every other endpoint normally answers in well under a second.