WhatsApp Business Message History Events API | Developer Documentation
A worksheet for one WhatsApp sending attempt
Copy the table into your own incident record when a sending tool and your application show different progress. Fill it from available evidence, then hand the unresolved stage to its owner. This is a support worksheet, not a ChatArchitect API schema or a promise that a complete history can be retrieved. Use the delivery-result guide to interpret statuses and verify the mapping between request and event references.
Copy and fill this worksheet
| Stage | Evidence to attach | Observed result or gap |
|---|---|---|
| Application prepares the job | Tool/application, job or attempt reference, selected connection, recipient and preparation time as recorded. | Was the intended job prepared? Mark unavailable records as unknown. |
| Application submits the request | Available request record and its exact response, with the issuing system for each reference. | What response belongs to this request? |
| Receiver gets a result | The received event and receipt record; retain any source time exactly as supplied. | Which event is verified to belong to the attempt? Who can establish a missing mapping? |
| Application processes the result | Available processing record, destination conversation/job and resulting display. | Was this event applied to the intended record? Name the owner of any missing evidence. |
Keep secret credentials out of the worksheet. Label each recorded clock and time zone; where the representation is unknown, retain the raw value and mark it unknown. Use the API Quick Start for documented request and callback examples.
Worked example: correlation remains unresolved
This example is entirely fictional. JOB-EXAMPLE-7, RESP-EXAMPLE-A and EVENT-EXAMPLE-B are invented worksheet labels, not valid API values or a correlation rule. The times below are fictional local log times labelled UTC.
| Stage | Recorded observation | Conclusion supported by this record |
|---|---|---|
| Preparation | 09:00:00 UTC: JOB-EXAMPLE-7 prepared for the permitted test contact on the chosen connection. | A job was prepared. |
| Submission | 09:00:02 UTC: its send response was recorded as submitted; reference recorded as RESP-EXAMPLE-A. | This request was accepted into the sending queue. |
| Receipt | 09:00:05 UTC: receiver recorded a sent event for the same destination; reference recorded as EVENT-EXAMPLE-B. | An event reached the receiver. Its mapping to JOB-EXAMPLE-7 has not been established. |
| Processing | The conversation still displays queued; no processing record for this particular event is available. | Neither successful application of this event nor its association with the job has been proved. |
The completed worksheet leaves two gaps: the integration's reference mapping and evidence of processing the mapped event. The application owner can supply those records or mark them unavailable. A similar recipient and time does not fill either gap; this example does not establish delivery to the recipient.
Hand over the unresolved row
Attach the filled worksheet and the relevant sanitized source records. State the observed mismatch, which association is verified, what remains unknown and who can check it. Use the receiver checklist when receipt or handling needs investigation. Keep the original attempt unresolved until the evidence supports an outcome; the worksheet alone is not a reason to send the message again.
No comments to display
No comments to display