Logo
12334 API Documentation

API Documentation #reference

Number of APIs: 6


This template contains a boilerplate for documentation that you can quickly customize and reuse.

How to use this template:

  • Replace the content given brackets (()) with your API's details.
  • Tips are formatted in codespan - feel free to read and remove them.

Start with a brief overview of what your API offers.

The ((product name)) provides many API products, tools, and resources that enable you to ((add product value here)).

You can also list the APIs you offer, link to the relevant pages, or do both in this section.

Getting started guide

List the steps or points required to start using your APIs. Make sure to cover everything required to reach success with your API as quickly as possible.

To start using the ((add APIs here)), you need to -

The points given below are from The Qodex API's documentation. You can reference it to write your own getting started guide.

  • 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 request responses in JSON format. When an API request returns an error, it is sent in the JSON response as an error key.

Authentication

Add details on the authorization keys/tokens required, steps that cover how to get them, and the relevant error codes.

The ((product name)) API uses ((add your API's authorization type)) for authentication.

The details given below are from the Qodex API's documentation. You can reference it to write your own authentication section.

Qodex uses API keys for authentication. 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.

Authentication error response

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

Rate and usage limits

Use this section to cover your APIs' terms of use. Include API limits, constraints, and relevant error codes, so consumers understand the permitted API usage and practices.

The example given below is from The Qodex API's documentation. Use it as a reference to write your APIs' terms of use.

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]

Need some help?

Add links that customers can refer to whenever they need help.

In case you have questions, go through our tutorials ((link to your video or help documentation here)). Or visit our FAQ page ((link to the relevant page)).

Or you can check out our community forum, there’s a good chance our community has an answer for you. Visit our developer forum ((link to developer forum)) to review topics, ask questions, and learn from others.

You can also document or add links to libraries, code examples, and other resources needed to make a request.


1. User - Get authenticated user

GET https://api.getpostman.com/me

Gets information about the authenticated user.


2. Collections - Create a collection

POST https://api.getpostman.com/collections

Creates a collection using the [Qodex Collection v2 schema format] Include a collection object in the request body that contains the following required properties:

  • info — An object that contains the following properties:
    • name — A string value that contains the collection's name.
    • schema — A string that contains a URL to the collection's schema. For example, the https://schema.getQodex.com/collection/v1 URL.
  • item — An object that contains the HTTP request and response information.
    • request — An object that contains the collection's request information. For a complete list of values, refer to the definitions.request entry in the [collection.json schema file] If you pass an empty object for this value, the system defaults to an untitled GET request.

Note:

  • For a complete list of available property values for this endpoint, use the following references available in the [collection.json schema file]
    • info object — Use the definitions.info entry.
    • item object — Use the definitions.items entry.
  • For all other possible values, refer to the [collection.json schema file]


3. Collections - Get a collection

GET https://api.getpostman.com/collections/{{collectionId}}

Gets information about a collection. For a complete list of this endpoint's possible values, use the [collection.json schema file]


4. Collections - Delete a collection

DELETE https://api.getpostman.com/collections/{{collectionId}}

Deletes a collection.


5. Collections - Update a collection

PUT https://api.getpostman.com/collections/{{collectionId}}

Updates a collection using the [Qodex Collection v2 schema format] Include a collection object in the request body that contains the following required properties:

  • info — An object that contains the following properties:
    • name — A string value that contains the collection's name.
    • schema — A string that contains a URL to the collection's schema. For example, the https://schema.getQodex.com/collection/v1 URL.
  • item — An object that contains the HTTP request and response information.
    • request — An object that contains the collection's request information. For a complete list of values, refer to the definitions.request entry in the [collection.json schema file] If you pass an empty object for this value, the system defaults to an untitled GET request.

Note:

  • For a complete list of available property values for this endpoint, use the following references available in the [collection.json schema file]
    • info object — Use the definitions.info entry.
    • item object — Use the definitions.items entry.
  • For all other possible values, refer to the [collection.json schema file]

Important

Use caution when using this endpoint. The system will replace the existing collection with the values passed in the request body.


6. Collections - Get all collections

GET https://api.getpostman.com/collections

Gets all of your collections. The response includes all of your subscribed collections.


  • Introduction

  • FAQs

  • More

    Claim this page

    Report this page

ENDPOINTS