Didn't Answer Button

PATCHhttps://app.aisync.link/api/disposition/{id}/status

curl --request PATCH \
  --url https://app.aisync.link/api/disposition/MQ==/status \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
  "enabled": true
}'

{
  "data": {
    "id": "MQ==",
    "status": "Default",
    "didnt_answer_button_enabled": true
  },
  "message": "Status updated successfully.",
  "success": true
}

Didn't Answer Button#

Same as the Setup Didn't Answer Button column. Default means on. Active means off. Only one disposition per company can be on. Turning this one on clears the flag on the others. Omit the body to flip the current value.

PATCH /api/disposition/{id}/didnt-answer-button does the same thing.

Authorizationstringheaderrequired

Bearer token in the format: Bearer {access_token}

idstringpathrequired

Base64 disposition id from List Dispositions

enabledbooleanbody

true turns the button on. false turns it off. Optional

curl --location --request PATCH 'https://app.aisync.link/api/disposition/MQ==/status' \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Bearer {{bearer_token}}' \
  --data '{
    "enabled": true
  }'

data.statusstring

Default when the button is on, otherwise Active

data.didnt_answer_button_enabledboolean

Whether the Didn't Answer button is on

PreviousCall Status Options Next Default Option

Didn't Answer Button

curl --request PATCH \
  --url https://app.aisync.link/api/disposition/MQ==/status \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
  "enabled": true
}'

{
  "data": {
    "id": "MQ==",
    "status": "Default",
    "didnt_answer_button_enabled": true
  },
  "message": "Status updated successfully.",
  "success": true
}