Skip to main content
POST
/
v1
/
webhooks
/
calls
Create a new webhook for calls
curl --request POST \
  --url https://api.quo.com/v1/webhooks/calls \
  --header 'Authorization: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "url": "https://example.com/",
  "events": [],
  "resourceIds": [
    "PN1234"
  ],
  "userId": "US123abc",
  "label": "my webhook label",
  "status": "enabled"
}
'
{
  "data": {
    "id": "WHabcd1234",
    "userId": "US123abc",
    "orgId": "OR1223abc",
    "label": "my webhook label",
    "status": "enabled",
    "url": "https://example.com/",
    "key": "example-key",
    "createdAt": "2022-01-01T00:00:00Z",
    "updatedAt": "2022-01-01T00:00:00Z",
    "deletedAt": "2022-01-01T00:00:00Z",
    "events": [],
    "resourceIds": [
      "PN1234"
    ]
  }
}

Authorizations

​
Authorization
string
header
required

Body

application/json
​
url
string<uri>
required

The endpoint that receives events from the webhook.

Example:

"https://example.com/"

​
events
enum<string>[]
required
Available options:
call.completed,
call.ringing,
call.recording.completed
​
resourceIds

The unique identifiers of the phone numbers associated with the webhook.

Pattern: ^PN(.*)$
Example:
["PN1234"]
​
userId
string

The unique identifier of the user that creates the webhook. If not provided, default to workspace owner.

Pattern: ^US(.*)$
Example:

"US123abc"

​
label
string

Webhook's label

Example:

"my webhook label"

​
status
enum<string>
default:enabled

The status of the webhook.

Available options:
enabled,
disabled
Example:

"enabled"

Response

Success

​
data
object
required