Skip to main content
POST
Request a service
Requesting a Service is what triggers the funding flow: once the Service is active on an invoice, Tilta finances the receivable and initiates payout to the merchant.
Confirm the invoice satisfies every prerequisite with Service Requirements before requesting the Service.
Listen for the Service status webhook event to learn when a Service becomes active and funding is in progress, rather than polling.

Authorizations

Authorization
string
header
required

Your Tilta API key, sent as Bearer <key>.

Body

application/json
external_id
string
required

Unique identifier of the invoice service.

Maximum string length: 100
Pattern: ^[a-zA-Z0-9-_]+$
invoice_external_id
string
required

Unique identifier of the invoice.

Maximum string length: 100
Pattern: ^[a-zA-Z0-9-_]+$
service_type
enum<string>
required
Available options:
FINANCING,
INSURANCE,
COLLECTION
terms_accepted_at
number
required
paid_out_at
number

Timestamp when the payout should be made (unix time in seconds).

Response

external_id
string
required
Maximum string length: 100
Pattern: ^[a-zA-Z0-9-_]+$
invoice_external_id
string
required
Maximum string length: 100
Pattern: ^[a-zA-Z0-9-_]+$
service_type
enum<string>
required
Available options:
FINANCING,
INSURANCE,
COLLECTION
status
enum<string>
required
Available options:
IN_REVIEW,
ACCEPTED,
REJECTED,
CANCELLED,
PAID_OUT,
SETTLED,
DEFAULTED,
CLAIM_NOTIFIED,
CLAIM_IN_ASSESSMENT,
CLAIM_PAID,
CLAIM_DENIED,
COVER_EXPIRED,
EARLY_COLLECTION,
LATE_COLLECTION,
COLLECTED,
UNCOLLECTIBLE
created_at
number
required
updated_at
number
required
requirements
object[]
advance
object

Advance amount paid out to the merchant for this invoice. Each invoice receives its own SEPA transfer (or N transfers when split above 100K), with the invoice number leading the remittance information for startsWith reconciliation.

fee
object

Fees applied to this invoice, in the smallest currency unit. gross = net + tax.