All Messaging API requests are authenticated using a network API key passed in the request header.Documentation Index
Fetch the complete documentation index at: https://docs.aui.io/llms.txt
Use this file to discover all available pages before exploring further.
Network API Key
Your network API key is provided during onboarding or can be obtained from your AUI account manager through the AUI Console.Required Headers
Every request must include:| Header | Description | Example |
|---|---|---|
x-network-api-key | Your network API key | your-network-api-key |
Content-Type | Request body format (for POST requests) | application/json |
cURL
WebSocket Authentication
For WebSocket connections, pass the API key as a query parameter:Invalid credentials will close the WebSocket connection with close code
1008 (Policy Violation).CLI Authentication
The AUI CLI supports multiple authentication methods:Error Responses
Authentication failures return a401 status:
Security Best Practices
Keep keys server-side
Never expose your network API key in client-side code. All API calls should be proxied through your backend.
