Whapi Accounts API

Name: Accounts API
Brand: Accounts API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityForms Surveysnone9 EndpointsREST

Install Jentic One Beta

Connect the Accounts API to your agent

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

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

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 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 Accounts API.

Retrieves details of a customers account

Get a customers account balance

Sets a flag based on name to value provided for the user.

Query and filter Accounts API records by parameters

GET STARTED

Start building with Accounts API

Explore with Jentic

View OpenAPI Document

For Agents

Programmatically retrieves details of a customers account, get a customers account balance. Covers 9 operations.

Use for: I need to retrieves details of a customers account, I want to a customers account balance, Search for sets a flag based on name to value provided for the user., Find all gets a customer's account payments

Not supported: Does not handle payments, communications, or crm - use for productivity only.

Use Cases

Patterns agents use Accounts API for, with concrete tasks.

★ Productivity Operations

Use the Accounts API to perform productivity operations programmatically. The API provides 9 endpoints covering core functionality including retrieves details of a customers account, get a customers account balance, sets a flag based on name to value provided for the user..

Call GET /account to retrieves details of a customers account

Automated Account Management

Automate account operations by combining multiple Accounts API endpoints. Agents can get a customers account balance and then sets a flag based on name to value provided for the user. in a single workflow.

Call GET /account/balance to get a customers account balance, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Accounts 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 none tokens manually.

Search Jentic for 'retrieves details of a customers account', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

9 endpoints — the accounts api is a collection of methods used to query a customer account.

METHOD

PATH

DESCRIPTION

GET

/account

Retrieves details of a customers account

GET

/account/balance

Get a customers account balance

POST

/account/flags

Sets a flag based on name to value provided for the user.

GET

/account/payments

Gets a customer's account payments

GET

/account/plusCard

Gets a customer's plus card details if they exist.

POST

/account/plusCard/lostStolen

Sets a customer's plus card as Lost/Stolen

POST

/account/plusCard/phone/{oldPhoneNumber}

Sets a customer's plus card phone number

POST

/account/plusCard/pin

Sets a customer's plus card pin

GET

/account

Retrieves details of a customers account

GET

/account/balance

Get a customers account balance

POST

/account/flags

Sets a flag based on name to value provided for the user.

GET

/account/payments

Gets a customer's account payments

GET

/account/plusCard

Gets a customer's plus card details if they exist.

Why Jentic?

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

Credential isolation

This Accounts API declares no authentication in its spec, so there is no credential to store; if your instance later adds one, Jentic One stores it once, encrypted, and injects it at execution time so it never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'get a customer's account details' or 'read the account balance', and Jentic returns the matching Accounts API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Accounts API through Jentic.

What authentication does the Accounts API use?

The Accounts API uses no authentication. 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 retrieves details of a customers account with the Accounts API?

Yes. Use the GET /account endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Accounts 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 retrieves details of a customers account through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'retrieves details of a customers account'. Jentic returns the matching Accounts API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Accounts API have?

The Accounts API exposes 9 endpoints covering account operations.

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

Yes. Jentic One is self-hosted, so you run it and your own rules decide which Accounts API operations and credentials the agent may use. Because this API carries account details in the request body rather than pinning to a single account in the path, you can restrict the agent to just the read operations it needs, such as GET /account for account details or GET /account/balance for the balance. Write actions on the plusCard, like reporting a card lost or stolen via POST /account/plusCard/lostStolen or changing the PIN via POST /account/plusCard/pin, stay off limits until you explicitly grant them.

Whapi Accounts API

Connect the Accounts API to your agent

Capabilities

Start building with Accounts API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs