Update metadata

Used to store metadata or custom identifiers on the request.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…

Adds custom metadata to the request. Metadata fields key-value pairs of type string.

Field names that start with $ are reserved for special use.

The following field names are used for Working With Custom Identifiers:

  • $email
  • $internalId
  • $phoneNumber

In addition, you can override a specific integration's identifier by setting a field called '${integrationType}. This will work regardless if the integration was designed to use email or any other identifier.

Example: To set the userId 123-456 for use with Google BigQuery integration, set the following field name:

"customFields": {
  "$googlebq": "123-456"
}

If you set a value for one or more of these fields, they will be used by integrations when fulfilling requests.

Setting an empty value

Marking an identifier as empty (i.e. value does not exist) can be done by setting "x-none" as the value.

Body Params
string
required
length ≥ 1

TicketID of the request to update status for

customFields
object
required

A collection of metadata fields to add to the request. Use the following special names to set custom identifiers: $phoneNumber, $internalId

boolean

Used for testing; When Test is true, the change will not actually apply

Headers
string
enum
Defaults to application/json-patch+json

Generated from available request content types

Allowed:
Responses
200

Success

400

Bad Request

401

Unauthorized

Language
Credentials
Header
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here!