canonical: https://jentic.com/apis/sandbox.api.starkbank.com/sandbox-api-starkbank

# Sandbox Api Starkbank Stark Bank API

Stark Bank API for financial services in Brazil. The API exposes 72 endpoints.

## For AI agents

Programmatically create transactions, list transactions. Covers 72 operations.

## Scope

Does not handle payments, communications, or crm - use for finance and accounting only.

## Capabilities

- Create transactions
- List transactions
- Get transaction by ID
- Query and filter Stark Bank API records by parameters
- Monitor Stark Bank API operational status and events

## Use cases

### Finance and Accounting Operations

Use the Stark Bank API to perform finance operations programmatically. The API provides 72 endpoints covering core functionality including create transactions, list transactions, get transaction by id.

Example prompt: Call POST /transaction to create transactions

### Automated invoice Management

Automate invoice operations by combining multiple Stark Bank API endpoints. Agents can list transactions and then get transaction by id in a single workflow.

Example prompt: Call GET /transaction to list transactions, then verify the result

### AI Agent Integration via Jentic

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/transaction` | Create transactions |
| GET | `/transaction` | List transactions |
| GET | `/transaction/{transactionId}` | Get transaction by ID |
| GET | `/balance` | List balances |
| POST | `/transfer` | Create transfers |
| GET | `/transfer` | List transfers |
| GET | `/transfer/{transferId}` | Get transfer by ID |
| GET | `/transfer/{transferId}/pdf` | Get transfer PDF receipt by ID |

## Key resources

- **invoice** — Operations related to invoice
- **boleto** — Operations related to boleto
- **brcodePayment** — Operations related to brcodePayment
- **boletoPayment** — Operations related to boletoPayment
- **utilityPayment** — Operations related to utilityPayment

## Why Jentic

- **Setup:** Wiring the Stark Bank API by hand means building its request signing, choosing the sandbox or production api.starkbank.com host, and handling paging and retries across transfers and transactions yourself. Through Jentic you install once, import Stark Bank from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** Stark Bank puts the resource id in the URL path (`/transfer/{transferId}`, `/transaction/{transactionId}`), so a rule can pin your agent to specific transfers and transactions: it can read the ones you allow and nothing else. You choose the operations it may call, so writes like creating transfers are not included unless you add them.
- **Credential handling:** Your Stark Bank credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get account balance' or 'get a transfer', and Jentic returns the matching Stark Bank operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Plaid** — Alternative finance API
- **Xero** — Alternative finance API

## FAQ

### What authentication does the Stark Bank API use?

The Stark Bank 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 create transactions with the Stark Bank API?

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

### What are the rate limits for the Stark Bank 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 create transactions through Jentic?

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

### How many endpoints does the Stark Bank API have?

The Stark Bank API exposes 72 endpoints covering invoice, boleto, brcodepayment operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Stark Bank operations and credentials the agent may use. Since Stark Bank puts the resource id in the URL path, such as `/transfer/{transferId}` and `/transaction/{transactionId}`, you can pin the agent to specific transfers and transactions and let it read only the ones you permit. You also choose the operations it may call, so write actions like POST /transfer to create transfers stay off unless you add them.