Developer API

Use the AvenPing HTTP API to send WhatsApp messages, list templates and flows, and download media directly from your own backends and automations. WhatsApp access is provided through AvenPing, an official Meta Business Partner, using credentials linked to your workspace.

Current version

All endpoints are served under the v2 path prefix (/v2).
The previous v1 base path is fully deprecated; requests to /v1 endpoints are no longer supported and will not return data.

Where to go next

Page	What you will find
Authentication & requirements	How to get a token, plan rules, and your first successful request (GET /v2/me)
HTTP API v2 Overview	Conventions, auth rules, errors, and links to each endpoint group
Postman collection	Importable collection, variables, and how to publish docs in Postman

Quick facts

Topic	Detail
Production base URL	https://api.avenping.com (append paths such as /v2/health)
Public checks (no token)	GET /v2/health, GET /v2/version
Authentication	Authorization: Bearer <token> or X-API-Token: <token> (from Settings → API Settings)
Plans	Premium or Enterprise, subscription active
JSON bodies	Content-Type: application/json, max 2 MB

Capability map (v2)

• Public & meta — GET /, GET /v2/health, GET /v2/version (no token)
• Account — GET /v2/me for user, WABA id, and all phoneNumberId values (plus defaultPhoneNumberId when only one line exists)
• Templates — list, fetch by name, send and test-send (with phoneNumberId checks)
• Forms (flows) — list from Meta, search in AvenPing DB, fetch flow by ID
• Media — stream download by Meta media ID
• Messages — text, media, location, interactive, plus smart POST /v2/messages/send
• Webhooks — set or clear your outbound webhook URL and code (same data as Settings → Webhooks)

Start from the HTTP API v2 Overview for global rules, then open the group you need.