WhatsApp Cloud API Skill

Use this skill to run WhatsApp Business Platform Cloud API operations through uxc + OpenAPI.

Reuse the uxc skill for shared execution, auth, and error-handling guidance.

Prerequisites

• - uxc is installed and available in PATH.
• Network access to https://graph.facebook.com/v25.0.
• Access to the curated OpenAPI schema URL:

• - A Meta app and WhatsApp Business account with Cloud API access.
• A valid system-user or app access token that can call the target WhatsApp assets.
• At least one phone_number_id, and for phone number listing, the related waba_id.

Scope

This skill covers a compact Cloud API request/response surface:

• - phone number listing
• phone number metadata reads
• business profile reads and updates
• outbound message sends

This skill does not cover:

• - inbound webhook receiver runtime
• template lifecycle management
• embedded signup or broader business onboarding flows
• media upload/download lifecycle
• the full WhatsApp Business Platform surface

API Version

This skill is pinned to Graph API v25.0, based on current Meta developer examples at implementation time. Keep the base URL versioned:

• - INLINECODE9

If Meta deprecates this version later, the wrapper should be revised in a follow-up update rather than assuming unversioned compatibility.

Authentication

WhatsApp Cloud API uses Authorization: Bearer <access_token>.

Configure one bearer credential and bind it to the versioned Graph API base path:

CODEBLOCK0

Validate the active mapping when auth looks wrong:

CODEBLOCK1

Core Workflow

1. 1. Use the fixed link command by default:

1. 2. Inspect operation schema first:

1. 3. Prefer read/setup validation before writes:

1. 4. Execute with key/value or positional JSON:

Operation Groups

Asset Discovery

• - INLINECODE22
• INLINECODE23

Business Profile

• - INLINECODE24
• INLINECODE25

Messaging

• - INLINECODE26

Guardrails

• - Keep automation on the JSON output envelope; do not use --text.
• Parse stable fields first: ok, kind, protocol, data, error.
• INLINECODE33 is a high-risk write. Require explicit user confirmation before execution.
• Message delivery is still constrained by WhatsApp conversation rules, template approval rules, recipient opt-in expectations, and account policy state. Auth success does not imply a send is allowed.
• This v1 skill does not manage media uploads. If you send image or document content, use already hosted URLs or existing asset references as allowed by the platform.
• Webhook subscription and verification are intentionally documented only. This skill does not configure a receiver runtime.
• Business profile update fields are partial. Only send the fields you intend to change.
• INLINECODE36 is equivalent to uxc https://graph.facebook.com/v25.0 --schema-url <whatsapp_openapi_schema> <operation> ....

References

• - Usage patterns: INLINECODE38
• Curated OpenAPI schema: INLINECODE39
• WhatsApp Cloud API docs: https://developers.facebook.com/docs/whatsapp/cloud-api
• Graph API access tokens: https://developers.facebook.com/docs/graph-api/overview/access-tokens/