ISS Location API (Open Notify) · Rate Limits

Iss Api Rate Limits

The Open Notify ISS API does not publish formal rate limit thresholds. The service is unauthenticated and free. No Retry-After, X-RateLimit-*, or RateLimit-Policy headers are documented. Best practice is to poll the location endpoint no more frequently than once every five seconds (the server-side refresh interval) and to cache responses client-side to reduce unnecessary load on the community-operated infrastructure.

Iss Api Rate Limits is the machine-readable rate-limit profile for ISS Location API (Open Notify) on the APIs.io network, in the API Commons Rate Limits shape.

It captures 2 rate-limit definitions, across the free tier, measuring requests_per_second and requests_per_minute.

Limit state is signalled in the limit, remaining, reset, and retryAfter response headers, and an exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled, quotaExceeded, and serviceUnavailable.

Tagged areas include Space, ISS, Public API, Open Source, and Rate Limiting.

2 Limits Exhausted: HTTP 429 limitremainingresetretryAfter
Method: generated, dated 2026-06-13.
Written by API Evangelist on 2026-06-13 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
SpaceISSPublic APIOpen SourceRate Limiting

Limits

ISS Location Polling Cadence ip
requests_per_second · second
1
The ISS position data updates approximately every five seconds on the server. Polling more frequently than once per second provides no additional precision and increases load on the shared service.
People in Space Polling Cadence ip
requests_per_minute · minute
12
Crew roster data changes rarely (crew rotations happen every few months). Polling more than a few times per hour is unnecessary for most use cases.

Policies

Fair Use
The service is community-operated and funded voluntarily. Callers should implement client-side caching, avoid tight polling loops, and be good citizens of a shared public resource.
Backoff Strategy
If the server returns a 429 or 503, implement exponential backoff before retrying. No Retry-After header is documented, so begin with a 5-second wait and double on each subsequent failure.
Caching
Cache ISS position responses for at least five seconds (the server refresh interval) and astronaut roster responses for at least one hour to minimize unnecessary traffic.

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/iss-api-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.