What Is API Collection Manager?
API Collection Manager is a free online tool by TechnSols that stores API requests as named collections in your browser. You create a collection, add requests with a name, a method, a URL, headers, and a body, and the tool keeps them saved, so a working request is one click away instead of a paste from a note. Collections export as JSON and import back the same way. There is nothing to install and no account to make.
A collection is the habit that separates a one-off test from a repeatable workflow. The Postman Collections Guide guide describes the same idea in Postman: group related requests, give each one a clear name, and run them in order when you need to check a whole API. When a saved request returns an answer, the REST API Playground tool sends it to the endpoint and shows the status, the time, and the body.
The honest limit is that collections live only in this browser. They are stored in localStorage on your own computer, not on a server, so they do not follow you to another device unless you export the JSON file and import it there. If the browser data is cleared, the collections go with it, so export a backup after a big change. A collection can hold many requests, but it never sends one by itself: the GraphQL Playground tool runs a saved query, and sending stays the playground’s job.
How To Use API Collection Manager?
Here is how to manage API collections online in three quick steps. Using API Collection Manager is simple. There is no software to install and no account to make. Create a collection, add requests, and export a backup. When a spec lists the endpoints to collect, the API Documentation Tester tool tests each one first.
Step 1: Create A Collection
Type a collection name that says what the API is, for example Sample Books API, and press Create Collection. A collection holds the requests for one API, so make one per API instead of mixing several APIs into one list. The name is the label you will see in the list, so keep it short and clear.
Step 2: Add Named Requests
Open the collection and add a request: a name that says what it does, the method, the full URL, the headers one per line, and the body when the method needs one. Name the request after its job, such as List Books or Create Book, so the list reads like a checklist. A request with a vague name is hard to find later.
Step 3: Edit, Export, And Import
Edit a request when the API changes, and delete the ones that no longer exist, so the collection stays true. Press Export to download the whole collection as a JSON file, and keep that file as a backup. Press Import to load a JSON file back, whether it came from this tool or from a teammate.
The whole job takes a few minutes. A collection that is exported after every change is never lost, and a collection that is kept tidy is the one you will actually use.
Why API Collection Manager?
Requests scattered across notes, chat messages, and browser history are requests you will lose. A collection puts them in one named place, with the method, URL, headers, and body together, so the next test starts from a known good request instead of a half-remembered paste. The API Documentation Builder tool turns a tidy collection into written docs when the API needs them.
A Known Good Request Every Time
Every API test starts from a request that worked before. When that request lives in a collection, you open it and send it, instead of rebuilding it from memory and wondering which header you forgot. A known good request turns a failing test into a real signal, because the request itself is not the variable.
Names That Read Like A Checklist
A collection named after the API, with requests named after their jobs, reads like a checklist of what the API does. List Books, Get Book, Create Book, Delete Book: the list itself documents the API. That clarity helps a teammate who opens the collection for the first time and needs to know where to start.
Export Keeps Your Work Portable
Collections are JSON files, so they move: export one, send it to a teammate, and they import it and see the same requests. That portability is the difference between a personal note and a shared workflow. An exported file is also a backup, so a cleared browser never means lost work.
What Can You Do With API Collection Manager?
Collections fit any workflow where the same requests are sent again and again. These are the jobs it handles best.
Organise Requests By API
Give each API its own collection, and each endpoint its own named request. A project with three APIs gets three collections, not one long mixed list. When a saved request returns JSON, the JSON Formatter tool formats the answer so it is easy to read.
Keep A Regression Set Ready
Save the requests that prove an API works: one per endpoint, with the values that should succeed. After a deploy, open the collection and send each one in turn. A request that fails after a deploy points at the change that broke it, and the set grows as the API grows.
Share Requests With A Teammate
Export a collection and send the JSON file to a teammate, who imports it and sees the same requests, with the same names, methods, and URLs. The URL Encoder Decoder tool encodes the query values in a shared request URL when it carries spaces or special characters.
Quality And Settings
The manager shows a list of collections, each with its requests, and a form for adding or editing one request. Requests carry a name, a method, a URL, headers, and a body, and collections carry a name and a request count. The OpenAPI Documentation Previewer tool previews a full OpenAPI spec as docs when you need the whole API, not one collection.
- Collections: create, rename, and delete named collections, each holding many requests.
- Requests: name, method, URL, headers, and body per request, with edit and delete.
- Export: the whole collection as a JSON file, ready to back up or share.
- Import: a JSON file back in, with a clear error when the file is not a collection.
- Limits: stored in this browser only; export to move or back up; no sending from this tool.
There are no settings beyond collections and requests, because the list is the whole tool. Keep names clear, export after a change, and delete the requests that no longer exist.
How API Collection Manager Works
The manager keeps your collections in the browser’s localStorage, under one key per collection set. Adding a request writes it to that store at once, so closing the tab does not lose it, and opening the page again shows the same collections. The HTTP Status Code Checker tool explains the status code a saved request returns when you send it.
Two limits are worth knowing. First, localStorage belongs to this browser on this device, so a collection does not appear on another computer until you export the JSON and import it there. The LocalStorage Guide guide explains that storage rule. Second, a token stored in a request is visible to anyone who opens the browser, so use test tokens where you can and export with care.
Privacy
Everything you type stays in your browser. The work is done on your own computer, and nothing you enter is uploaded to a server, stored, or shared with anyone. Closing the tab clears the form, so the details never leave your device.
Because no account is needed, there is no name, email, or history tied to what you check. Closing the tab ends the session, and the browser clears the input from memory. That is the same protection on every tool here: your work stays yours, and nothing about it is kept, shared, or sold.
Tips
A few habits make API Collection Manager work smoother, whether you are keeping one collection or a dozen.
- One collection per API, so a list never mixes two different services.
- Name requests after their job, so the list reads like a checklist.
- Export after every big change, so a cleared browser never means lost work.
- Delete requests the API no longer has, so the collection stays true.
- Keep test tokens in requests, never a live production token.
When a collection is tidy and backed up, it becomes the first place you look when an API changes. If a saved request needs a value checked in its answer, the Regex Tester tool finds it with a pattern.
More Tools For The Same Job
These tools handle the same kinds of jobs: testing, reading, and organising the APIs a project needs.
- REST API Playground: sends a request from a collection to a REST endpoint.
- GraphQL Playground: runs a query saved in a collection against an endpoint.
- API Documentation Tester: tests every endpoint listed in an OpenAPI spec.
- API Documentation Builder: turns a collection into written API docs.
- OpenAPI Documentation Previewer: previews an OpenAPI spec as readable docs.
- JSON Formatter: formats the JSON a saved request returns.
- URL Encoder Decoder: encodes the query values in a saved request URL.
- HTTP Status Code Checker: explains the status code a saved request returns.
- Regex Tester: finds a value inside a long response with a pattern.
- URL Query String Parser: reads the query string of a saved request URL.
FAQ
Common questions about API Collection Manager, answered plainly.
Is API Collection Manager by TechnSols Free?
Yes, API Collection Manager by TechnSols is completely free to use, with no account, no sign-up, and no usage limit. You can create as many collections and requests as you like, and everything stays in your browser, so nothing is uploaded or stored anywhere.
Where Are My Collections Stored?
Collections are stored in your browser’s localStorage, on your own computer, under one key for the whole set. They are not sent to a server and they do not follow you to another device. Export a collection as JSON to move it, and import that file on the other device.
Can I Import A Postman Collection?
The manager imports the JSON format this tool exports, which is a simple list of collections and requests. A Postman v2.1 export has a different shape, so it will not import directly. Export from Postman is a separate format; use the requests as a guide and add them here by hand.
Does The Manager Send Requests?
No, the manager only stores requests; it never sends one. Open a saved request in the playground to send it and read the answer. Keeping storage and sending apart means a saved request is never sent by accident, and the playground shows the live response when you choose to send.
What If The Import File Is Wrong?
The manager checks the file before it imports anything and shows a clear error when the file is not a collection in the expected shape. Nothing is overwritten when an import fails, so your existing collections stay safe. Fix the file, or export a fresh one, and try again.
Create the collection, name the requests after their jobs, and export a backup. A tidy collection is the fastest way to test an API twice, and the cheapest way to share it.