Temporary API
3 free days per endpoint, no signup.
- 1 Pick a method GET, POST, PUT, DELETE and PATCH all work
- 2 Paste JSON The body you want back — params are optional
- 3 Grab the URL Hit create, copy the /t/xxxx one
Open it in a browser, or use curl:
curl "https://www.temp-api.com/t/xxxx"
All five methods work; the one you pick only labels the endpoint. The response body must be valid JSON — the page tells you if it isn't.
Going further
Open a section when you need it.
Management key: manage it from any machine
After creation the management key appears in the Manage block of the preview page (12 characters, like XXXX-XXXX-XXXX). It is kept only in this browser, so the page never shows it again — use the copy button next to it and save it somewhere safe.
On another computer, in another browser, or after clearing the cache, open https://www.temp-api.com/e/xxxx and enter the key to keep managing the endpoint. The key is the credential: don't commit it, share it, or post it publicly.
Update issues a new key and the old one stops working immediately. The URL and the content stay the same.
Edit, pause and resume
Edit on the preview page changes the response in place — save it and the same URL returns the new JSON right away. Editing does not extend the expiry date.
The Status switch pauses or resumes the endpoint at any time: while paused visitors get 503 plus a short note, and the content is kept. Flip it back and the endpoint returns immediately.
Hand it to an AI assistant
AI prompt on the same page copies a short brief with the endpoint URL, the management URL and the key. Paste it to an AI assistant or agent (ChatGPT, Claude Code, DeepSeek) and it can call the endpoint, edit the content, pause or resume it — no docs to write.
The brief contains the key, so only paste it into tools you trust; hover the prompt to preview it first.
How expiry works
The countdown starts when you create it, and the endpoint stops working 3 days later. Requests after that return 410 with no data. Need longer? See the long-term API below.
Need it for longer?
Opened with a key and valid for your plan — built for ongoing frontend-backend integration.
Show the steps
1. Get a key — no key yet? Contact support to request one.
2. Create an endpoint — open the Long-term API page, enter your key under API key, then pick a request method and enter the response body. Click Create long-term API. The form is the same as on the temporary page, plus the key field.
You then land on a preview page with a URL that starts with /p/, e.g. https://www.temp-api.com/p/xxxx.
3. Call it — request that URL and it returns the JSON you entered:
curl "https://www.temp-api.com/p/xxxx"
To see the response format first, open the long-term example. Existing endpoints show remaining quota and expiry, and can be edited or deleted; deleting frees the slot right away.
Rather not build one? Use mock data
Users, products, orders, posts and todos, ready to use — with pagination, filtering and CORS.
curl "https://www.temp-api.com/mock/users?limit=3"
curl "https://www.temp-api.com/mock/users/1/orders"
More about mock data
Nothing to create — call them directly under https://www.temp-api.com/mock, and the URLs never change. No key, no signup.
Data covers users, products, orders, posts, comments and todos, plus auth and HTTP debugging endpoints. The shapes mirror real-world products, and responses stay the same between calls.
Writes (POST, PUT, DELETE) return a simulated result but are not stored.
Browse Mock APIs · Users · Products · Posts
Common statuses
What 404, 410, 429 and 503 mean
| Status | Meaning | What to do |
|---|---|---|
| 404 | Not found | Check the URL |
| 403 | Invalid or expired key (long-term) | Check the key or contact support |
| 410 | Expired | Create a new endpoint, or renew a long-term one |
| 429 | Too many requests | Try again later |
| 503 | The creator paused the endpoint | The content is still there — wait for it to be resumed, or use the management key to turn it back on |
Start with: Temporary API · Long-term API · Mock data