- At present, Resilinc does not provide a separate staging or test environment for API testing.
- All API interactions, including writeback functionality, are supported only in the production environment.
- Separate credentials for non-production testing are not provided.
Key Points to Understand:
- Single environment: API calls are executed directly against the production system. There is no sandbox or non‑production environment available.
- Credentials: Separate credentials for testing purposes are not issued. Users must use their production credentials to authenticate API requests.
- Impact of writeback: Since writeback operations affect live data, users should exercise caution when testing or experimenting with APIs to avoid unintended changes.
- Best practice: If testing is required, it is recommended to use non‑critical or sample records in production to validate API behavior without impacting key business data.
- Monitoring: Ensure that API usage is monitored closely during testing to track any changes and confirm expected outcomes
Recommendation:
- Organizations should plan API testing carefully within production, ideally with support from their Resilinc administrator or technical team, to minimize risk and ensure data integrity.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article