blastVersioning and compatibility
Use https://www.blast.fun/api/v1 for new integrations. The major version in the URL selects the API contract. The OpenAPI document’s info.version describes that contract’s release; the openapi field describes the specification format. Neither field selects a version for an HTTP request.
Open the v1 reference · Download the v1 OpenAPI document
What stays compatible in v1
Section titled “What stays compatible in v1”Existing routes, required fields, field types, units, nullability, documented enum values, parameter meanings, default ordering, pagination behavior, HTTP statuses, and error codes remain compatible. IDs and base-unit amounts remain strings where documented; do not convert them to JavaScript numbers.
We can add new endpoints and optional response fields within v1. Clients should ignore unknown response fields. Changes to an existing field’s meaning or type, new required request parameters, removal of fields or routes, or incompatible enum changes require a new major version.
Bug fixes and data updates do not create a new API version. Rate limits and operational availability are documented separately; honor Retry-After and handle unavailable data explicitly.
A future v2
Section titled “A future v2”Breaking changes will use /api/v2/..., with separate documentation and migration guidance. V1 will continue to run during an announced migration period. There is no scheduled v1 retirement. We will publish any deprecation date, replacement endpoint, migration instructions, and retirement date before requiring partners to move.
Keys and partner quotas are not tied to a URL version. Using different versions or rotating keys does not grant extra quota. Revoking a key invalidates it across all supported partner URLs immediately after revocation completes.
Keep a pagination cursor within the endpoint, version, filters, and sort that produced it. Treat cursors as opaque; do not move them between versions or construct them yourself.
Existing integrations and Blast’s frontend
Section titled “Existing integrations and Blast’s frontend”The existing partner endpoints under /api/social/... and /api/launchpad/... continue working with their current request and response formats. They have not been removed or redirected. Blast’s frontend continues using these URLs and its existing authentication and visibility rules.
For new partner integrations, use v1. To migrate an existing partner integration, change only the path prefix according to this table; keys, query parameters and response bodies remain the same:
| Existing URL | V1 URL |
|---|---|
/api/social/presales and its documented subpaths |
/api/v1/presales and the same subpaths |
/api/social/prices |
/api/v1/prices |
/api/launchpad/discovery |
/api/v1/discovery |
/api/launchpad/search |
/api/v1/search |
/api/launchpad/market/... |
/api/v1/market/... |
V1 always requires X-Blast-Partner-Key, including when a browser has a Blast session. It never grants access to pages, account data, writes, or undocumented routes. The frontend can remain private while partners use v1.