The customer API serves one client business and its locations. Public documentation does not establish entitlement for this account.

Before you beginHave the account owner confirm API availability and authorize the intended operations. Keep keys outside this public documentation hub.

Step by step

  1. Use the complete customer reference at doc.mysaas.site and the base address it documents.
  2. Confirm the credential belongs to the intended client; agency credentials have a broader audience.
  3. Use the documented x-api-key header from a server-side secret store.
  4. Begin with an authorized business lookup and resolve locations from that business’s result.
  5. Test one permitted read and verify the returned business and location identifiers.
  6. Handle failures without logging keys or full customer payloads. Approve writes and review invitations separately.
  7. Confirm the customer plan includes Automation Features and that the authorized Owner can access Settings → Automate. The provider documents the business key as business-bound; an agency key has broader authority and belongs in a separate integration.
  8. Treat the key as a password. The provider currently documents no self-service rotation or revocation control; if exposure is suspected, stop using the affected integration and follow the support recovery process rather than assuming a replacement key is available.
  9. Handle HTTP 429 without blindly retrying. The provider documents a limit of 1,000 calls per hour for a client key; use the returned limit/reset headers and a bounded retry policy. Confirm current limits and subscription errors in the official reference before launch.

Expected result

The integration can trace one authorized read to the correct client business and location.

Troubleshooting

  • A missing account feature must be resolved with the owner rather than an agency-key workaround.
  • The vendor currently documents no platform key rotation or revocation control; exposed keys require support.
  • Do not assume every documented operation is available to every customer plan.

Supporting documentation

These links open the provider’s documentation. Availability and permissions depend on your account.

More guides

Choose the correct RevPro API audienceKeep customer business/location access separate from agency integration access and verify entitlement first.
Assess API and MCP automation boundariesAuthorize the task and audience before connecting an assistant.