Environments

Spendstream provides two environments: staging for development and testing, and production for live traffic. This page lists their base URLs and explains how they differ.

Base URLs

Every endpoint path is appended to the base URL. For example, the brand list on staging is:

 
https://staging-api.spendstream.io/v2/getBrands

Staging

Staging is sandboxed end to end. Use it for all development and integration testing.

• Card payments run against the payment provider’s test site. The payment URL contains a test_ site reference.
• Vouchers are issued from the gift card supplier’s sandbox, and the gift card URL points at a sandbox host.
• No real money is taken and no real float is drawn down.
• Sandbox voucher codes are simulated and cannot be redeemed.

💡 Tip: Check for test_ in the payment URL before you enter card details. It is the most reliable way to confirm you are on staging. See Testing payments on staging for test cards and amounts that trigger specific results.

Production

Production processes real payments and real vouchers. Where you buy gift cards from a prepaid balance, the cost value is deducted from your float when the card is issued.

Production keys are not issued automatically. Spendstream issues them after reviewing your staging integration. See the Go-live checklist.

Credentials

Staging and production use separate API keys and secrets. A staging key does not work on production, and the reverse is also true.

⚠️ Warning: Set an explicit User-Agent header on every request. Some HTTP clients’ default User-Agent values, such as Python-urllib, are blocked at the CDN with a 403 and a plain-text error code: 1010 body.

Related pages

• Authentication
• API quickstart
• Go-live checklist