canonical: https://jentic.com/apis/swaggerhub.hackney/accounts-api

# Hackney Accounts API

To gather and provide information relating to customer accounts. The API exposes 5 endpoints.

## For AI agents

Programmatically post-accounts, get-accounts. Covers 5 operations.

## Scope

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

## Capabilities

- post-accounts
- get-accounts
- put-accounts-by-id
- Query and filter Accounts API records by parameters
- Monitor Accounts API operational status and events

## Use cases

### Developer Tools Operations

Use the Accounts API to perform developer tools operations programmatically. The API provides 5 endpoints covering core functionality including post-accounts, get-accounts, get-accounts-arrears.

Example prompt: Call POST /accounts to post-accounts

### Automated Accounts API Management

Automate accounts API operations by combining multiple Accounts API endpoints. Agents can get-accounts and then get-accounts-arrears in a single workflow.

Example prompt: Call GET /accounts to get-accounts, 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.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /accounts | post-accounts |
| GET | /accounts | get-accounts |
| GET | /accounts/arrears | get-accounts-arrears |
| GET | /accounts/{id} | get-accounts-by-id |
| PUT | /accounts/{id} | put-accounts-by-id |

## Key resources

- **Accounts API** — Retrieve account details
- **Production** — This API is available in the Production environment
- **Staging** — This API is available in the Staging environment
- **Development** — This API is available in the Development environment
- **accounts** — Operations related to accounts

## Why Jentic

- **Setup:** Wiring the Hackney Accounts API by hand means coding each account call against the service host and handling paging and retries yourself, even though it declares no auth scheme. Through Jentic you install once, import the Accounts API from the API Directory, and your agent calls it.
- **Permission scoping:** This API puts the account id in the URL path (/accounts/{id}), so a rule can pin your agent to one account: it can read that account and nothing else. You choose the operations it may call, so writes like creating or updating an account are not included unless you add them.
- **Credential handling:** This Accounts API declares no credential, so there is nothing to store. If your deployment later requires one, your own Jentic One instance stores it encrypted and injects it at execution time so it never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list accounts' or 'get an account by id', and Jentic returns the matching Accounts API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### 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 post-accounts with the Accounts API?

Yes. Use the POST /accounts 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 post-accounts through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'post-accounts'. 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 5 endpoints covering accounts API, production, staging operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Accounts API operations the agent may call and which credentials it may use. Since the account id sits in the URL path (/accounts/{id}), you can pin the agent to a single account and let it only read that record while excluding writes such as POST /accounts or PUT /accounts/{id}. You add each operation, like GET /accounts/arrears, only when you want the agent to reach it.