Skip to main content
PATCH
Update the metadata of a pre-order
  • Credential: an API key of the account that owns the pre-order.
  • Line-scoped keys: the list of lines of a line-scoped key is not applied.
  • Idempotency-Key: not honored. See Operations that honor the key.
  • Events: none. The events sent after the call carry the new metadata. The call works in every status.
  • Body: required. It has one field, metadata, and is sent with Content-Type: application/json. The merge rules are in Metadata.

Errors

The errors that every operation shares are in Errors.

Authorizations

Authorization
string
header
required

An API key created in the iSnap dashboard, or a trial key, sent as Authorization: Bearer <key>. An API key starts with isnap_live_ or isnap_test_; both act on the same account, lines and billing. A trial key acts on its trial only.

Path Parameters

id
string<uuid>
required

Id of the pre-order: the UUID returned in id by POST /v1/pre-orders.

Example:

"7f3b9c1e-2a4d-4f6b-8e0a-5c1d2e3f4a5b"

Body

application/json

Metadata to merge into the metadata of a pre-order.

metadata
object
required

Keys to merge into the metadata of the pre-order. A key with a value is set, and a key with null is deleted. At most 20 keys and 8,192 bytes once serialized as JSON.

Example:

Response

The pre-order, with its metadata after the merge.

success
enum<boolean>
required

Always true on a success response.

Available options:
true
data
object
required

A pre-order: an order for one rented iMessage line.

trace_id
string
required

Trace id of the request that produced this response: 32 lowercase hexadecimal characters. Quote it when you report a problem to iSnap.

request_id
string
required

Id of the request that produced this response: req_ followed by 25 letters or digits.