Authentication
The API's address, its format, and how your software proves who it is.
Address
Every request goes to:
https://api.wa.goupdev.net/v1v1 is the API version. If we ever need to change the API in a way that would break your code, we'll publish it as v2 and keep v1 working.
Format
Requests and answers are JSON. Send Content-Type: application/json with every request that has a body.
Every error answer has the same shape:
{ "error": "Device not found" }See Errors for the full list.
API Key
Create an API Key in the Dashboard (see API Keys) and send it in the Authorization header of every request:
Authorization: Bearer YOUR_API_KEYThe key decides which Tenant you work with. You see and change only that Tenant's Devices, Messages and Webhook.
curl https://api.wa.goupdev.net/v1/devices \
-H "Authorization: Bearer YOUR_API_KEY"| Answer | Why |
|---|---|
401 {"error": "Missing or invalid Authorization header"} | The header is missing, or doesn't start with Bearer . |
401 {"error": "Invalid API key"} | The key is wrong or was revoked. |
Call the API from your server only. Anyone who sees your key can send Messages in your name.