For developers
Postman collection generator
Get a full Postman Collection v2.1 JSON for our API, with the real base URL and a bearer-auth placeholder already set - paste it straight into Postman.
Free, no accountIn your browser
A full collection, or just one section of the API.
Result
Collection ready - 174 requests
A Postman Collection v2.1 JSON for every documented operation, with https://resellerhq.com/api as the base URL and a bearer-auth placeholder already set.
Postman collection
Paste your own key into the RHQ_API_KEY collection variable before sending anything - this placeholder is never a real key.
- This is a copyable JSON value, not a file download - the platform has no download affordance for it. Import it into Postman with Import → Raw text, or save it to a .json file yourself.
- Every example value comes from the OpenAPI document's own documented examples; a parameter with none is left blank, not guessed at.
What this is
This Postman collection generator builds a Postman Collection v2.1 JSON straight from the same operations our API docs describe - the real base URL, every documented parameter and example, and a bearer-auth placeholder already wired up, so importing it is the only step left before a real key makes it runnable.
Every request in the collection comes from the same committed OpenAPI document our own API docs are built from: the method, the path, every parameter and its documented example value. Choosing a section only ever narrows which operations are included - it never changes what any one of them says.
The collection sets its base URL as a `baseUrl` variable and its authorisation as a bearer token read from an `RHQ_API_KEY` variable, left blank on purpose: Postman asks for that variable once, in one place, rather than a real key being typed into dozens of individual requests.
How to read the result
Copy the JSON below and use Postman's own Import → Raw text to bring it in, then fill the `RHQ_API_KEY` collection variable with your real key - every request already points at it through the collection's shared bearer auth, so nothing per-request needs editing.
Choosing one section of the API instead of all of it is for a smaller collection to work with while testing one part of an integration; the headline above always says exactly how many requests the chosen scope produced.
"Verifying one of our webhooks" points here for bringing the whole API into Postman in one step, alongside the single-operation API request builder, before its own sections on signing, retries and error codes.
Common mistakes
What goes wrong most often, and how to tell.
- Expecting a file to downloadThis page has no download button: the collection is a copyable JSON value, the same as any other generated artifact here. Copy it and use Postman's own Import → Raw text, or paste it into a .json file yourself.
- Sending a request before the RHQ_API_KEY variable is filled inThe bearer token the collection sets is a placeholder variable, deliberately left blank - every request answers 401 until that one collection variable is filled in with a real key from the dashboard.
Questions
What people ask about this tool.
- No - this page copies a JSON value to your clipboard, the same as every other generated artifact here; it has no file-download button. Paste the copied JSON into Postman with Import → Raw text, or save it to a .json file yourself.
- No. The bearer token is a placeholder collection variable named RHQ_API_KEY, left blank on purpose - nothing generated here can see or hold your real key, and every request in the collection fails with 401 until you fill that one variable in yourself.
- Because the collection only ever includes the operations that section's own tag covers in our OpenAPI document - the headline always states exactly how many requests that choice produced, so it is never a surprise once the JSON is pasted into Postman.
- Schema v2.1, the same one Postman itself documents at schema.postman.com - every request here carries the fields that schema actually requires: a name, a request with a method and a URL, and headers that each carry a key and a value.
Sources
Every fixed value here comes from the provider’s own documentation. These pages change, so each says the day it was last read.
- Postman, “Postman Collection Format v2.1.0” read 13 October 2026
Use it from the API
The same check, as one request.