Legacy Cloud API

External Cloud API

Full reference for /external-api — still supported for existing Cloud integrations. New projects should prefer API v1; capabilities below work on both surfaces.

Supported & maintained If your integration already uses /external-api, keep shipping on it. The scenario guides below use legacy paths so you can copy them without migrating first.

Base URL

Production
https://staging-mobile.washeej.com/external-api

Quick path

1
Whitelist your IPDeveloper Tools → IP Whitelist (mandatory for API key authentication).
2
Copy credentialsclient-id and client-secret from Developer Tools.
3
PingAuthenticated check: confirms credentials, whitelisted IP and the IP Washeej sees. If the IP is not whitelisted yet, the 401 message shows it.
4
SendPOST /inbox/send-message or POST /inbox/send-template-message with an explicit whatsapp_account_id.
GET /ping Credentials required https://staging-mobile.washeej.com/external-api/ping

Authenticated connectivity check (needs credentials and a whitelisted IP). Returns the IP Washeej sees. If your IP is not whitelisted yet, the 401 response message shows that IP instead.

cURL
curl -H "client-id: YOUR_CLIENT_ID" \
     -H "client-secret: YOUR_CLIENT_SECRET" \
     https://staging-mobile.washeej.com/external-api/ping

Scenario map (legacy paths)

NeedLegacy endpointKey fieldsDeep guide
Text inside 24h window POST /inbox/send-message message, whatsapp_account_id Session Window
PDF / image / video / audio (session) POST /inbox/send-message multipart document / image / video / audio Messages · Session Media
CTA / list / location / product POST /inbox/send-message cta_url_id, interactive_list_id, latitude… Messages · Interactive
Business-initiated / outside 24h POST /inbox/send-template-message template_id, body_variables Templates
Native PDF file via template POST /inbox/send-template-message header_media_url or header_media_file Template Media Headers
URL inside template text POST /inbox/send-template-message body_variables[0] = HTTPS URL Dynamic Invoice Link
OTP / login code POST /inbox/send-template-message AUTHENTICATION + one 4–8 digit code Authentication OTP
Pick the correct number all send endpoints whatsapp_account_id or from_number Channel Selection

End-to-end checklist: Integration Playbook (same product rules; swap paths to /external-api/...).

Webhooks

Register and manage webhooks on the unified API v1 surface (Webhooks docs — events cover Cloud messages sent through this legacy API as well.

Migrate when ready

No forced deadline. Path mapping: Migrate to API v1.