Escrow.com API

Name: Escrow.com API
Brand: Escrow.com API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentPaymentsPayouts Transfersbasic15 EndpointsREST

For Agents

Create and manage escrow transactions for high-value online sales, fund them, and drive the buyer-seller acceptance flow. Authenticate with HTTP Basic auth.

Install Jentic One Beta

Connect the Escrow.com API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Escrow.com API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Escrow.com API.

Create a new escrow transaction with buyer, seller, and item details

Fund a transaction by selecting an available payment method

Mark an item as shipped, received, accepted, or rejected to drive transaction state

GET STARTED

Start building with Escrow.com API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for the Escrow.com API, keeping it validated and agent-ready. Escrow.com brokers online escrow payments for buyers and sellers of high-value goods, domains, vehicles, and digital assets. The API exposes 15 endpoints to create and update transactions, fund them with a payment, list payment and disbursement methods, mark items as shipped or received, and manage customer accounts. Authentication is HTTP Basic, and every transaction operates under the 2017-09-01 versioned base path. The buyer-seller acceptance flow drives item state transitions through ship, receive, accept, and reject endpoints.

Use Cases

Patterns agents use Escrow.com API for, with concrete tasks.

★ High-Value Online Marketplace Settlement

Marketplaces selling vehicles, domains, or industrial equipment need a settlement layer that holds funds until the buyer accepts the item. Escrow.com's POST /2017-09-01/transaction creates the escrow and the item ship/receive/accept endpoints drive state transitions, replacing custom escrow code with a single REST integration.

Call POST /2017-09-01/transaction with buyer, seller, and item details for a 25,000 USD vehicle, then return the transaction ID and payment URL.

Trust Layer for Domain or Digital Asset Transfers

Brokers selling domain names or digital assets need a way to assure both sides that funds and ownership transfer atomically. Escrow.com's transaction lifecycle (create > fund > ship > receive > accept) handles the trust layer, and the /payment_methods endpoint enables wire, ACH, or card funding depending on amount.

Call POST /2017-09-01/transaction for a domain sale, then GET /2017-09-01/transaction/{id}/payment_methods to surface funding options to the buyer.

Programmatic Customer Onboarding for an Escrow-Backed Service

Platforms wrapping Escrow.com need to onboard customers programmatically rather than redirecting users to escrow.com. The /customer endpoints create accounts, fetch profiles, and look up existing customers by email, so an agent can map a platform user to an Escrow.com customer ID without manual sign-up.

Call POST /2017-09-01/customer with the user's name, email, and address, then GET /2017-09-01/customer/me to confirm the new account.

AI Agent Escrow Assistant via Jentic

An AI agent in a marketplace tooling stack can use Jentic to create and update escrow transactions on behalf of staff. The agent searches by intent (for example 'create an escrow transaction'), loads the schema, and executes with HTTP Basic credentials scoped from the vault - useful for support workflows that need to spin up replacement transactions or update shipping details without leaving the chat.

Use Jentic search('create an escrow transaction'), load the POST /2017-09-01/transaction operation, and execute it with the order details.

Key Endpoints

15 endpoints — jentic publishes the only available openapi specification for the escrow.

METHOD

PATH

DESCRIPTION

POST

/2017-09-01/transaction

Create an escrow transaction

GET

/2017-09-01/transaction/{id}

Get a transaction by ID

PATCH

/2017-09-01/transaction/{id}

Update a transaction

POST

/2017-09-01/transaction/{id}/payment

Fund a transaction

POST

/2017-09-01/transaction/{transactionId}/item/{itemId}/ship

Mark item as shipped

POST

/2017-09-01/transaction/{transactionId}/item/{itemId}/accept

Buyer accepts item

POST

/2017-09-01/customer

Create a customer account

GET

/2017-09-01/customer/me

Get authenticated customer profile

POST

/2017-09-01/transaction

Create an escrow transaction

GET

/2017-09-01/transaction/{id}

Get a transaction by ID

PATCH

/2017-09-01/transaction/{id}

Update a transaction

POST

/2017-09-01/transaction/{id}/payment

Fund a transaction

POST

/2017-09-01/transaction/{transactionId}/item/{itemId}/ship

Mark item as shipped

Why Jentic?

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

Credential isolation

Your Escrow.com email and API key are stored once, encrypted, by your own Jentic One instance and combined into the Basic header at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create an escrow transaction' or 'fund a transaction', and Jentic returns the matching Escrow.com operation with its input schema so the agent calls the right endpoint without memorising the 2017-09-01 path prefix.

Time to first call

FAQs

Specific to using Escrow.com API through Jentic.

Why is there no official OpenAPI spec for the Escrow.com API?

Escrow.com publishes API documentation but not a downloadable OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call the Escrow.com API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Escrow.com API use?

Escrow.com uses HTTP Basic authentication with your account email and API key. Through Jentic the credentials are stored encrypted in your Jentic One instance and injected at execution time so raw secrets never appear in the agent's context.

Can I create an escrow transaction with the Escrow.com API?

Yes. POST /2017-09-01/transaction creates an escrow with buyer, seller, item, and amount details and returns the transaction ID used for funding and lifecycle calls.

What are the rate limits for the Escrow.com API?

Escrow.com applies internal throughput controls but does not publish a fixed quota in the spec. Treat 429 responses as the signal to back off and avoid tight polling on transaction state.

How do I mark an item as shipped through Jentic?

Search 'mark escrow item as shipped'. Jentic returns the POST /2017-09-01/transaction/{transactionId}/item/{itemId}/ship operation, you load its schema, and execute with the transaction and item IDs. Basic auth is injected from the vault.

Can the API list payment methods available on a transaction?

Yes. GET /2017-09-01/transaction/{id}/payment_methods returns the funding options (wire, ACH, card) available for the given transaction based on amount and customer location.

Does the API support buyer rejection of an item?

Yes. POST /2017-09-01/transaction/{transactionId}/item/{itemId}/reject moves the item into a rejected state, triggering Escrow.com's dispute flow.

Can I limit what my agent is allowed to do with the Escrow.com API?

Yes. Because Jentic One is self-hosted, your own rules decide which Escrow.com operations and credentials the agent may use. Since Escrow.com puts the transaction ID in the URL path (/2017-09-01/transaction/{id}/...), you can pin the agent to a single transaction so it can only read that transaction, add a payment, and ship or accept its items. You also choose which operations are reachable at all, so account-level calls like creating a new transaction or customer stay off-limits unless you explicitly allow them.

Escrow.com API

Connect the Escrow.com API to your agent

Capabilities

Start building with Escrow.com API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs