Look up a delivery result
Bizgo lets you confirm delivery results in two ways.
| Method | Description | Recommended when |
|---|---|---|
| Webhook (push) | Sent to your server as soon as the result occurs | You need real-time processing |
| Individual lookup (inquiry) | Look up the result of a specific message directly by msgKey | You want to check a specific message, or to cover a webhook you did not receive |
The recommended pattern is to use webhooks as your default and fall back to individual lookups when a webhook does not arrive.
The individual lookup flow
- Store the
msgKeyfrom the send API response - Call the lookup API with the
msgKey - Confirm final delivery from the
reportCode
Lookup window: up to 30 days back
Why storing the msgKey matters
Without the msgKey, you cannot look up the result later, raise an inquiry, or retry.
Always store it in your database from the send response.
JavaScript
const response = await sendMessage(payload);
const msgKey = response.data.data.destinations[0].msgKey;
await db.messages.insert({ msgKey, ref: payload.ref, status: 'sent' });
Interpreting the result code
Use the reportCode in the lookup response to determine final delivery.
Next steps
- Check the API specification → API reference — delivery result lookup
- Batch-look-up results in bulk → Poll for delivery results