Skip to main content

Testing Environment

The Testing environment replicates the production environment, allowing you to experiment with new API calls, test integrations, and debug without affecting real data. All XGS APIs in the testing environment use the same endpoints as production, with a key difference in the URL path.

URL Structure​

Testing APIs are identical to production APIs but with /testing as the prefix in the URL path. For example:

GET /testing/agent/probill

Authentication​

The same set of credentials and token works for both Testing and Production enviroment.

tip

Refer the Authenticaion Guide for details on how to get Token and use it with APIs

Example: Switching Between Environments in XGS​

Let’s consider an example where you want to retrieve probill details in both environments.

  • Production API Call:
GET https://srvcs.xgsi.com/agent/probill?probillNumber=12345678

This call fetches probill details from the live production environment.

  • Testing API Call:
GET https://srvcs.xgsi.com/testing/agent/probill?probillNumber=12345678

This call does the same but in the testing environment, allowing you to safely test without impacting live data. By simply adding the /testing prefix, you can switch to a sandboxed environment without altering the core logic of your application. This is especially useful for debugging and refining code before moving it to production.

Use Cases​

  • Feature Testing: Try out new API features or endpoints in a safe, non-production environment.
  • Integration Development: Build and test integration workflows to ensure they function as expected before moving to production.
  • User Training: Provide training for users without risking live data.