Attentive 060 Attentive API
Browse all Swaggerhub Attentive 060 APIs★ Only Publicly Available OpenAPI DocumentCRMContact Managementbearer21 EndpointsREST
For Agents
Programmatically me, create webhook. Covers 21 operations with bearer authentication.
Use for: I need to me, I want to webhook, Search for webhooks, Find all webhook
Not supported: Does not handle payments, communications, or developer tools — use for crm only.
For any questions, contact us at [api@attentivemobile.com](mailto:api@attentivemobile.com). **Authentication** To keep data on Attentive's platform safe and secure, all apps connecting with Attentive's APIs must authenticate when making API requests. Different types of apps require different authentication or authorization methods: * Private apps use basic HTTP authentication. * Public apps use OA. The API exposes 21 endpoints secured with bearer authentication.
Install Jentic One Beta
Connect the Attentive API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Attentive API, 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.
Me
Create webhook
List webhooks
Update webhook
Delete webhook
Access Token
Product view
Use Cases
Patterns agents use Attentive API for, with concrete tasks.
★ CRM Operations
Use the Attentive API to perform crm operations programmatically. The API provides 21 endpoints covering core functionality including me, create webhook, list webhooks.
Call GET /me to me
Automated Test Authentication Management
Automate test authentication operations by combining multiple Attentive API endpoints. Agents can create webhook and then list webhooks in a single workflow.
Call POST /webhooks to create webhook, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Attentive API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.
Search Jentic for 'me', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
21 endpoints — for any questions, contact us at [api@attentivemobile.
METHOD
PATH
DESCRIPTION
GET
/me
Me
POST
/webhooks
Create webhook
GET
/webhooks
List webhooks
PUT
/webhooks/{webhookId}
Update webhook
DELETE
/webhooks/{webhookId}
Delete webhook
POST
/authorization-codes/tokens
Access Token
POST
/events/ecommerce/product-view
Product view
POST
/events/ecommerce/add-to-cart
Add to cart
GET
/me
Me
POST
/webhooks
Create webhook
GET
/webhooks
List webhooks
PUT
/webhooks/{webhookId}
Update webhook
DELETE
/webhooks/{webhookId}
Delete webhook
POST
/authorization-codes/tokens
Access Token
POST
/events/ecommerce/product-view
Product view
POST
/events/ecommerce/add-to-cart
Add to cart
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Attentive API bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'me') and Jentic returns the matching Attentive API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Attentive API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Attentive API through Jentic.
What authentication does the Attentive API use?
The Attentive API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.
Can I me with the Attentive API?
Yes. Use the GET /me endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Attentive API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I me through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'me'. Jentic returns the matching Attentive API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the Attentive API have?
The Attentive API exposes 21 endpoints covering test authentication, access token, webhooks operations.
GET STARTED