Environments
The Replyco API has one environment, production, at one base URL:
| Environment | Base URL |
|---|---|
| Production | https://open-api.replyco.com |
There is no separate sandbox. A token reaches the live data of one company: the company of the user who signed in.
How it works
Section titled “How it works”- Base URL and paths. Every operation’s path starts with
/openapi/and is written in lower case, as in the API reference. Append it to the base URL:https://open-api.replyco.com/openapi/user/me. - HTTPS only. Call the API over
https://. Do not rely on a plainhttp://address being redirected. - One company per token. Which company’s tickets, customers and orders a call sees depends only on the user the token stands for. To work with a second company, sign in as a user of that company and keep its tokens apart.
Testing against live data
Section titled “Testing against live data”Because every call works with your company’s real data, test with care:
- Start with read operations, such as Your first request and the list operations, until your requests and your parsing work.
- Sign in as a dedicated user for the integration, so that anything it writes is easy to recognise as its work.
- When you build a custom integration, register a separate integration for testing.
Tickets and customers you create through it belong to that integration, so they are easy to tell apart from your
real channels. Delete the test integration with
DELETE /openapi/account/{id}when you no longer need it.
Related
Section titled “Related”- Authentication: signing in and the token on every call.
- Rate limits: how many calls the API accepts.