Going live
Checks to run before your integration handles real traffic.
There is no test environment. Every key is live, and every send reaches a real WhatsApp user. Work through these checks before launch.
Keys
- Keep keys in a secret manager on your server. Never put a key in a browser, a mobile app, a URL, or a log.
- Use one key for each system that calls Alia.
- Know how to rotate a key: create the new key, deploy it, then revoke the old one in the Console.
Reading
- Follow
nextCursoruntil it isnull. Never assume one page holds everything. - Store each agency's ID from
GET /me. Call it again when an agency seems to be missing: Alia adds new agencies to your key automatically. - URL-encode phone numbers in paths.
Sending
- Ask the CRM user to confirm each message.
- Send an
operationIdwith every message, and reuse it when you retry. - Handle
queued: true. Show the user that the message waits for the contact's consent. - Tell users that a send turns the AI off for that contact.
Errors and logs
- Log the status code, the error
message, and theX-Correlation-Idresponse header. Give Alia support the correlation ID when you report a problem. - Never log keys, phone numbers, or message text.
- Retry
5xxresponses and network errors, waiting longer after each try. Don't retry a4xxresponse until you have changed the request.
First run
- Call
GET /meand check the list of agencies. - List one agency's conversations and page through them.
- Read the messages in one conversation.
- Send one message to a phone you control. Check that it arrives, and that the AI is now off for that conversation.