Status and support
Availability
Section titled “Availability”- There is no contractual SLA for the API.
- There is no public status page for the API yet. When one exists it will be linked from this page.
- When the API cannot verify keys or limits it fails closed with
503andRetry-After: 5(see Limits and headers); treat a run of those as an incident on our side and retry after the interval.
Support
Section titled “Support”Support for the developer API goes through pump.fun’s support channel: open pump.fun, choose Support in the sidebar, and start your message with “Developer API” so it reaches the right team. Decisions on applications, and the note that comes with a rejection, show in the developer console.
In every request include:
- the key prefix and last four characters as shown in the developer console (never the full key),
- the
X-Request-Idandx-pump-api-key-idresponse headers of a failing call, - the route, the time (UTC) and the response body.
Requests we handle
Section titled “Requests we handle”| Request | What to send |
|---|---|
| Raise rate or daily limits | key prefix, routes you call, expected volume |
Add a scope (for example moderation.read) |
key prefix, the product need |
| Report a bug in the data or the docs | request id, route, what you expected |
| Report a leaked key | revoke it first in the developer console, then tell us the prefix |
Changes and deprecations
Section titled “Changes and deprecations”Deprecations are announced with the headers described in Versioning and deprecation and in the OpenAPI document (deprecated: true on the operation), at least 90 days before a route is removed.