canonical: https://jentic.com/apis/swaggerhub.sandipchandra/swaggerhub-sandipchandra

# Sandipchandra Account API

To identify all information to be captured with regards to the Accounts domain. The API exposes 12 endpoints.

## For AI agents

Programmatically createaccountsummary, getaccountsummary. Covers 12 operations.

## Scope

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

## Capabilities

- createAccountSummary
- getAccountSummary
- createArrears
- getAssetHighArrears
- getTenureHighArrears
- createAssetAccount
- updateAssetAccount

## Use cases

### Developer Tools Operations

Use the Account API to perform developer tools operations programmatically. The API provides 12 endpoints covering core functionality including createaccountsummary, getaccountsummary, createarrears.

Example prompt: Call POST /account/summary to createaccountsummary

### Automated Account Management

Automate account operations by combining multiple Account API endpoints. Agents can getaccountsummary and then createarrears in a single workflow.

Example prompt: Call GET /account/summary to getaccountsummary, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Account 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 'createaccountsummary', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /account/summary | createAccountSummary |
| GET | /account/summary | getAccountSummary |
| POST | /accounts/arrears | createArrears |
| GET | /accounts/arrears/asset/{targetType} | getAssetHighArrears |
| GET | /accounts/arrears/tenure | getTenureHighArrears |
| POST | /accounts/asset | createAssetAccount |
| PUT | /accounts/asset | updateAssetAccount |
| GET | /accounts/asset/{targetid} | getAssetAccounts |

## Key resources

- **Account** — Operations for account
- **Accounts** — Operations for accounts

## Why Jentic

- **Setup:** Wiring Account API by hand means standing up its base host and handling requests and retries yourself, even though it ships no auth scheme. Through Jentic you install once, import Account API from the API Directory, store any connection details once, and your agent calls it.
- **Permission scoping:** Account API puts the asset id in the URL path (/accounts/asset/{targetid}), so a rule can pin your agent to one asset: it can read that asset and nothing else. You choose the operations it may call, so writes like creating or updating assets are not included unless you add them.
- **Credential handling:** Any Account API connection detail 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 'get an account summary' or 'look up arrears for an asset', and Jentic returns the matching Account 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 Account API use?

The Account 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 createaccountsummary with the Account API?

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

### What are the rate limits for the Account 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 createaccountsummary through Jentic?

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

### How many endpoints does the Account API have?

The Account API exposes 12 endpoints covering account, accounts operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Account API operations and connection details the agent can use. Since the asset id sits in the URL path (GET /accounts/asset/{targetid}), you can pin the agent to a single asset so it only reads that account summary or arrears data. You choose the operations it may call, so write actions such as createAssetAccount, updateAssetAccount, or createArrears are excluded unless you explicitly grant them.