Bond API

Name: Bond API API
Brand: Bond API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentFinanceBankingapiKey38 EndpointsREST

For Agents

Onboard customers, run KYC and KYB, issue and manage cards, open accounts, move money, and subscribe to transaction webhooks through Bond.

Quickstart

Get started with Bond API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"issue a virtual card"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Bond API API.

Onboard a new customer or business and run the matching KYC or KYB verification

Issue a virtual or physical card, activate it, and close or reissue it on demand

Open and manage deposit accounts including transfer-out and account closure

Stream transactions and produce monthly statements for a connected account

GET STARTED

Start building with Bond API API

Explore with Jentic

View OpenAPI Document

Use for: I need to onboard a new customer and run KYC, Issue a virtual card for an existing customer, Activate a physical card that just arrived to the cardholder, Move money from one Bond account to another

Not supported: Does not handle merchant acquiring, payroll, or consumer-facing UI flows — use for embedded banking, card issuance, and identity verification only.

Jentic publishes the only available OpenAPI document for Bond API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Bond API, keeping it validated and agent-ready. Bond is a financial infrastructure platform that lets companies issue cards, open accounts, run KYC and KYB verification, move money, and run their own embedded banking products. The API exposes 38 endpoints covering customers, businesses, cards, accounts, transactions, transfers, statements, webhooks, credit applications, and verification flows. Use it to onboard a customer, verify their identity, issue a debit or credit card, fund an account, and stream transaction events into your ledger.

Use Cases

Patterns agents use Bond API API for, with concrete tasks.

★ Embedded Card Issuance for a Fintech Product

Issue branded virtual or physical cards directly from a fintech product without becoming a card issuer. POST /customers creates the cardholder, POST /verification/kyc clears them, and POST /cards issues the card. Lets product teams ship a card in days rather than negotiating with a sponsor bank.

POST /cards with customer_id cust_8821 and card_type 'virtual' to issue a USD debit card

KYC and KYB Onboarding for Regulated Products

Run regulated identity checks on individuals and businesses before opening accounts or issuing cards. POST /verification/kyc and POST /kyb start the checks, and the corresponding GET endpoints return status. Gates compliance for fintech, marketplace, and B2B SaaS products that need verified counterparties.

POST /verification/kyc for customer_id cust_8821 with their date of birth and SSN-last-4

Real-Time Transaction Pipeline

Stream transaction events into a ledger or fraud system as they happen by registering webhooks rather than polling /transactions. POST /webhooks subscribes to event types, and the registered URL receives the payload moments after each transaction. Enables real-time fraud and balance reconciliation for embedded banking products.

POST /webhooks with url https://example.com/webhooks/bond and events ['transaction.created']

Credit Application and Decisioning

Accept a credit application from a customer, track it through underwriting, and issue a credit-backed card on approval. POST /credit-applications creates the request, GET /credit-applications/{id} returns the decision, and the customer's existing card record can be upgraded or reissued. Useful for products that bundle credit lines with their core offering.

POST /credit-applications for customer_id cust_8821 requesting a 5000 USD credit line

AI Agent Banking Operations

An AI agent uses Jentic to discover Bond operations, onboards customers, issues cards, and reconciles transactions on behalf of a fintech operations team. The Bond API key lives in the Jentic vault so it never enters the agent's prompt. Replaces a multi-week sponsor-bank integration with a single search-load-execute cycle.

Search Jentic for 'issue a virtual card', load the operation, and execute it for the verified customer

Key Endpoints

38 endpoints — jentic publishes the only available openapi specification for bond api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/customers

Create a customer

POST

/verification/kyc

Start KYC verification

POST

/cards

Issue a card

POST

/cards/activate

Activate a physical card

POST

/accounts

Open a deposit account

POST

/transfer

Move money between accounts

POST

/webhooks

Subscribe to webhook events

POST

/credit-applications

Submit a credit application

POST

/customers

Create a customer

POST

/verification/kyc

Start KYC verification

POST

/cards

Issue a card

POST

/cards/activate

Activate a physical card

POST

/accounts

Open a deposit account

POST

/transfer

Why though Jentic?

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

Credential isolation

Bond API keys are stored encrypted in the Jentic vault (MAXsystem) and exchanged for scoped, short-lived access at execution time. The raw Authorization header value never enters the agent's context or logs.

Intent-based discovery

Agents search Jentic with intents like 'issue a virtual card' or 'start KYC verification' and Jentic returns the matching Bond operation with its input schema, removing the need to read the Bond reference docs.

Time to first call

Direct Bond integration: 1-2 weeks to handle KYC, card issuance, webhooks, and statement retrieval. Through Jentic: under an hour with search, load, and execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Boleto Cloud API

Bond issues cards while Boleto Cloud handles Brazilian receivables.

Use both for a Brazilian fintech product that needs cards plus boleto receivables.

Complementary

Bokio API

Sync Bond transactions into Bokio's accounting ledger for Swedish operations.

Pair when Swedish fintechs need both card issuance and accounting books.

Complementary

BoldSign API

Sign cardholder agreements in BoldSign before issuing the card via Bond.

Pair for any card program that requires a signed cardholder agreement upfront.

FAQs

Specific to using Bond API API through Jentic.

Why is there no official OpenAPI spec for Bond API?

Bond does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Bond API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Bond API use?

Bond uses an API key sent in the Authorization header. Through Jentic the key is stored encrypted in the vault and the agent never sees the raw value — only a scoped, short-lived token at execution time.

Can I issue both virtual and physical cards with the Bond API?

Yes. POST /cards creates either type depending on the card_type field. Physical cards must be activated via POST /cards/activate when they reach the cardholder, and any card can be closed with POST /cards/close or reissued via POST /cards/reissue.

How do I run KYC and KYB through Jentic?

Search Jentic for 'start KYC verification', load the POST /verification/kyc operation, then execute it with the customer's identifying details. For businesses, use 'start KYB verification' which loads POST /kyb.

What are the rate limits for the Bond API?

Formal rate limits are not declared in this OpenAPI specification. For high-volume transaction processing, prefer subscribing to /webhooks rather than polling /transactions to avoid unnecessary requests.

Can I get monthly account statements?

Yes. GET /statements returns all statements for the connected accounts and GET /statements/{yyyy-mm} returns the statement for a specific month, formatted as YYYY-MM.