canonical: https://jentic.com/apis/swaggerhub.attentive-060/attentive-api

# Attentive 060 Attentive API

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.

## For AI agents

Programmatically me, create webhook. Covers 21 operations with bearer authentication.

## Scope

Does not handle payments, communications, or developer tools - use for crm only.

## Capabilities

- Me
- Create webhook
- List webhooks
- Update webhook
- Delete webhook
- Access Token
- Product view

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'me', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| 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 |

## Key resources

- **Test Authentication** — Use the Test Authentication endpoint to test your unique token that you received from Attentive. Mak
- **Access Token** — Public applications must authenticate using the OAuth 2.0 specification to use Attentive’s API resou
- **Webhooks** — Create and manage webhooks
- **eCommerce** — Use the eCommerce API to trigger an event when a user views a product, adds a product to their shopp
- **Offers** — You can use the Offers API to add discount codes to an existing offer.

## Why Jentic

- **Setup:** This Attentive API uses bearer authentication with your API key as the token, so hand-wiring it means generating the key, attaching the Authorization header to every call, and handling retries yourself. Through Jentic you install once, import the Attentive API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** This API puts the webhook id in the URL path (/webhooks/{webhookId}), so a rule can pin your agent to one webhook. You choose the operations it may call, so destructive ones like deleting a webhook are not included unless you add them.
- **Credential handling:** Your Attentive API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'register a webhook' or 'record an add-to-cart event', and Jentic returns the matching Attentive API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Hubspot** — Alternative crm API
- **Salesforce** — Alternative crm API
- **Pipedrive** — Complementary crm API
- **Zoho** — Complementary crm API

## FAQ

### 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 your Jentic One instance 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 through Jentic One, the self-hosted execution layer, 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.

### Can I limit what my agent is allowed to do with the Attentive API?

Yes. Jentic One runs self-hosted, so your own rules decide which Attentive API operations and credentials your agent can use. Because the API puts the webhook id in the URL path (/webhooks/{webhookId}), you can pin the agent to a single webhook, and you choose the operations it may call, so destructive ones like DELETE /webhooks/{webhookId} are excluded unless you add them. You can grant read-only access to GET /me and GET /webhooks while withholding POST and PUT calls, keeping the stored API key out of the agent's prompt and logs.