> ## Documentation Index
> Fetch the complete documentation index at: https://developer.uphold.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Make your first API call

> Make your first Uphold Enterprise API call using the public Postman workspace, with pre-configured Sandbox and Production environments and example requests.

The fastest way to make your first API call is through our public [Postman workspace](https://www.postman.com/uphold/workspace/enterprise-api). It includes pre-configured requests for every endpoint, automated scripts that chain variables between calls, and ready-to-use Sandbox and Production environments — no boilerplate required.

<Steps>
  <Step title="Fork the workspace">
    Open the [Enterprise API Postman workspace](https://www.postman.com/uphold/workspace/enterprise-api) and fork the collection to your own Postman account.

    Forking gives you a personal copy you can edit freely, and lets you pull upstream updates as the collection evolves.

    <Frame>
      <img src="https://mintcdn.com/uphold-d4756e17/7PPwldQuSVea3LMz/get-started/_media/postman-workspace.png?fit=max&auto=format&n=7PPwldQuSVea3LMz&q=85&s=042d6c5dc0339cd07b95ee57cd234625" alt="Enterprise API Postman workspace" width="3492" height="1958" data-path="get-started/_media/postman-workspace.png" />
    </Frame>
  </Step>

  <Step title="Select an environment">
    In the top-right corner of Postman, open the environment selector and choose the environment you want to target:

    * **Sandbox** — isolated testing environment with test funds and data. Recommended for development.
    * **Production** — live environment.

    <Warning>
      Targeting Production may result in unintended changes to live data. Always validate against Sandbox first.
    </Warning>
  </Step>

  <Step title="Set your credentials">
    Click the **Variables icon** next to the environment selector to open the variables drawer and set the following:

    | Variable             | Value                                         |
    | -------------------- | --------------------------------------------- |
    | `auth.client_id`     | Your Client ID from the Enterprise Portal     |
    | `auth.client_secret` | Your Client Secret from the Enterprise Portal |

    <Frame>
      <img src="https://mintcdn.com/uphold-d4756e17/7PPwldQuSVea3LMz/get-started/_media/postman-sandbox-setup-client-credentials-env.png?fit=max&auto=format&n=7PPwldQuSVea3LMz&q=85&s=9687916de0d722bfa1f47368369f3342" alt="Postman variables drawer with client credentials" width="3492" height="1958" data-path="get-started/_media/postman-sandbox-setup-client-credentials-env.png" />
    </Frame>

    <Tip>
      If you are using the public workspace without forking, please be aware that credentials must be set through the variables drawer as shown above. Editing them via the Environments tab is not supported since the workspace is read-only.
    </Tip>

    Don't have credentials yet? Follow the [Set up your account](/get-started/set-up-your-account) guide to create your API client.
  </Step>

  <Step title="Make your first API call">
    <Icon icon="rocket-launch" /> Lift off!

    Start with the [Authentication token](https://www.postman.com/uphold/workspace/enterprise-api/request/34958229-01b72490-f8c2-47c4-9449-83cb06726948?action=share\&source=copy-link\&creator=42626858\&active-environment=27bc7058-5bbb-457e-9234-c1abcba54ea8) request. It exchanges your client credentials for an access token.

    Once you send it, the collection scripts automatically store the token in the `auth.access_token` variable — subsequent requests will use it without any manual steps. The same applies throughout the collection: resource IDs (e.g. `core.user.id`, `core.account.id`, `core.transaction.id`) are captured after create/fetch operations and reused in follow-up requests automatically.

    This means you can work through a full flow — authenticate, create a user, create a quote, execute a transaction — by running requests in sequence without manually copying values between them.
  </Step>
</Steps>