Patch a contact by email. If contact does not exists, it is created
PATCH https://api.connectif.cloud/contacts/{email}
Parameter name | Value | Description | Additional |
---|---|---|---|
Email of the contact to be patched |
Required |
The request body takes a complete ContactPatch resource, containing the following writable properties:
{
"<key>": "string",
"_birthdate": "date-time",
"_emailStatus": "string",
"_mobilePhone": "international",
"_mobilePhoneStatus": "string",
"_name": "string",
"_newsletterSubscriptionStatus": "string",
"_points": "integer",
"_smsSubscriptionStatus": "string",
"_surname": "string"
}
Name | Type | Description | Additional |
---|---|---|---|
<key> | map of string |
A custom field created in Connectif. The key must be the custom field id and the value must be of the appropiate type: string for 'text', 'email', 'date', 'radio' and 'phone' fields; boolean for 'boolean' fields; number for 'decimal' fields; 'integer' for integer fields and an array of string for 'checkbox' fields. |
Optional |
_birthdate | date-time |
Birthdate of the contact in ISO8601 format. |
Optional |
_emailStatus | string |
Status of the email address of the contact: active (email address is valid and can receive emails), bounced, paused or banned. Possible values are:
|
Optional |
_mobilePhone | international |
The phone number of the contact in international format. |
Optional |
_mobilePhoneStatus | string |
Status of the phone number of the contact: active (phone number is valid and can receive SMS), bounced or paused. Possible values are:
|
Optional |
_name | string |
The name of the contact. |
Optional |
_newsletterSubscriptionStatus | string |
Status of subscription of the contact to the email newsletter: subscribed, unsubscribed or none (not specified yet). Possible values are:
|
Optional |
_points | integer |
The score of the contact. |
Optional |
_smsSubscriptionStatus | string |
Status of subscription of the contact to the SMS newsletter: subscribed, unsubscribed or none (not specified yet). Possible values are:
|
Optional |
_surname | string |
The surname of the contact. |
Optional |
This request requires the use of one of following authorization methods:
API key
.
The following HTTP status codes may be returned, optionally with a response resource.
Status code | Description | Resource |
---|---|---|
200 | OK Success. |
Contact |
201 | Created Success. |
Contact |
400 | Bad Request Bad request, i.e.: invalid json or invalid email in path. |
HttpError |
401 | Unauthorized Not authorized to access API. |
|
403 | Forbidden Permission not granted to the API Key or account has been blocked. |
HttpError |
415 | Unsupported Media Type Request without application/json Content-Type header. |
HttpError |
422 | Unprocessable Entity Resource contains validation errors. |
HttpUnprocessableEntityError |
429 | Too Many Requests Requests rate limit reached. |