Search Results

Use the credentials for your ChatArchitect connection A custom service connected through ChatArchitect uses the App key/App ID and Secret supplied by ChatArchitect. The API quick start calls these credentials APP_ID and APP_SECRET and uses them as the Basic ...

Match the business number to the intended integration Keep a clear record of the business phone number your team will use with ChatArchitect. The business number, its display name, the selected WhatsApp account and the recipient's number describe different par...

Check billing for your ChatArchitect WhatsApp connection For WhatsApp messaging through ChatArchitect, the customer pays ChatArchitect under the applicable plan and separate commercial terms. Meta's provider credit-line documentation describes an internal plat...

Manage the receiver for your ChatArchitect connection A custom application uses a receiver to get incoming customer messages and later results of outgoing attempts from ChatArchitect. Start with the webhook overview and the API quick start for the documented r...

Meta provider reference: provider application registration and review. This imported technical reference describes a separate Meta developer workflow. A regular ChatArchitect connection uses the supplied setup and, for a custom application, the issued App key/...

Meta provider reference: starting a Meta Solution Partner implementation. This imported technical reference describes a separate Meta developer workflow. A regular ChatArchitect connection uses the supplied setup and, for a custom application, the issued App k...

Meta provider reference: measurement-partner documentation. This imported technical reference describes a separate Meta developer workflow. A regular ChatArchitect connection uses the supplied setup and, for a custom application, the issued App key/App ID and ...

Meta provider reference: a Meta provider programme upgrade. This imported technical reference describes a separate Meta developer workflow. A regular ChatArchitect connection uses the supplied setup and, for a custom application, the issued App key/App ID and ...

Meta provider reference: review of a Meta developer application. This imported technical reference describes a separate Meta developer workflow. A regular ChatArchitect connection uses the supplied setup and, for a custom application, the issued App key/App ID...

Meta provider reference: partner-initiated account creation. This imported technical reference describes a separate Meta developer workflow. A regular ChatArchitect connection uses the supplied setup and, for a custom application, the issued App key/App ID and...

Meta provider reference: a joint Meta partner solution. This imported technical reference describes a separate Meta developer workflow. A regular ChatArchitect connection uses the supplied setup and, for a custom application, the issued App key/App ID and Secr...

Meta provider reference: embedded creation of a Meta partner solution. This imported technical reference describes a separate Meta developer workflow. A regular ChatArchitect connection uses the supplied setup and, for a custom application, the issued App key/...

Meta provider reference: configuration of Meta Multi-Solution Conversations. This imported technical reference describes a separate Meta developer workflow. A regular ChatArchitect connection uses the supplied setup and, for a custom application, the issued Ap...

Meta provider reference: a provider-led business-verification process. This imported technical reference describes a separate Meta developer workflow. A regular ChatArchitect connection uses the supplied setup and, for a custom application, the issued App key/...

Meta provider reference: Meta Pixel tracking in a provider setup. This imported technical reference describes a separate Meta developer workflow. A regular ChatArchitect connection uses the supplied setup and, for a custom application, the issued App key/App I...

Meta provider reference: registration of a customer number by a Meta provider. This imported technical reference describes a separate Meta developer workflow. A regular ChatArchitect connection uses the supplied setup and, for a custom application, the issued ...

Meta provider reference: the historical Meta On-Behalf-Of ownership model. This imported technical reference describes a separate Meta developer workflow. A regular ChatArchitect connection uses the supplied setup and, for a custom application, the issued App ...

Meta provider reference: migration of a number in a Meta provider implementation. This imported technical reference describes a separate Meta developer workflow. A regular ChatArchitect connection uses the supplied setup and, for a custom application, the issu...