Integrations
Every useapi.net endpoint is a plain HTTPS request with your API token in the Authorization header, so it works from any tool that can make one. This page covers Postman, n8n and other automation tools, MCP clients, and machine-readable descriptions of the APIs.
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
- Postman collections
- Use a Postman collection
- n8n, Make.com and other automation tools
- MCP servers
- OpenAPI / Swagger
- Machine-readable discovery
Postman collections
The raw JSON files are the same collections we sync to the workspace, in Postman Collection v2.1 format.
Use a Postman 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.
n8n, Make.com and other automation tools
No plugin is needed. In n8n, add an HTTP Request node, take the method and URL from the endpoint’s docs page, and send your token as an Authorization: Bearer {API token} header. Most generation endpoints are asynchronous: poll the job endpoint until the job completes, or, where the endpoint accepts replyUrl, set it to an n8n Webhook node URL so the result is pushed to your workflow.
n8n AI Agent workflows can also call our hosted MCP servers through the MCP Client Tool node. Use the server URL from that service’s MCP page, listed under MCP Servers, and your API token as a Bearer auth header. Gemini Notebook (NotebookLM) podcasts with n8n is a full worked example.
Make.com, Zapier and similar tools work the same way through their HTTP modules. To upload a raw file from Make.com, see this Q&A answer.
MCP servers
Our hosted MCP servers expose the APIs as tools to Claude Code, Cursor, VS Code and other MCP clients, with your API token in the Authorization header. MCP Servers links to each server’s page, which gives its URL and setup.
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.