Update a Call activity | Close | Developer API Documentation

curl -X PUT https://api.close.com/api/v1/activity/call/id/ \
     -H "Content-Type: application/json" \
     -u "<CLOSE_API_KEY>:" \
     -d '{
  "note_html": "<body><p>This is some new call note.</p></body>",
  "outcome_id": "outcome_031uY9IKV1JxfNKM9n2qCw"
}'

{
  "_type": "Call",
  "activity_at": "2013-02-01T00:51:33+00:00",
  "contact_id": "cont_q4xYmlGhA3060dEl0NDJuHRxPMuVjqLn30AFSzh1fRk",
  "created_by": "user_N6KhMpzHRCYQHdn4gRNIFNN5JExnsrprKA6ekxM63XA",
  "date_created": "2013-02-20T06:34:33.637000+00:00",
  "date_updated": "2013-02-20T06:34:35.656000+00:00",
  "id": "acti_Ay0QqN91HKAHVQUesISYV8QlhDobGfWb1Ui3TE75pJR",
  "lead_id": "lead_s6vHFTK1TSRoH6otXOexWDO9jM4xyb1kELHDoU7Fdsp",
  "organization_id": "orga_RbREgmiiwcr1w2b4cOnCMQaQPSIFxMqAD2Dh243uxcH",
  "outcome_id": "outcome_031uY9IKV1JxfNKM9n2qCw",
  "source": "Close.io",
  "status": "completed",
  "updated_by": "user_N6KhMpzHRCYQHdn4gRNIFNN5JExnsrprKA6ekxM63XA",
  "user_id": "user_N6KhMpzHRCYQHdn4gRNIFNN5JExnsrprKA6ekxM63XA",
  "users": [],
  "call_method": "regular",
  "cost": "2",
  "direction": "outbound",
  "disposition": "answered",
  "duration": 10,
  "local_country_iso": "US",
  "local_phone": "+16505556666",
  "local_phone_formatted": "+1 650-555-6666",
  "note": "This is some new call note.",
  "note_html": "<body><p>This is some new call note.</p></body>",
  "phone": "+16503334444",
  "remote_country_iso": "US",
  "remote_phone": "+16503334444",
  "remote_phone_formatted": "+1 650-333-4444"
}

Most commonly used to update note_html or outcome_id. Some fields (status, duration, direction) cannot be updated for internal calls made through Close’s VoIP system.

note_html and note: setting one overwrites the other. If both are provided, note_html takes precedence. note_html supports rich-text HTML; note is plaintext only.

Most commonly used to update `note_html` or `outcome_id`. Some fields (`status`, `duration`, `direction`) cannot be updated for internal calls made through Close's VoIP system. **`note_html` and `note`**: setting one overwrites the other. If both are provided, `note_html` takes precedence. `note_html` supports rich-text HTML; `note` is plaintext only.

Authentication

AuthorizationBasic

Basic authentication of the form Basic <base64(username:)>.

AuthorizationBearer

Bearer authentication of the form Bearer <token>, where token is your auth token.

Path parameters

idstringRequired

Request

This endpoint expects an object.

activity_atdatetime or nullOptional

contact_idstring or nullOptional

conversation_type_idstring or nullOptional

custom_fieldsmap from strings to any or nullOptional

durationinteger or nullOptional<=604800

lead_idstring or nullOptional

notestring or nullOptional

note_htmlstring or nullOptional

outcome_idstring or nullOptional

phonestring or nullOptional

Phone number in E.164 format

playbook_idstring or nullOptional

quality_infostring or nullOptional

recording_urlstring or nullOptionalformat: "uri"

statusenumOptional

user_idstring or nullOptional

voicemail_urlstring or nullOptionalformat: "uri"

Response

Successful response

_typestring

activity_atdatetime or null

contact_idstring or null

created_bystring or null

date_createddatetime

date_updateddatetime

idstring

lead_idstring or null

organization_idstring

outcome_idstring or null

sourceenum

Source of a phone call or an SMS message.

Allowed values:

statusenum

Indicates the status of the call.

A brand new call starts off as Created. Then, if it’s answered, its status changes to InProgress. Finally, once either party hangs up, the status is updated to Completed.

Of course, that’s the happy path. There are other scenarios in which the call assumes a different status. Read the comments below for details.

Also, see possible call status values for Twilio [0] and, for historical calls, Plivo [1] from which the statuses below are derived.

[0] https://www.twilio.com/docs/voice/api/call-resource#call-status-values [1] https://www.plivo.com/docs/voice/detailed-reference/xml/introduction/request#call-status

Indicates the status of the call. A brand new call starts off as `Created`. Then, if it's answered, its status changes to `InProgress`. Finally, once either party hangs up, the status is updated to `Completed`. Of course, that's the happy path. There are other scenarios in which the call assumes a different status. Read the comments below for details. Also, see possible call status values for Twilio [0] and, for historical calls, Plivo [1] from which the statuses below are derived. [0] https://www.twilio.com/docs/voice/api/call-resource#call-status-values [1] https://www.plivo.com/docs/voice/detailed-reference/xml/introduction/request#call-status

updated_bystring or null

user_idstring or null

userslist of strings

created_by_namestring or null

sequence_idstring or null

sequence_namestring or null

sequence_subscription_idstring or null

updated_by_namestring or null

user_namestring or null

Errors

400

Bad Request Error

401

Unauthorized Error

404

Not Found Error