---
title: "Postman collection"
description: "Import, configure, and use the versioned Inttegro API collection in Postman or Newman."
canonical: "https://studio.inttegro.com/collections/postman"
format: inttegro-machine-docs/v1
language: "cURL"
reader_profile: optional
reader_manifest: "https://studio.inttegro.com/machine/curl/readers/index.json"
reader_identification: "Optional: declare your client only if known and your current-session capabilities; use reader_manifest for supplemental recommendations."
preamble_estimated_tokens: 336
model_token_report: "https://studio.inttegro.com/machine/token-report.json"
preamble_questions: 5
preamble_source: "general"
recommended_mcp_tools: []
estimated_tokens: 1463
token_estimate_method: "utf8_bytes_divided_by_4"
---

## Machine preamble

**Summary:** Import, configure, and use the versioned Inttegro API collection in Postman or Newman. This cURL representation preserves HTTP paths and JSON wire names.

### Five questions

#### Q1. When should the reader use Postman collection?

Use this page as orientation before selecting the narrower guide or reference that owns the implementation contract.

#### Q2. What is authoritative on this page?

Use this page for orientation; follow its canonical SDK, guide, API, or MCP links for exact contracts.

#### Q3. What page-specific constraint matters most?

Use the page to choose a canonical next source instead of treating summary material as a complete implementation contract.

#### Q4. Can Inttegro MCP materially help with this task?

No catalog ability is sufficiently specific to recommend for this page. Use the documentation directly; consult the MCP catalog only if the task later requires governed live account context or a supported operation.

#### Q5. How should the reader verify the answer and continue?

Select the narrowest linked guide or reference, apply its stated completion condition, and verify against authoritative resource state when the task changes data. Continue with [Read the API quickstart](https://studio.inttegro.com/machine/curl/quickstart.md) when those concerns enter scope.

## Document content

![Postman](/img/logos/api/postman.svg)

# Use the Inttegro API in Postman

Import ready-to-send requests for every public Inttegro API operation. The
collections include request examples, shared variables, response checks, and a
safe hosted-checkout workflow. [Get the Postman collection](https://github.com/inttegro/openapi/tree/master/postman) [Read the API quickstart](https://studio.inttegro.com/machine/curl/quickstart.md)

## Import and configure

1. Download and import `00-environment.postman_environment.json`.
2. Import the API-area collections you need, or import all of them.
3. Select the **Inttegro API** environment and set `api_key` locally. The
   published value is empty and marked secret.
4. Give `idempotency_key` a new stable value for each new logical operation.
   Reuse it only when retrying the same request with the same body.
5. Replace the example variables required by the request you want to send.

Successful create requests save returned IDs to the selected environment. For
example, a customer created in the Customers collection becomes available to
Payment Methods and Checkout without copying its ID by hand.

## What is available

| Area                          | What you can test                                                       |
| ----------------------------- | ----------------------------------------------------------------------- |
| Checkout and orders           | Hosted checkout and the complete order lifecycle                        |
| Customers and payment methods | Customer records and reusable payment methods                           |
| Catalog and Purchase intents  | Products, prices, Purchase intents, and Buy links                       |
| Money movement                | Financial accounts, balances, balance transactions, and payouts         |
| Communications                | Notifications, schedules, broadcasts, templates, and one-time passwords |
| Files                         | Files, file links, and third-party upload requests                      |
| Platform                      | Apps, API keys, and reference data                                      |
| Refunds                       | Refund creation, lookup, and history                                    |

## Start with hosted checkout

Import `workflows/checkout-quickstart.postman_collection.json` and run its two
requests in order. It creates a finalized order, captures `order_id` and
`checkout_url`, and looks the order up. It does not request or confirm payment.

To run the same workflow in CI, provide the key and request-specific values as
environment variables and pass them to Newman at runtime:

```sh
npx newman run postman/workflows/checkout-quickstart.postman_collection.json \
  --environment postman/00-environment.postman_environment.json \
  --env-var "api_key=${INTTEGRO_API_KEY}" \
  --env-var "base_url=${INTTEGRO_API_BASE_URL}" \
  --env-var "order_number=${INTTEGRO_ORDER_NUMBER}" \
  --env-var "idempotency_key=${INTTEGRO_IDEMPOTENCY_KEY}" \
  --bail
```

Choose a new order number and idempotency key together for each new checkout.
Keep both unchanged when retrying that checkout after a timeout.

:::warning Run only the operation you intend

Some collections can send messages, schedule payouts, change settings, cancel
resources, or delete files. Do not run every collection indiscriminately
against a live account.

:::

## Versions

The collection bundle version matches the public API contract version. Postman
Collection 2.1 is the file format, not the Inttegro API version. The version is
available in each collection's `info.version` and as `collection_version` in
the shared environment. Pin the bundle's Git commit for repeatable CI.