Managing Webhooks | Developer Documentation

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 registration and event examples.

Identify who owns the receiver

For a ready-made CRM or help desk, check where that integration sends incoming chats and shows delivery results. Confirm the affected connection and receiver with support before adding a custom callback alongside an established integration.

For your own application, identify the HTTPS endpoint, its owner and the business connection it serves. Follow the preparation guide to set up and register it using the documented ChatArchitect workflow.

Check the two directions separately

1. Use a permitted test contact and record the connected business number and a distinctive test message.
2. Check that an incoming customer message reaches the intended receiver and application conversation.
3. Send an appropriate reply and keep its response reference.
4. Check the later result against that same attempt, using the delivery-status guide.

The quick start documents submitted, failed, sent, delivered and read results. A successful send response does not show that a later event reached your receiver. Keep enough references to distinguish two separate attempts.

Change an established callback deliberately

Identify the affected connection, current destination and supported way to restore it. Confirm who will handle the next incoming messages and outgoing results. After the change, repeat the incoming-message and outgoing-result checks. If delivery is incomplete, record the missing stage and ask support to confirm the callback mapping and contract.

Transport authentication, retry timing, acknowledgement rules and every optional Meta management event are not established by the basic quick-start examples. Confirm those rules before relying on them in your application.

Separate Meta subscriptions from customer callbacks

The Meta developer reference below describes app subscriptions to WhatsApp business accounts. A regular ChatArchitect customer uses the documented ChatArchitect receiver workflow. Its App key/Secret authenticates the documented API requests; it does not by itself define how to verify an incoming callback.

Provider implementation reference

For a separate Meta provider implementation, consult the Meta developer reference for Managing Webhooks. That reference uses its own application, account and permission context. Use the customer workflow above for ChatArchitect.