PalCards provides two environments. Build and test against sandbox, then switch to production.
Base URLs
| Environment | Base URL | Use it for |
|---|---|---|
| Sandbox | https://api-sandbox.palcards.ps |
Development & testing |
| Production | https://api.palcards.ps |
Live orders |
Keep the base URL in a single config value (e.g. BASE_URL) so you can switch environments without changing code:
BASE_URL="https://api-sandbox.palcards.ps" # production: https://api.palcards.ps
curl -H "x-api-key: $API_KEY" "$BASE_URL/user/profile"
Interactive API explorer (Swagger)
A Swagger / OpenAPI reference for the sandbox is available at https://api-sandbox.palcards.ps/docs. It is protected — ask your PalCards account manager for sandbox access and credentials.
Go-live checklist
Before pointing your integration at production:
- [ ] Your flow runs end-to-end in sandbox: catalog → (preflight) → create order → status/webhook.
- [ ] You created a production API key and added your production server IP(s) to its allowlist (see Create & manage your API key).
- [ ] You switch
BASE_URLtohttps://api.palcards.ps. - [ ] You treat fulfillment as asynchronous and handle every order status (see Order status lifecycle).
- [ ] You verify webhook payloads by re-fetching
GET /order/{id}— webhooks are unsigned (see Order webhooks). - [ ] Your wallet has a balance in the currency you'll order in (see Wallet & balance).
- [ ] You store each order's
idand yourclientOrderReffor reconciliation.