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

# Attentive 060 Attentive Provisioning API

The Attentive Provisioning API is used for creating and managing Attentive Accounts, Users and Subscribers. This Open API Spec is configured to use Bearer Token authentication. Click the Authorize button and enter your Attentive API Key to authenticate. The API exposes 26 endpoints secured with bearer authentication.

## For AI agents

Programmatically check if domain prefix is available, check if internal name is available. Covers 26 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for identity and authentication only.

## Capabilities

- Check if domain prefix is available
- Create company
- Fetch company by ID
- Update company details
- Monitor Attentive Provisioning API operational status and events

## Use cases

### Identity and Authentication Operations

Use the Attentive Provisioning API to perform identity auth operations programmatically. The API provides 26 endpoints covering core functionality including check if domain prefix is available, check if internal name is available, create company.

Example prompt: Call GET /v1/companies/validation/domain/{attentiveDomainPrefix} to check if domain prefix is available

### Automated Preflight Management

Automate preflight operations by combining multiple Attentive Provisioning API endpoints. Agents can check if internal name is available and then create company in a single workflow.

Example prompt: Call GET /v1/companies/validation/internalName/{internalName} to check if internal name is available, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Attentive Provisioning 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 'check if domain prefix is available', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /v1/companies/validation/domain/{attentiveDomainPrefix} | Check if domain prefix is available |
| GET | /v1/companies/validation/internalName/{internalName} | Check if internal name is available |
| POST | /v1/companies | Create company |
| GET | /v1/companies/{id} | Fetch company by ID |
| PATCH | /v1/companies/{id} | Update company details |
| GET | /v1/companies/{id}/parent | Fetch parent company for the given company |
| PUT | /v1/companies/{id}/parent | Updates the parent company for the given company |
| GET | /v1/companies/{id}/status/datasync | Fetch company status |

## Key resources

- **Preflight** — Check for existence of company name or domain
- **Companies** — Create, fetch and update companies
- **Parent Company** — Get and update parent company
- **Status** — Check company status and fetch credentials
- **Users** — Create, fetch and delete users

## Why Jentic

- **Setup:** This Attentive Provisioning API uses bearer authentication with your API key as the token, so hand-wiring it means attaching the Authorization header to every company call and handling retries yourself. Through Jentic you install once, import the Attentive Provisioning API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** This API puts the company id in the URL path (/v1/companies/{id}), so a rule can pin your agent to one company. You choose the operations it may call, so writes like patching a company or setting its parent are not included unless you add them.
- **Credential handling:** Your Attentive Provisioning 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 'check if a domain prefix is available' or 'create a company', and Jentic returns the matching Attentive Provisioning API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Auth0** — Alternative identity auth API
- **Okta** — Alternative identity auth API

## FAQ

### What authentication does the Attentive Provisioning API use?

The Attentive Provisioning 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 check if domain prefix is available with the Attentive Provisioning API?

Yes. Use the GET /v1/companies/validation/domain/{attentiveDomainPrefix} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Attentive Provisioning 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 check if domain prefix is available through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'check if domain prefix is available'. Jentic returns the matching Attentive Provisioning API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Attentive Provisioning API have?

The Attentive Provisioning API exposes 26 endpoints covering preflight, companies, parent company operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which Attentive Provisioning API operations and which credentials your agent may use. Because this API carries the company id in the URL path such as /v1/companies/{id}, you can pin the agent to a single company. You also choose the exact operations it can call, so you can allow read calls like fetching a company or its parent while excluding writes such as PATCH /v1/companies/{id} or PUT /v1/companies/{id}/parent.