Reference · built on requestConnectorMarketing, reviews & analytics

Attentive

Subscribers, custom attributes, events, segments, and signed webhooks from Attentive for SMS and email marketing.

Request accessPricing ↗

About

Attentive is an SMS and email marketing platform. An account holds subscribers with their marketing and transactional consent by channel, custom attributes, custom and ecommerce events, segments, journeys, and offers. The API at api.attentivemobile.com/v1 serves REST and GraphQL and is authorized per app with scopes. Webhooks report subscriptions, sends, opens, and link clicks.

Through Fibric, an operator checks a subscriber's eligibility, joins it with orders and support cases, and proposes a custom event, an attribute change, or a segment update for your approval. Each approved write happens once and is logged with its reason and how to reverse it.

This is a reference listing. It documents what Fibric would read from Attentive and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Subscription eligibility for a user by phone or email, showing the subscription types and channels they are opted into
  • Custom attributes on a user, queried by phone or email
  • Segments created through the API, with bulk membership jobs tracked at GET /v2/bulk/job/{bulkJobId}
  • Webhooks for sms.subscribed, sms.sent, sms.message_link_click, email.subscribed, email.unsubscribed, email.message_link_click, email.opened, and custom_attribute.set
  • Bulk job status and .jsonl result files for attribute and segment uploads

Proposed actions

  • Target capability: propose a custom event through POST /v1/events/custom, which segments and journeys can act on
  • Target capability: propose a custom attribute update on a user, or a bulk update of up to 256 payloads
  • Target capability: propose adding or removing segment members in bulk, 1 to 10,000 per request
  • Target capability: propose an opt-in through POST /v1/subscriptions, or an unsubscribe for a type or channel
  • Target capability: propose a purchase, product view, or add-to-cart event through the Ecommerce endpoints

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Text the customer when a shipment stalls

    The carrier feed shows no scan. The operator checks SMS eligibility for the phone, then proposes a custom event with the order and new estimate that your journey turns into a text.

    With Stalled Shipment, ETA Notice

  • Pause promotions after a complaint

    A low score arrives from your help desk. The operator proposes a custom attribute on the user so journeys and campaigns can hold marketing texts until the case closes.

    With Detractor Callback

  • Rebuild a segment from order history

    The operator computes who is due to reorder from your store data and proposes a bulk segment membership job. You approve the list; the job runs once.

    With Reorder Prompt, Churn Watch

  • Keep consent in step with the help desk

    sms.subscribed and email.unsubscribed webhooks arrive signed. The operator matches each to a customer record and proposes a note so agents see current consent.

    With Contact Drivers

Requirements

  • An Attentive account and an app with the scopes the operator needs, for example events:write, attributes:write, subscriptions:write, or segments:Write
  • For programmatic opt-ins, an API sign-up unit with compliant legal disclosure, referenced by signUpSourceId or resolved from locale and subscriptionType
  • A journey or segment in Attentive that reacts to the custom events or attributes the operator writes
  • An HTTPS endpoint and the webhook signing key for event notifications
Authentication
A Bearer token: an API key for a private app, or an access token from the OAuth 2.0 authorization code flow for a public app, with scopes such as events:write and subscriptions:write.

Limits

  • Most endpoints allow up to 150 requests per second; Identity and Subscribe allow 10, Unsubscribe 5, and product catalog uploads 1
  • A custom event with a timestamp older than 12 hours is stored but does not trigger journeys
  • Custom attributes cannot be arrays or nested objects; a user can hold 100 of them through the single-user endpoint
  • Opt-in and unsubscribe calls on TEXT subscriptions send the person a confirmation text, even when the state already matches

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Attentive ↗

Questions and answers

What does the API need to opt a user in?
A call to POST /v1/subscriptions with the phone in E.164 format or an email, plus either a signUpSourceId from the Sign-up Units tab or both a locale and a subscriptionType of MARKETING or TRANSACTIONAL. Attentive requires a legal disclosure for programmatic opt-ins, and a TEXT opt-in sends a confirmation message.
How are webhooks signed?
Each webhook is an HTTP POST with a JSON body. When a signing key is configured, Attentive adds an x-attentive-hmac-sha256 header containing the HMAC-SHA256 of the body. Compare it against your own digest with a constant-time comparison before acting.
How fast can the connector write?
Default limits are up to 150 requests per second for most endpoints, 10 for Identity and Subscribe, 5 for Unsubscribe, and 1 for product catalog uploads. Responses carry x-ratelimit-limit and x-ratelimit-remaining, and a 429 means back off and retry.
Ask about Attentive

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Attentive through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy