Sends a content to a user.

Adds or updates a custom field value for a user.

Finds a user by custom field.

Finds a user by name.

Make a call to this endpoint when a user adds a product to their shopping cart.

Make a call to this endpoint for any event-based data representing user actions.

Get Custom Attributes for a User

Make a call to this endpoint to subscribe a user to subscriptions. Note that when a user is subscribed programmatically, it must include

Make a call to this endpoint when a user views a product.

Creates or updates a single user record, including associated attributes, subscriptions, and identifiers. If a user with the provided identifiers already exists, their information will be updated; otherwise, a new user will be created. There is a limit of 100 of custom attributes that can be created. If intending to update an existing attribute, the name of the key must match the name of the existing attribute. If an existing attribute does not exist, a new attribute will be created with the given key as the name. Attributes with enumerated values must have a value that matches an existing enum value; new enum values will not be created. Attempting to pass custom attributes as an array or a map such as ["New York City] or {"favorite city": "Boston"} will result in a 400 error.

Sends a message to a user.

Subscribes existing ManyChat Subscriber to a Sequence. Subscribers can't be added via Zapier.

Finds a user by ID.

Make a call to this endpoint for any attribute-based data.

You can use the Privacy Request API in order to comply with

Make a call to this endpoint to get recent catalog uploads with their statuses to gain visibility into the ingestion workflow in order of creation. See the POST of this endpoint for details.

Use the Identity API to manage user identifiers. With this API, you can programmatically add a client user identifier or custom identifier(s) to a user. You should only use clientUserId and customIdentifiers to send Attentive your system-assigned unique identifiers (even when testing).

Make a call to this endpoint to unsubscribe a user from a subscription type or channel. If no subscriptions are present in the request, the user is unsubscribed from all subscriptions. If subscriptions are present in the request, the user is unsubscribed from the requested type or channel combination. By default, if a subscription exists, but the user is already unsubscribed, it records the attempt to unsubscribe the subscription again. For TEXT subscriptions, a message is sent to the person indicating that they are unsubscribed.

Make a call to this endpoint when a user generates an order or purchase.

Make a call to this endpoint to list all subscription types and channels a user is subscribed to. You can query for a subscriber using either their phone number or email. One of the query parameters is required in order to look up a subscriber. As an example, you can use this endpoint to check if a subscriber is eligible to receive SMS or email campaigns, and then send them a message based on that eligibility.