Getting Started
Use the staging environment first to complete your integration flow before sending production traffic.
Environments
Use the Console that matches the API environment you want to call.
| Environment | Console | API Base URL |
|---|---|---|
| Staging | https://staging-merchant.esing.io | https://esing-pay-staging-api.eastasia.cloudapp.azure.com |
| Production | https://merchant.esing.io | https://api.esing.io |
Staging and production are completely isolated. Create API keys and webhook configuration separately for each environment. Resources and integration data are not shared between staging and production.
Configure Your Integration
Before calling the API:
- Sign in to the Console for the target environment.
- Create an API key for that environment. The authentication flow is documented in Authentication.
- Configure your webhook URL in the same environment.
- Keep the API base URL and API key paired to the same environment in your integration configuration.
Make Your First Request
Start with a read-only request in staging to verify that your API key is valid and your HTTP client is configured correctly.
curl --request GET \
--url 'https://esing-pay-staging-api.eastasia.cloudapp.azure.com/external/v1/wallets' \
--header 'Accept: application/json' \
--header 'Authorization: Bearer <staging_api_key>'
If the request returns 401 Unauthorized, check that you are using the staging API host with a staging API key and that the Authorization header uses the Bearer scheme.
Blockchain Networks
The blockchain network is selected by the API environment. Staging requests use the configured test network, while production requests use the corresponding main network. For Tron, staging currently uses Nile (tron:nile) and production uses Mainnet (tron:mainnet).