Skip to content
Akedly
Command reference

Meta events

Akedly CLI command reference: Meta events.

meta-events list

Review account-level WhatsApp/Meta configuration and quality webhooks received by Akedly.

When to use

  • Use after Meta template approval/rejection, category, phone-quality, account-review or capability changes.

How it works

  1. The CLI reads /meta-events; results are restricted to the authenticated account and ordered newest first.
  2. Date bounds are strict YYYY-MM-DD; the end day includes the whole server-local day. Pagination defaults to page 1, 20 rows; --all uses limit 100.
  3. The event rows are account-level Meta events, not individual message deliveries.

Prerequisites

  • An authenticated session allowed to read account analytics.

Expected outcome

Event rows and pagination metadata.

Next steps

  • For deliveries, correlate a row’s transactionID or wamid with your internal investigation.
  • Treat recipientPhone and message metadata as private account data.

Usage

sh
akedly meta-events list

Inspect this command offline before preparing an operation:

sh
akedly describe "meta-events list" --output json

Flags

FlagTypeEnum / rangeDescription
--ksaboolean switch—Select the KSA deployment.
--event-typeenumtemplate_status | template_category | phone_quality | account_review | business_capabilityCommand-specific option; see the full command details below. Query parameter: type.
--start-datetext—Command-specific option; see the full command details below. Query parameter: from.
--end-datetext—Command-specific option; see the full command details below. Query parameter: to.
--pageinteger1 to unboundedCommand-specific option; see the full command details below. Query parameter: page.
--limitinteger1 to 100Command-specific option; see the full command details below. Query parameter: limit.
--allboolean switch—Command-specific option; see the full command details below.
--helpboolean switch—Show offline command help.
--outputenumjson | humanSelect JSON or human output.
--fieldsdot-paths—Select comma-separated safe dot paths; apply to each element of a root array.

Authentication, permission and guards

Auth: login. Permission: whatsapp:read.

Server request: GET /meta-events.

Shared server-guard guidance.

Consent

none. --dry-run bypasses confirmation where supported. Destructive: false. Spends money: false. Real send: false.

Retry

idempotent: Idempotent requests retry network errors and HTTP 429/502/503/504, at most 3 tries, waiting for cooldownSeconds, retryAfter or the Retry-After header (otherwise 1 second) between tries, up to 30 seconds; a longer requested wait is returned as the error.

Output

Output: data. API output is pass-through server data unless the command details describe a CLI shape. Local commands, composites and hand-offs use their documented CLI shapes.

Full command details

List your account Meta events. Page defaults to 1 and limit to 20; --all defaults omitted limit to 100 and uses the shared Pagination rules. --start-date and --end-date take strict YYYY-MM-DD; --end-date includes the whole server-local end day. Read-only logins are supported. --start-date must not be after --end-date.

Login 429 guidance.

Pagination rules.

Worked examples

Examples are synthetic illustrations, never live account records. Replace resource IDs with your own authorized resources. Secret values are omitted here; redacted examples illustrate the shape and are not schema-validation fixtures.

Example meta-events list

Review account-level WhatsApp/Meta configuration and quality webhooks received by Akedly.

sh
akedly meta-events list --start-date 2026-10-01 --end-date 2026-10-31

Illustrative response (sensitive values omitted):

json
{
  "status": "success",
  "data": {
    "events": [
      {
        "receivedAt": "2026-10-20T12:00:00.000Z",
        "eventType": "template_status",
        "templateName": "verify_code",
        "templateLanguage": "en",
        "event": "approved",
        "reason": null,
        "previousCategory": null,
        "qualityRating": null
      }
    ],
    "pagination": {
      "currentPage": 1,
      "totalPages": 1,
      "totalCount": 1,
      "limit": 20
    }
  }
}

Additional command forms

sh
akedly meta-events list

Input and file contracts

The contract below describes typed arguments, file formats, validation boundaries and API mappings. Boolean switches take no value; numeric and comma-separated values are each passed as one argument. Read prerequisites and full command details for state-dependent requirements.

Response contract

The report body contains stored report data; field availability varies by report kind and status. Optional template/event/category/reason/quality text fields are nullable; null is normal when a webhook event type does not populate that field.

Common error guidance.

meta-events deliveries

Investigate WhatsApp message delivery states for your account, including failures and fallback outcomes.

When to use

  • Use to determine whether your account’s WhatsApp messages were sent, delivered, read or failed and whether fallback occurred.

