Attentive Provisioning API

Name: Attentive Provisioning API API
Brand: Attentive Provisioning API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIdentity AuthAuthenticationbearer26 EndpointsREST

For Agents

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

Connect the Attentive Provisioning API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Attentive Provisioning 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.

Install Jentic One Beta (Self-Hosted)

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

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 instance

Jentic 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 Provisioning API API.

Check if domain prefix is available

Create company

Fetch company by ID

Update company details

GET STARTED

Start building with Attentive Provisioning API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Attentive Provisioning API, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use Attentive Provisioning API API for, with concrete tasks.

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

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.

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.

Search Jentic for 'check if domain prefix is available', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

26 endpoints — the attentive provisioning api is used for creating and managing attentive accounts, users and subscribers.

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

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Attentive Provisioning 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., 'check if domain prefix is available') and Jentic returns the matching Attentive Provisioning API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Attentive Provisioning 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.

Alternative

Auth0

Alternative identity auth API

Choose Auth0 when you need a different approach to identity auth operations

Alternative

Okta

Alternative identity auth API

Choose Okta when you need a different approach to identity auth operations

FAQs

Specific to using Attentive Provisioning API API through Jentic.

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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.