canonical: https://jentic.com/apis/straddle.com/straddle

# Straddle API

Straddle is a payments processing platform that enables businesses to accept fast, secure payments via Pay by Bank. Manage accounts, customers, payments, payouts, and linked bank accounts. The API exposes 57 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create account, list accounts. Covers 57 operations with apiKey authentication.

## Scope

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

## Capabilities

- Create Account
- List Accounts
- Lookup Account
- Update Account
- Onboard Account
- Simulate Account Onboarding

## Use cases

### Payments Operations

Use the Straddle API to perform payments operations programmatically. The API provides 57 endpoints covering core functionality including create account, list accounts, lookup account.

Example prompt: Call POST /accounts to create account

### Automated Accounts Management

Automate accounts operations by combining multiple Straddle API endpoints. Agents can list accounts and then lookup account in a single workflow.

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

### AI Agent Integration via Jentic

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

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/accounts` | Create Account |
| GET | `/accounts` | List Accounts |
| GET | `/accounts/{accountId}` | Lookup Account |
| PATCH | `/accounts/{accountId}` | Update Account |
| POST | `/accounts/{accountId}/onboard` | Onboard Account |
| POST | `/accounts/{accountId}/simulate-onboarding` | Simulate Account Onboarding |
| POST | `/linked-bank-accounts` | Create Linked Bank Account |
| GET | `/linked-bank-accounts` | List Linked Bank Accounts |

## Key resources

- **Accounts** — Account management endpoints
- **Linked Bank Accounts** — Linked bank account management
- **Charges** — Payment collection (charges)
- **Payouts** — Payment disbursement (payouts)
- **Customers** — Customer management

## Why Jentic

- **Setup:** Wiring the Straddle API by hand means sending its key in the Authorization header on every call to api.straddle.com/v1 and coordinating the account, charge, and payout lifecycles yourself. Through Jentic you install once, import the Straddle API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** Straddle puts the resource id in the URL path (`/charges/{chargeId}/...` and `/accounts/{accountId}/...`), so a rule can pin your agent to one account and its charges. You choose the operations it may call, so releasing a payout or unmasking bank account details is not included unless you add it.
- **Credential handling:** Your Straddle API key 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 'create a charge' or 'onboard an account', and Jentic returns the matching Straddle API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Stripe** — Alternative payments API
- **Adyen** — Alternative payments API
- **Square** — Complementary payments API
- **Paypal** — Complementary payments API

## FAQ

### What authentication does the Straddle API use?

The Straddle API uses an API key passed in the `Authorization` header. 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 account with the Straddle 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 Straddle 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 account through Jentic?

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

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

The Straddle API exposes 57 endpoints covering accounts, linked bank accounts, charges operations.

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

Yes. Because Jentic One is self-hosted, your own rules decide which Straddle operations and credentials the agent may use. Straddle puts the resource id in the URL path, such as `/accounts/{accountId}`/ and `/charges/{chargeId}`/, so you can pin the agent to a single account and its charges. You also choose the exact operations it may call, so sensitive actions like releasing a payout or unmasking linked bank account details are excluded unless you explicitly allow them.