How it works

  1. The CLI reads /meta-events/deliveries; results are restricted to the authenticated account and ordered newest first.
  2. Date bounds are strict YYYY-MM-DD; the end day includes the whole server-local day. Pagination defaults to page 1, 20 rows; --all uses limit 100.
  3. The summary counts every delivery status in the date range and deliberately ignores the --status and page filters; delivery rows omit OTP values and API keys but include full recipient phone numbers.

Prerequisites

  • An authenticated session allowed to read account analytics.

Expected outcome

Delivery rows, status totals for the selected date range and pagination metadata.

Next steps

  • For deliveries, correlate a row’s transactionID or wamid with your internal investigation.
  • Treat recipientPhone and message metadata as private account data.

Usage

sh
akedly meta-events deliveries

Inspect this command offline before preparing an operation:

sh
akedly describe "meta-events deliveries" --output json

Flags

FlagTypeEnum / rangeDescription
--ksaboolean switch—Select the KSA deployment.
--statusenumpending | sent | delivered | read | failedCommand-specific option; see the full command details below. Query parameter: status.
--start-datetext—Command-specific option; see the full command details below. Query parameter: from.
--end-datetext—Command-specific option; see the full command details below. Query parameter: to.
--pageinteger1 to unboundedCommand-specific option; see the full command details below. Query parameter: page.
--limitinteger1 to 100Command-specific option; see the full command details below. Query parameter: limit.
--allboolean switch—Command-specific option; see the full command details below.
--helpboolean switch—Show offline command help.
--outputenumjson | humanSelect JSON or human output.
--fieldsdot-paths—Select comma-separated safe dot paths; apply to each element of a root array.

Authentication, permission and guards

Auth: login. Permission: whatsapp:read.

Server request: GET /meta-events/deliveries.

Shared server-guard guidance.

Consent

none. --dry-run bypasses confirmation where supported. Destructive: false. Spends money: false. Real send: false.

Retry

idempotent: Idempotent requests retry network errors and HTTP 429/502/503/504, at most 3 tries, waiting for cooldownSeconds, retryAfter or the Retry-After header (otherwise 1 second) between tries, up to 30 seconds; a longer requested wait is returned as the error.

Output

Output: data. API output is pass-through server data unless the command details describe a CLI shape. Local commands, composites and hand-offs use their documented CLI shapes.

Full command details

List your own WhatsApp delivery records; full recipient phone numbers are private PII, but live OTPs and API keys are excluded. The summary ignores --status and paging and counts the whole --start-date/--end-date range. Page defaults to 1 and limit to 20; --all defaults omitted limit to 100 and uses the shared Pagination rules. --start-date and --end-date take strict YYYY-MM-DD; --end-date includes the whole server-local end day. Read-only logins are supported. --start-date must not be after --end-date.

Login 429 guidance.

Pagination rules.

Worked examples

Examples are synthetic illustrations, never live account records. Replace resource IDs with your own authorized resources. Secret values are omitted here; redacted examples illustrate the shape and are not schema-validation fixtures.

Example meta-events deliveries

Investigate WhatsApp message delivery states for your account, including failures and fallback outcomes.

sh
akedly meta-events deliveries --start-date 2026-10-01 --end-date 2026-10-31

Illustrative response (sensitive values omitted):

json
{
  "status": "success",
  "data": {
    "deliveries": [
      {
        "wamid": "wamid.synthetic.1",
        "transactionID": "tx_synthetic_1",
        "recipientPhone": "+201234567890",
        "messageType": "template",
        "templateName": "verify_code",
        "sendStatus": "success",
        "deliveryStatus": "delivered",
        "sentAt": "2026-10-20T12:00:00.000Z",
        "fallbackTriggered": false,
        "deliveryTimestamp": null,
        "lastStatusUpdate": null,
        "fallbackAt": null,
        "fallbackChannel": null,
        "fallbackSkippedReason": null,
        "byoIntegrationName": null
      }
    ],
    "summary": {
      "pending": 0,
      "sent": 0,
      "delivered": 1,
      "read": 0,
      "failed": 0
    },
    "pagination": {
      "currentPage": 1,
      "totalPages": 1,
      "totalCount": 1,
      "limit": 20
    }
  }
}

Additional command forms

sh
akedly meta-events deliveries

Input and file contracts

The contract below describes typed arguments, file formats, validation boundaries and API mappings. Boolean switches take no value; numeric and comma-separated values are each passed as one argument. Read prerequisites and full command details for state-dependent requirements.

Response contract

recipientPhone is full PII; plaintext OTP and API keys are deliberately not selected. Nullable event/error and fallback fields are normal model states; sentAt is a date. Recipient phone numbers are PII. OTP and API key fields are excluded by the controller projection.

Common error guidance.