Authentication
Ce contenu n’est pas encore disponible dans votre langue.
Use the credential required by the service you are calling. API keys are created in Security → API Key in the portal and are only displayed in full once.
Client API
Section titled “Client API”The preferred format is the standard Bearer header:
Authorization: Bearer <PORTAL_API_KEY>Existing integrations can continue to send the legacy pair:
x-client-email: developer@example.comx-portal-api-key: <PORTAL_API_KEY>POST /auth/portal/login validates portal credentials; it does not issue a token or create a session. Do not call it as part of normal API authentication.
Outbound API
Section titled “Outbound API”X-APIKEY-SECRET-AI4CALL: <OUTBOUND_API_KEY>Use this only with https://outcall.ai4call.com.
Public RAG API
Section titled “Public RAG API”Authorization: Bearer <RAG_API_KEY>Use this only with https://rag.ai4call.com.
Assistant identifiers
Section titled “Assistant identifiers”An assistant has a public assistantId and a confidential assistantApiKey. Prefer the public ID when an endpoint supports it. Treat assistantApiKey as a secret: never return it from your own APIs or include it in telemetry.