Interactive Messages
Send Contact
Sends one or more contact cards. Supported on WhatsApp, Z-API, and ZapperAPI.
POST
/
messages
/
interactive
/
send-contact
Sends one or more contact cards (vCard) via WhatsApp. This is supported on WhatsApp, Z-API, and ZapperHUB channels.
Authentication: Requires a valid API key or session. Pass as Authorization: Bearer <api_key>.
Request Body
The API uses a dynamic schema to reconstruct a contact object from flat parameters.
Required Parameters
agentId: The ID of the agent sending the message.conversationId: The ID of the conversation to send to.name_formatted_name: Full name as it should appear in the contact card.name_first_name: First name. Required by Meta’s API even though documented as optional.phone_1_phone: Phone number.
Optional Parameters
Name fields
name_last_name: Last name.name_middle_name: Middle name.name_suffix: Name suffix (e.g., “Jr.”, “Esq.”).name_prefix: Name prefix (e.g., “Dr.”, “Ms.”).
Phone fields (up to multiple phones)
phone_1_type: Type of phone (e.g.,CELL,WORK,HOME,Mobile,Landline).phone_1_wa_id: WhatsApp ID for the phone. When this matches the recipient, WhatsApp shows Message and Save to Contacts buttons.phone_2_phone,phone_2_type,phone_2_wa_id: Second phone number.
Email fields (up to multiple emails)
email_1_email: Email address.email_1_type: Type of email (e.g.,WORK,HOME).email_2_email,email_2_type: Second email.
Address fields (up to multiple addresses)
address_1_street: Street address.address_1_city: City.address_1_state: State code.address_1_zip: ZIP / postal code.address_1_country: Country name.address_1_country_code: 2-letter country code (e.g.,BR,US).address_1_type: Address type (e.g.,HOME,WORK).
Organization fields
org_company: Company name.org_department: Department.org_title: Job title.
URL fields
url_1_url: Website URL.url_1_type: URL type (e.g.,WORK,COMPANY).
Other
birthday: Date of birth (YYYY-MM-DD format).
Important Notes
name_first_nameis required by Meta — the API auto-fills it fromname_formatted_nameif omitted.- If
phone_1_wa_idmatches the recipient, WhatsApp shows Message + Save buttons. Without it, only generic contact info is shown. - The message is only saved to the conversation history if Meta confirms delivery with a message ID.
Example (minimal)
Example (full)
Error Responses
The endpoint returns errors in the following scenarios:
| HTTP Status | Meaning |
|---|---|
| 400 | Invalid request body (missing required fields, validation error) |
| 401 | Invalid or missing API key |
| 403 | Agent does not belong to your organization |
| 404 | Conversation or agent not found |
| 500 | WhatsApp API error (Meta rejected the message, invalid token, etc.) |
On success, returns the Meta API response including the message ID.
Authorizations
Authorization
string
headerrequiredBearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
application/json
agentId
string
requiredThe ID of the agent.
conversationId
string
requiredThe ID of the conversation.
name_formatted_name
string
requiredFull name as it should appear.
Was this page helpful?

