Skip to main content
The REST API accepts an API key in the x-api-key header, the x-api-key query parameter, or the Authentication header. Create and rotate API keys from your Rapida project credentials. 
curl --request POST "https://assistant-01.in.rapida.ai/v1/talk/create-phone-call" \
  --header "Content-Type: application/json" \
  --header "x-api-key: $RAPIDA_API_KEY" \
  --data '{
    "assistant": {
      "assistantId": "2227823180112723968",
      "version": "latest"
    },
    "toNumber": "+14155550123"
  }'

curl --request POST "https://assistant-01.in.rapida.ai/v1/talk/create-phone-call?x-api-key=$RAPIDA_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
    "assistant": {
      "assistantId": "2227823180112723968",
      "version": "latest"
    },
    "toNumber": "+14155550123"
  }'

curl --request POST "https://assistant-01.in.rapida.ai/v1/talk/create-phone-call" \
  --header "Content-Type: application/json" \
  --header "Authentication: $RAPIDA_API_KEY" \
  --data '{
    "assistant": {
      "assistantId": "2227823180112723968",
      "version": "latest"
    },
    "toNumber": "+14155550123"
  }'

​
Authentication parameters

​
x-api-key
string
API key sent as a request header.
​
x-api-key
string
API key sent as a query parameter.
​
Authentication
string
API key sent as an Authentication header.
Use one authentication method per request. Prefer headers for server-side integrations because query parameters can appear in logs.

​
Optional headers

​
x-auth-id
string
Optional user identifier to propagate with the request.
​
x-client-source
string
Optional client source identifier. SDK clients send this automatically.

​
Base URLs

Use the endpoint for the region where your assistant API is hosted. 
https://assistant-01.in.rapida.ai
https://assistant-01.us.rapida.ai
Do not expose project API keys in browser or mobile clients. Send REST API requests from a trusted backend service.