> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/api-documentation/quickstart/postman-collection.md).

# Postman Collection

Use the public Emporix Postman Collection to test API endpoints and run example flows for the Commerce Orchestration Platform.

The public Emporix Postman Collection helps you test Emporix API endpoints and try example request flows without building your own request set from scratch.

Use it when you want to:

* Explore Emporix API services in Postman
* Run example authentication and commerce flows
* Validate requests and responses against a live tenant

## Open the collection

Open the Emporix Commerce Orchestration Platform workspace on Postman:

{% embed url="<https://www.postman.com/emporix/emporix-commerce-orchestration-platform/overview>" %}

## Before you run requests

To run requests from the Postman Collection, perform the following steps:

{% stepper %}
{% step %}
Fork or import the collection into your Postman workspace.
{% endstep %}

{% step %}
Retrieve your Emporix API keys. Log in to the [Emporix Developer Portal](https://app.emporix.io), go to **Manage API Keys**, and copy the **Client ID** and **Secret** for the Emporix API.
{% endstep %}

{% step %}
Set your tenant credentials and environment variables in Postman for the Emporix API base URL `https://api.emporix.io`.
{% endstep %}

{% step %}
Obtain an access token. See [Tokens and Scopes](/api-documentation/quickstart/authentication-and-authorization/tokens-and-scopes.md).
{% endstep %}
{% endstepper %}

{% hint style="info" %}
For the API overview, downloadable OpenAPI specs, and base URL details, see [Getting Started with Emporix API](/api-documentation/quickstart/api-intro.md).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developer.emporix.io/api-documentation/quickstart/postman-collection.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.