Auphere Partner API · Reference
/ v0.1
Troubleshooting
The errors you are most likely to hit, what causes them and what to do.
Authentication and scopes
| Symptom | Likely cause | Fix |
|---|---|---|
401 Invalid API key | Typo, revoked key, or expired rotation grace | Check the key end to end; ask for a rotation if in doubt |
403 API key lacks required scope: broadcasts | Your key can provision but not send | Ask for a key with the broadcasts scope |
403 … cannot be used from a tenant-scoped API key | You are using a key restricted to one client on a partner-level endpoint | Use your partner key |
403 Partner is suspended | Your partner account is suspended | Contact us |
Provisioning
| Symptom | Likely cause | Fix |
|---|---|---|
422 Faltan datos del negocio… | A blueprint placeholder has no value | Send the keys the detail names in agent.placeholders |
422 … la whitelist quedó vacía | Admin-only vertical with no usable admin phone | Send at least one E.164 number with 7+ digits |
404 Unknown client reference | The client was never provisioned, or the ref has a typo | Provision it first; refs are exact-match and per-partner |
| Credentials changed unexpectedly | You called POST /clients to read state | Use GET /v1/partners/clients/{ref} — provisioning rotates credentials |
WhatsApp connection
| Symptom | Likely cause | Fix |
|---|---|---|
400 Meta rejected the code | The code expired or was already used | Reopen the popup and send the fresh code immediately |
409 on connect | The number is already linked to another workspace | Contact us to move it |
| Connected, but the agent stays silent | tenant_status is still provisioning | Read activation_blocked_reason: no_agent → check provisioning; operator_review → we activate it |
| Connected, agent answers nobody | Admin-only vertical with the wrong phones whitelisted | Check GET .../admins matches the numbers actually writing |
Campaigns
| Symptom | Likely cause | Fix |
|---|---|---|
409 whatsapp_not_connected | The client has no active number yet | Finish the signup first |
422 … is PENDING, not APPROVED | The template is not approved in that client’s account | Wait for Meta, or pick another template |
422 … positional parameters | The template uses {{1}} instead of {{cliente}} | Recreate it in Meta with named parameters |
413 | More recipients than your cap | Split the send or ask us to raise the cap |
429 | Too many sends per minute | Space them out or ask for a higher limit |
Recipients come back rejected | Opt-out, or a phone we could not normalise | Read reason per recipient — opt-outs are final and must be respected |
| Template list is empty | Nothing APPROVED in that client’s account yet | The initial set is created with our help after signup |
Still stuck?
Send us the detail string, the endpoint and roughly when it happened. Every call is audited on our side, so with that we can trace the exact request. Get in touch.