The vendor documents separate customer and agency MCP endpoints backed by their respective API credentials.

Before you beginConfirm account entitlement, approved assistant access and the exact read or write task. Do not paste credentials into public examples.

Step by step

  1. Choose customer or agency scope based on the data owner and task.
  2. Read the matching complete API reference before enabling an assistant to call operations.
  3. Use the documented MCP endpoint for that audience and store its credential securely.
  4. Start with a controlled authorized read; inspect which account and location the result represents.
  5. Require separate authorization for invitations, public replies, billing changes and other writes.
  6. Assign an owner to review access, usage and unexpected actions. Establish the support path for credential exposure.

Expected result

The automation has a defined audience, bounded task and explicit write permissions.

Troubleshooting

  • An assistant connection is not blanket approval for every API operation.
  • Do not use an agency connector to bypass unavailable customer tools.
  • Keep source-reference examples distinct from live API results.

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.
Prepare a RevPro customer API connectionVerify audience, business identity and supported operations before a read.