get upcoming and previous orbital launch schedules via the launch library 2 api
domain: thespacedevs.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Call GET on the current version's /launch/upcoming/ path (per current thespacedevs.com/llapi docs) for future launches plus launches from the last 24 hours.
Use query params such as search (matches launch name, rocket, agency, or mission name), lsp_id/lsp_name (launch service provider), or launcher_config__id to filter results.
Choose mode=list|detailed to control response verbosity, and use limit/offset for pagination.
Note that a launch stays in the 'upcoming' endpoint for 24 hours after its window so outcome/result fields can be filled in without a second call.
For historical launches beyond that window, use the equivalent /launch/previous/ endpoint.
Known gotchas
TheSpaceDevs offers a free public tier with throttling and a paid tier for higher volume — check current response headers/status codes for your actual limit rather than assuming a fixed quota, since limits have changed across API versions.
There are separate production (ll.thespacedevs.com) and development/staging (lldev.thespacedevs.com) hosts with different stability guarantees — don't point production workloads at the dev host.
API version numbers in the URL path are not fully interchangeable; field names and endpoints have shifted across versions, so pin to a specific version and watch for changes.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?