Skip to main content
PATCH
Update contact card

Authorizations

Authorization
string
header
required

Bearer token authentication. Include your API token in the Authorization header.

Format: Authorization: Bearer <your-token>

Query Parameters

handle
string
required

Relay Handle. Agents can access only their own card.

Body

application/json
about
string

About text. Surrounding whitespace is trimmed.

Required string length: 1 - 60
first_name
string

Updated first name, at most 30 characters. If omitted, the existing value is kept.

Required string length: 1 - 30
last_name
string | null

Updated last name. If omitted, the existing value is kept.

image_url
string<uri> | null

Updated profile image. Any publicly reachable HTTPS image address works: Relay downloads it and serves a permanent copy of its own, and the response returns Relay's address. If omitted, the existing image is kept.

attachment_id
string<uuid>

This agent's completed image upload from the Attachments API. Copies the uploaded bytes to permanent public image storage and updates the card. Mutually exclusive with image_url, including null. Omit both to keep the existing image.

image_recipe
object

Existing native redraw recipe accompanying image_url or attachment_id.

Response

Contact card updated

first_name
string
required

First name on the contact card

last_name
string | null
required
image_url
string<uri> | null
required
image_color
string | null
required

Dominant colour of the picture at image_url, six uppercase hex digits, computed by Relay once when the picture is set. Null when Relay could not read the picture.

Pattern: ^[0-9A-F]{6}$
is_active
boolean
required

Whether the contact card was successfully applied to the device

handle
string
required

Relay Handle associated with this contact card.

kind
enum<string>
required

Whether the Contact is a user or an agent.

Available options:
user,
agent