Skip to main content
Auth. HMAC v1 or bearer token — see Authentication. Status. Live · Idempotent: No.
Builds a vCard from the supplied fields and sends it as a tappable contact bubble in the chat. The recipient sees a normal contact card they can tap to save. Works in both DMs and groups. Wrap the card details in a top-level contact object (or supply raw vcard_text). Include at least one identifying field inside contactfull_name, given_name, family_name, organization, or a non-empty phones / emails. This is independent of the line’s own saved contact card — use share-contact-info to share the line’s “Me” card.

Addressing the recipient

Pick the form that matches your state:
  1. By chat idPOST /api/v1/chats/{id}/send-contact once a chat exists.
  2. By phone — pass to in the request body. Use this on first-touch when no chat exists yet; Chert resolves or creates the chat in-line.

Request

POST /api/v1/chats/{id}/send-contact

Response

Path parameters

string
Chat identifier (ch_…). Omit and use body.to for first-touch recipients with no chat yet.

Body

Provide either a contact object (canonical) or a raw vcard_text string.
string
Recipient phone in E.164 format. Use instead of the {id} path segment when no chat exists yet. Ignored when {id} is supplied.
object
Canonical contact wrap. Must include at least one identifying field.
string
Raw vCard payload (begins with BEGIN:VCARD). Use this when you already produce vCards elsewhere.

Response fields

string
The chat the card was sent into.
string
Always "sent" on success.

Errors

See the full error code reference.

See also