Attentivemobile Attentive API V2
✓ Official Vendor SpecMarketingMarketing Automationbearer, oauth24 EndpointsREST
For Agents
Push user attributes and subscription state into Attentive — single-user upserts and bulk ingestion jobs — and check job status from a warehouse or CDP.
Use for: Upsert a user's email and SMS subscription state in Attentive, Submit a bulk attribute job for 50,000 users, Check the status of a previously submitted Attentive bulk job, Validate that an Attentive bearer token is still active
Not supported: Does not handle campaign creation, message content, or analytics — use for user-attribute upserts and bulk ingestion only.
Attentive is an SMS and email marketing platform for direct-to-consumer brands. The V2 API focuses on user-attribute and bulk-ingestion flows, with endpoints for upserting a single user with attributes and subscription state, submitting bulk user attribute jobs, retrieving the status of those jobs, and validating the calling identity through /v2/me. It is intentionally lean — designed to feed Attentive from a CDP or warehouse rather than to manage campaigns or content.
Install Jentic One Beta
Connect the Attentive API V2 to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Attentive API V2, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Attentive API V2 API.
Upsert a single user's attributes and SMS or email subscription state via POST /v2/user/attributes
Submit a bulk user-attributes job to ingest large attribute deltas through POST /v2/bulk/user/attributes
Retrieve the status of a running or completed bulk job via GET /v2/bulk/job/{bulkJobId}
Validate the calling token and tenant context using GET /v2/me
Sync warehouse-derived audience traits into Attentive on a recurring schedule
Use Cases
Patterns agents use Attentive API V2 API for, with concrete tasks.
★ Warehouse to Attentive Identity Sync
Direct-to-consumer brands compute audience attributes (lifetime value bucket, last purchase channel, churn risk) in a warehouse and need them inside Attentive to drive segmentation. The V2 bulk endpoint lets a sync agent ship a daily job of attribute deltas through POST /v2/bulk/user/attributes and poll GET /v2/bulk/job/{bulkJobId} until it completes. Single-user updates flow through POST /v2/user/attributes for real-time changes.
Submit a bulk user-attributes job containing today's attribute deltas, then poll /v2/bulk/job/{bulkJobId} until status is COMPLETED
Real-Time Subscription State Updates
When a customer opts in or out of SMS through a brand's own surface (account page, support flow), that change must reach Attentive immediately. POST /v2/user/attributes accepts the user's identifier and updated subscription state, so a single call keeps consent in sync. This avoids the eventual-consistency window of a daily batch and keeps consent records audit-ready.
POST /v2/user/attributes with the user's email, phone, and subscription={'sms':'OPT_IN'} after they confirm consent on the brand site
Bulk Job Monitoring
Operations teams running daily Attentive ingestion need to alert on failed bulk jobs and retry safely. The /v2/bulk/job/{bulkJobId} endpoint returns the job status, error counts, and completion timestamp, so a monitoring agent can flag failures, summarise the row counts, and trigger a retry of the affected slice. This keeps SLA-tracked sync windows transparent.
Every 5 minutes, list outstanding bulk job ids, GET /v2/bulk/job/{bulkJobId} for each, and post a Slack alert if any returned status is FAILED
Attentive Sync via Jentic
Through Jentic, an AI agent or warehouse pipeline calling Attentive searches by intent ('upsert subscriber attributes') and Jentic returns POST /v2/user/attributes or POST /v2/bulk/user/attributes with their schemas. Bearer tokens are held in the Jentic vault, so the agent never sees the secret. This makes Attentive ingestion possible from any LLM or scheduled workflow without bespoke client code.
Use Jentic to search 'upsert Attentive user attributes', load POST /v2/user/attributes, and execute with the user's identifiers and trait map
Key Endpoints
4 endpoints — attentive is an sms and email marketing platform for direct-to-consumer brands.
METHOD
PATH
DESCRIPTION
GET
/v2/me
Validate the calling identity and tenant
POST
/v2/user/attributes
Upsert a single user's attributes and subscription state
POST
/v2/bulk/user/attributes
Submit a bulk user-attributes ingestion job
GET
/v2/bulk/job/{bulkJobId}
Get the status of a bulk ingestion job
GET
/v2/me
Validate the calling identity and tenant
POST
/v2/user/attributes
Upsert a single user's attributes and subscription state
POST
/v2/bulk/user/attributes
Submit a bulk user-attributes ingestion job
GET
/v2/bulk/job/{bulkJobId}
Get the status of a bulk ingestion job
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Attentive bearer tokens and OAuth credentials are stored encrypted in the Jentic vault (MAXsystem). Jentic injects the Authorization header at call time, so the raw token never enters the agent's context.
Intent-based discovery
Agents search Jentic by intent (e.g. 'upsert Attentive subscriber attributes') and Jentic returns POST /v2/user/attributes with its schema, so the agent posts the right shape on the first call.
Time to first call
Direct integration: half a day to wire bearer auth, attribute mapping, and bulk job polling. Through Jentic: under 30 minutes for the common upsert and bulk-status flows.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Attentive API V2 API through Jentic.
What authentication does the Attentive API V2 use?
Attentive V2 supports HTTP bearer auth for static API tokens and an OAuth 2.0 flow for app-based integrations. Through Jentic, the bearer token or OAuth credentials are held in the encrypted vault, and the Authorization header is set at call time so the secret never enters the agent's context.
Can I upsert a subscriber's attributes with the Attentive API?
Yes. POST /v2/user/attributes accepts the user's identifier alongside an attributes map and subscription state, and upserts the record in Attentive in a single call. Use this for real-time consent and trait changes.
What are the rate limits for the Attentive API V2?
Attentive throttles per token. The spec does not encode the limit numerically — the safe pattern is to back off on HTTP 429 responses and prefer the bulk endpoint for large attribute updates rather than looping over /v2/user/attributes.
How do I run a bulk attribute sync through Jentic?
Search Jentic for 'submit Attentive bulk attributes job', load POST /v2/bulk/user/attributes, and execute with the payload of attribute deltas. Then search 'get bulk job status', load GET /v2/bulk/job/{bulkJobId}, and poll until the job completes.
Can I read campaigns or message data with the V2 API?
No. The V2 surface in this spec is focused on user attributes and bulk ingestion, plus a /v2/me identity check. Campaign content and message-level reporting sit on other Attentive surfaces.
GET STARTED