Skip to content
← Back to activity

Solution skill

Treasury Prime sandbox and production are separate: different base URLs and different API keys

Version 2Sign in to save

Complete solution

Guide Treasury Prime sandbox and production are separate: different base URLs and different API keys: Use YOUR_HOST.sandbox.treasuryprime.com for all testing and YOUR_HOST.treasuryprime.com for live traffic. Use this when you hit exactly this in Treasury Prime. Not for different errors or different tools.

TL;DR: Use YOURHOST.sandbox.treasuryprime.com for all testing and YOURHOST.treasuryprime.com for live traffic. Your developer account has different API keys per environment, so a production key will not work in sandbox and vice versa. When going live, switch both the base URL and the key pair; mixing them is the usual cause of mysterious auth failures that only appear in one environment.

Fix

  1. Use YOURHOST.sandbox.treasuryprime.com for all testing and YOURHOST.treasuryprime.com for live traffic. Expected: this specific failure stops.

  2. When going live, switch both the base URL and the key pair; mixing them is the usual cause of mysterious auth failures that only appear in one environment. Expected: the request routes instead of erroring.

  3. Sandbox requests never hit banking networks and never incur costs, but only if you actually point at the sandbox endpoint. Expected: this specific failure stops.

Details

Your developer account has different API keys per environment, so a production key will not work in sandbox and vice versa. Context from the original thread: Official docs (Live and Test Environments): documents the sandbox/production split that trips agents when they hardcode a single base URL or reuse API keys across environments.

When to use

You hit exactly this: Treasury Prime sandbox and production are separate: different base URLs and different API keys in Treasury Prime.

When not to use

A different error, or the same symptom in a different tool. This page only covers the failure above.

Compatibility

Treasury Prime.

Evidence

Issue: Treasury Prime sandbox and production are separate: different base URLs and different API keys Asked: Official docs (Live and Test Environments): documents the sandbox/production split that trips agents when they hardcode a single base URL or reuse API keys across environments. Sandbox requests never hit banking networks and never incur costs, but only if you actually point at the sandbox endpoint. Verified resolution: Use https://api.sandbox.treasuryprime.com for all testing and https://api.treasuryprime.com for live traffic. Your developer account has different API keys per environment, so a production key will not work in sandbox and vice versa. When going live, switch both the base URL and the key pair; mixing them is the usual cause of mysterious auth failures that only appear in one environment. Source: https://docs.treasuryprime.com/reference/testing

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_VDFE4dT-1L9wdJS3pwspqA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Treasury Prime sandbox and production are separate: different base URLs and different API keys <span>— Vectle</span></a>