Become a Tech Provider | Developer Documentation

Do you need to become a Meta Tech Provider to use ChatArchitect?

For an application that uses the ChatArchitect API, start with your ChatArchitect connection and its issued App key/App ID and Secret. Registering as a Meta Tech Provider is a separate route for a company building its own Meta provider implementation.

Choose the work your application needs to do

Prepare the ChatArchitect API route

1. Identify the business number and the application that will send and receive messages.
2. Complete the agreed ChatArchitect connection and obtain the issued credential pair. The credential guide explains how it differs from a Meta access token.
3. Configure your application using the documented ChatArchitect requests. Keep the credentials on the server that makes those requests.
4. Check an agreed incoming and outgoing example in the intended application. A completed account form alone does not confirm the application's message handling.

If a setup guide asks you to create a Meta app

Identify whether it is describing the ChatArchitect service API or an independent Meta implementation. For the supported ChatArchitect customer route, customers use the ready-made connection; ChatArchitect does not provide partners with a signup implementation to embed in their own site.

Check who is responsible for each part of setup before creating additional assets. If your project really requires an independent Meta provider application, use Meta's current programme documentation for its requirements. This customer guide does not establish provider eligibility or ChatArchitect's own programme designation.