Postman collections
We maintain a Postman collection for every API we currently offer, in the public useapi.net Postman workspace. Each collection covers the endpoints of one API, and most requests link back to their page in these docs.
Table of contents
Collections
The raw JSON files are the same collections we sync to the workspace, in Postman Collection v2.1 format.
Use a collection
- Get your useapi.net API token, see Setup useapi.net.
- Open the collection in the workspace and click Fork to copy it into your own workspace. You can also download the raw JSON from the table above and use Import in the Postman app.
- Open the collection’s Variables tab and paste your token into
api-token. Requests send it asAuthorization: Bearer {API token}. - Fill in the other collection variables the requests use, such as the service account
emailor ajobidreturned by an earlier call. - Pick a request, adjust its body or query parameters, and send it. The endpoint’s docs page lists every parameter and response field.
Most generation endpoints are asynchronous. Send the create request first, then call the matching job endpoint with the returned id until the job completes. Every endpoint page also has a Try It form if you would rather test in the browser.
OpenAPI / Swagger
We do not publish separate OpenAPI (Swagger) specs for the current APIs. The Postman collections are the machine-readable description of each API. If your tooling needs OpenAPI, convert the raw collection JSON with a Postman-to-OpenAPI converter, and check the result against the endpoint docs.
Machine-readable discovery
/.well-known/api-cataloglists every active API with its docs page and its collection JSON (RFC 9727)./auth.mddescribes how API authentication works, for AI agents.- LLM tools has per-service documentation files,
llms.txt, and drop-in context files for Claude Code and Cursor.