API availability
A generally available customer integration API is planned, but no public contract is defined by this documentation release.
What not to rely on
Section titled “What not to rely on”Do not treat browser requests, private service addresses, or observed payloads as a supported integration surface. They can change without customer-facing compatibility guarantees.
What published documentation will include
Section titled “What published documentation will include”Before a public integration is ready, RevSystems documentation will define:
- supported use cases;
- authentication and authorization;
- versioning and compatibility;
- request and response formats;
- errors, limits, and retry guidance;
- security expectations;
- deprecation policy and changelog.
What to use today
Section titled “What to use today”Configure the available product through Agent Center. For an integration requirement, use Support to describe the business need without sending credentials or private customer data.