REST API

The REST API gives you unrestricted access to Tilta’s entire feature set. You implement all UI yourself, which means you have complete freedom over the buyer experience – but you are also responsible for every screen, validation, and state transition. This approach suits teams with engineering capacity and complex or highly bespoke requirements.

Prerequisites

Before you start, make sure you have the following in place:

A registered Tilta account
Sandbox API credentials – contact support@tilta.io to request access
A server environment capable of making outbound HTTPS requests

Tilta provides a full sandbox environment at https://api.tilta-sandbox.io so you can develop and test without affecting production data or real credit facilities.

API base URLs

Environment	Base URL
Production	`https://api.tilta.io`
Sandbox	`https://api.tilta-sandbox.io`

All endpoints are versioned under /v1/. Use the sandbox URL during development and switch to the production URL only when you are ready to go live.

Authentication

Tilta uses Bearer token authentication. Include your API key in the Authorization header on every request.

Authorization: Bearer YOUR_API_KEY

Never expose your API key in client-side code, public repositories, or logs. Always make Tilta API calls from your server, not directly from the browser.

To retrieve your API key:

Navigate to admin.tilta.io and sign in with your Tilta account credentials.

Open API settings

Go to Settings → API in the left-hand navigation menu.

Copy your API key

Copy the key for the environment you need (sandbox or production). Store it securely in your environment variables or secrets manager.

Making your first request

The example below creates a buyer – the first step in most Tilta integrations. A buyer represents a business that will receive a credit facility and make purchases on your platform.

curl --request POST \
     --url https://api.tilta.io/v1/buyers \
     --header 'Authorization: Bearer YOUR_API_KEY' \
     --header 'Content-Type: application/json' \
     --data '{
       "external_id": "buyer_001",
       "legal_name": "Acme GmbH",
       "registered_at": "DE"
     }'

A successful response returns a 201 Created status with the new buyer object:

{
  "id": "byr_xxxxxxxxxxxxxxxx",
  "external_id": "buyer_001",
  "legal_name": "Acme GmbH",
  "registered_at": "DE",
  "status": "pending",
  "created_at": "2024-01-15T10:30:00Z"
}

Use the external_id field to store your own internal identifier for the buyer. This makes it easy to look up Tilta resources by your platform’s native IDs.

Core integration flow

A typical REST API integration follows this sequence of API calls:

Create and onboard a buyer

Submit the buyer’s business details (legal name, registration country, address, and so on) via POST /v1/buyers. Tilta’s automated underwriting engine assesses the buyer and, if approved, opens a credit facility.

Request a credit facility

Once the buyer is onboarded, request a credit facility via POST /v1/buyers/{external_id}/facility. The facility defines the credit limit (up to €250,000) and is renewed automatically every three months.

Create an order

When the buyer is ready to purchase, create an order via POST /v1/orders. The order records the buyer’s purchase intent and must be authorised before it can proceed to invoicing.

Capture an invoice

After the goods or services are delivered, capture an invoice via POST /v1/invoices. This is the legally effective financing step – it triggers payout to the merchant and starts the buyer’s repayment clock based on the agreed payment terms (e.g., DEFER_30D).

Error handling

Tilta uses standard HTTP status codes. Always check the response body for a machine-readable code and a human-readable error:

{
  "code": "NOT_FOUND",
  "error": "No buyer found"
}

Status code	Meaning
`200` / `201`	Request succeeded
`400`	Validation error – check the request body, and `issues` for the specific field
`401`	Invalid or missing API key
`404`	The requested resource does not exist
`409`	Conflict – the resource already exists or is in an incompatible state
`424`	An external dependency failed – retry after a short delay
`500`	Tilta internal error – retry with exponential back-off

See API errors for the full list of status codes and error codes.

Resources

API reference

Browse full endpoint documentation including request and response schemas, required fields, and example payloads.

Integration guides

Step-by-step guides for common flows: buyer onboarding, credit facility requests, order creation, and invoice capture.

Recipes

Ready-to-use code snippets and end-to-end examples for the most common integration scenarios.

Get Started

Integration

Onboarding

Orders & Payments

Notifications & Communication

Platform & Reference

Prerequisites

API base URLs

Authentication

Making your first request

Core integration flow

Error handling

Resources

API reference

Integration guides

Recipes

​Prerequisites

​API base URLs

​Authentication

​Making your first request

​Core integration flow

​Error handling

​Resources

API reference

Integration guides

Recipes

Prerequisites

API base URLs

Authentication

Making your first request

Core integration flow

Error handling

Resources