Create a contact
Authentication
The API key should be passed in the request headers as api-key for authentication.
OAuth 2.0 client_credentials (machine-to-machine) grant. Exchange your app’s client_id/client_secret for a short-lived Bearer token.
Request
Pass the set of attributes and their values. The attribute’s parameter should be passed in capital letter while creating a contact. Values that don’t match the attribute type (e.g. text or string in a date attribute) will be ignored. These attributes must be present in your Brevo account. For eg: {“FNAME”:“Elly”, “LNAME”:“Roger”, “COUNTRIES”: [“India”,“China”]}
Email address of the user. Mandatory if “ext_id” & “SMS” field is not passed.
Set this field to blacklist the contact for emails (emailBlacklisted = true)
Set this field to blacklist the contact for SMS (smsBlacklisted = true)
transactional email forbidden sender for contact. Use only for email Contact ( only available if updateEnabled = true )
Facilitate to update the existing contact in the same request (updateEnabled = true)
When true, if the contact being created shares an identifier (email, SMS, ext_id, whatsapp, landline) with an existing contact, the two contacts are force-merged. The contact with the most recent last_modified timestamp is retained; the other is deleted. When false (default), a 4xx error is returned on identifier conflict.
When true, the response returns the id of the surviving contact after merge.