> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tilta.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Request a facility increase
> Submit a limit increase request for a buyer existing credit facility. Triggers a new underwriting review with the result delivered via webhook event.
If a buyer's purchasing volume grows beyond their current credit facility limit, you can request an increase on their behalf. The increase request triggers a new underwriting review using the latest credit bureau data and the buyer's updated business profile. The requested amount represents the new total limit you are asking for – not an incremental increase on top of the current limit. Because the review involves external data sources, the result is delivered asynchronously via a `FACILITY.INCREASE.*` webhook event rather than synchronously in the response.
## Webhook events
Tilta delivers the underwriting result for an increase request via the following webhook events:
| Event | Description |
| ----------------------------- | ------------------------------------------------------------------------------------- |
| `FACILITY.INCREASE.ACCEPTED` | The increase was approved. The existing credit facility is updated to the new limit. |
| `FACILITY.INCREASE.REJECTED` | The increase was rejected. The existing credit facility remains at its current limit. |
| `FACILITY.INCREASE.IN_REVIEW` | Underwriting requires additional review and is not yet complete. |
The `requested_amount` is the desired **total** facility limit, not an incremental add-on. If the buyer's current limit is
€100,000 (`10000000`) and you want to raise it to €150,000, submit `requested_amount: 15000000`.
A buyer can only have one increase request under review at a time. Submitting another while one is outstanding returns a `409
Conflict` – wait for the `FACILITY.INCREASE.ACCEPTED` or `FACILITY.INCREASE.REJECTED` webhook first.
Monitor credit utilization with [List facilities](/api-reference/facilities/list-facilities). When a buyer's `used_amount`
consistently approaches their `total_amount`, request an increase before checkout starts failing for insufficient credit.
## OpenAPI
````yaml POST /v1/buyers/{external_id}/facility/increase
openapi: 3.0.0
info:
version: 0.0.1
title: Tilta API
description: Tilta API documentation
servers:
- url: https://api.tilta.io
description: Tilta Production API
- url: https://api.tilta-sandbox.io
description: Tilta Sandbox API
security: []
paths:
/v1/buyers/{external_id}/facility/increase:
post:
tags:
- Credit Facilities
summary: Request a credit facility increase
description: Request the increase of a credit facility for a buyer.
parameters:
- schema:
type: string
maxLength: 100
pattern: ^[a-zA-Z0-9-_]+$
description: Unique identifier of a buyer.
required: true
description: Unique identifier of a buyer.
name: external_id
in: path
requestBody:
content:
application/json:
schema:
type: object
properties:
requested_amount:
type: integer
minimum: 0
exclusiveMinimum: true
description: The total amount of credit limit requested.
comments:
type: string
nullable: true
maxLength: 500
description: Comments for the request.
required:
- requested_amount
responses:
'202':
description: ''
content:
application/json:
schema:
type: object
properties:
buyer_external_id:
type: string
maxLength: 100
pattern: ^[a-zA-Z0-9-_]+$
description: Unique identifier for buyer.
example: 5f6374a46a5e8e0104aa5cd4
status:
type: string
enum:
- PENDING
description: Status of the Pending facility
required:
- buyer_external_id
- status
description: The creation of a credit facility is pending.
'400':
description: ''
content:
application/json:
schema:
$ref: '#/components/schemas/badRequestSchema'
'401':
description: ''
content:
application/json:
schema:
$ref: '#/components/schemas/unauthorizedRequestSchema'
'404':
description: ''
content:
application/json:
schema:
$ref: '#/components/schemas/buyerNotFoundSchema'
'409':
description: ''
content:
application/json:
schema:
$ref: '#/components/schemas/requestFacilityIncreaseConflictSchema'
security:
- bearerAuth: []
components:
schemas:
badRequestSchema:
type: object
properties:
code:
type: string
description: Error code
example: BAD_REQUEST
error:
type: string
description: Error message for debugging purposes
example: Request validation failed. 1 issue found.
issues:
type: array
items:
type: object
properties:
code:
type: string
description: Issue code
example: INVALID_TYPE
path:
type: string
description: Issue path starting with body, params, querystring, or headers
example: body.registered_at
message:
type: string
description: Issue message for debugging purposes
example: Invalid type
required:
- code
- path
- message
description: List of issues
example:
- code: INVALID_TYPE
path: body.registered_at
message: Invalid type
required:
- code
- error
- issues
description: Bad Request, see error message for details.
example:
code: BAD_REQUEST
error: Request validation failed. 1 issue found.
issues:
- code: INVALID_TYPE
path: body.registered_at
message: Invalid type
unauthorizedRequestSchema:
type: object
properties:
error:
type: string
description: Error details.
example: Unauthorized
code:
type: string
description: Error code.
example: UNAUTHORIZED
required:
- error
- code
description: Unauthorized Request.
example:
error: Unauthorized
code: UNAUTHORIZED
buyerNotFoundSchema:
type: object
properties:
error:
type: string
description: Error details.
example: No Entity found
code:
type: string
description: Error code.
example: NOT_FOUND
required:
- error
- code
description: Buyer not found
example:
error: No Entity found
code: NOT_FOUND
requestFacilityIncreaseConflictSchema:
type: object
properties:
error:
type: string
description: Error details.
example: Buyer already has a pending facility increase request
code:
type: string
description: Error code.
example: CONFLICT
required:
- error
- code
description: Buyer already has a pending facility increase request
example:
error: Buyer already has a pending facility increase request
code: CONFLICT
securitySchemes:
bearerAuth:
type: http
scheme: bearer
description: Your Tilta API key, sent as `Bearer `.
````