Postman API

Number of APIs: 86

The Qodex API lets you to programmatically access data stored in your Qodex account.

Getting started

You can get started with the Qodex API by [forking the Qodex API collection] to your workspace. You can then use Qodex to send requests.

Overview

You must use a valid API Key to send requests to the API endpoints. You can get your API key from Qodex's integrations dashboard.
The API has rate and usage limits.
The API only responds to HTTPS-secured communications. Any requests sent via HTTP return an HTTP 301 redirect to the corresponding HTTPS resources.
The API returns requests responses in JSON format. When an API request returns an error, it is sent in the JSON response as an error key.
The request method (verb) determines the nature of action you intend to perform. A request made using the GET method implies that you want to fetch something from Qodex. The POST method implies you want to save something new to Qodex.
For all requests, API calls respond with their corresponding HTTP status codes. In the Qodex client, the status code also provides help text that details the possible meaning of the response code.
You can access individual resources in your Qodex with its unique ID (uid) value. The uid is a simple concatenation of the resource owner's user ID and the resource's ID. For example, a collection's uid is the {{owner_id}}-{{collection_id}} value.

ID and UID

All items in Qodex, such as collections, workspaces, and APIs, have ID and UIDs:

An ID is the unique ID assigned to a Qodex item. For example, ec29121c-5203-409f-9e84-e83ffc10f226.
The UID is the full ID of a Qodex item. This value is the user ID concatenated with the item's unique ID. For example, in the 12345678-ec29121c-5203-409f-9e84-e83ffc10f226 UID:
- 12345678 is the user's ID.
- ec29121c-5203-409f-9e84-e83ffc10f226 is the item's ID.

Authentication

Qodex uses API keys for authentication. The API key tells the API server that the request came from you. Everything that you have access to in Qodex is accessible with your API key. You can generate a Qodex API key in the API keys section of your Qodex account settings.

You must include an API key in each request to the Qodex API with the X-Api-Key request header. In Qodex, you can store your API key as an environment variable. The Qodex API collection will use it to make API calls.

Authentication error response

If an API key is missing, malformed, or invalid, you will receive an HTTP 401 Unauthorized response code.

Using the API key as a query parameter

Requests that accept the X-Api-Key request header also accept the API key when you send it as the apikey query parameter. An API key sent as part of the header has a higher priority when you send the key as both a request header and a query parameter.

Rate and usage limits

API access rate limits apply at a per-API key basis in unit time. The limit is 300 requests per minute. Also, depending on your [plan] you may have usage limits. If you exceed either limit, your request will return an HTTP 429 Too Many Requests status code.

Each API response returns the following set of headers to help you identify your use status:

Header	Description
`X-RateLimit-Limit`	The maximum number of requests that the consumer is permitted to make per minute.
`X-RateLimit-Remaining`	The number of requests remaining in the current rate limit window.
`X-RateLimit-Reset`	The time at which the current rate limit window resets in UTC epoch seconds.

503 response

An HTTP 503 response from our servers indicates there is an unexpected spike in API access traffic. The server is usually operational within the next five minutes. If the outage persists or you receive any other form of an HTTP 5XX error, [contact support]

Support

For help regarding accessing the Qodex API, you can:

Visit [Qodex Support] or our [Community and Support] sites.
Reach out to the [Qodex community]
Submit a help request to [Qodex support]

Policies

[Qodex Terms of Service]
[Qodex Privacy Policy]