Partner link
Without writing a single line of code. We give you a link of your own and every application that arrives through it is recorded under your name.
- Ready the same day
- The source travels with the application
- We handle the process
Build sales-based funding into your platform: create applications, check their status and receive changes in real time. Without taking the merchant out of your product.
curl -X POST https://api.lenditas.co.uk/v1/applications \
-H "Authorization: Bearer $LENDITAS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"business": {
"legal_name": "Sunrise Café Ltd",
"tax_id": "GB123456789",
"months_trading": 42
},
"financing": {
"requested_amount": 2500000,
"currency": "GBP",
"purpose": "inventory"
}
}'
Depending on what you want to build and how much development time you have.
Without writing a single line of code. We give you a link of your own and every application that arrives through it is recorded under your name.
The funding lives inside your product. Your platform creates the applications, checks their status and receives every change by webhook.
The API is REST over HTTPS. Requests and responses are in JSON and every amount is expressed in pence, as whole numbers, with the currency declared separately. That way there are no rounding errors with decimals.
A typical integration runs like this:
The API is in early access: credentials are issued per partner during onboarding. Get in touch and we'll give you sandbox access so you can start integrating.
Two independent environments, with separate credentials. In the sandbox you can create as many applications as you like: they are not assessed and they never reach our team.
| Environment | Base URL | Key |
|---|---|---|
| Sandbox | https://sandbox.api.lenditas.co.uk/v1 | sk_test_… |
| Production | https://api.lenditas.co.uk/v1 | sk_live_… |
Every request carries your key in the header Authorization. The key identifies your company, so every application created with it is attributed to your channel automatically: you don't need to send a partner identifier of any kind.
Authorization: Bearer sk_live_••••••••••••••••
Content-Type: application/json
Idempotency-Key: 9f2c7b14-3a8e-4c21-b5d7-0e6f1a2b3c4d
The key always stays on the server. Never in the browser, in a mobile app or in a repository: anyone who holds it can create applications in your name.
/v1/applicationsRegisters a new funding application. Returns the application identifier, which you will use in all the other calls.
| Field | Type | Description |
|---|---|---|
business.legal_name | string | Full registered name. Required. |
business.tax_id | string | Company number or VAT number of the merchant. Required. |
business.months_trading | integer | Months trading. Required. |
business.sector | string | Business sector. Optional. |
contact.name | string | Contact person. Required. |
contact.email | string | Contact email. Required. |
contact.phone | string | Phone in international format. Optional. |
financing.requested_amount | integer | Amount requested, in pence. Required. |
financing.currency | string | ISO 4217 currency. For now GBP. |
financing.purpose | string | inventory, suppliers, equipment, refurbishment o working_capital. |
metadata | object | Your own data. We return it to you unchanged in the webhooks. |
curl -X POST https://api.lenditas.co.uk/v1/applications \
-H "Authorization: Bearer $LENDITAS_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: 9f2c7b14-3a8e-4c21-b5d7-0e6f1a2b3c4d" \
-d '{
"business": {
"legal_name": "Sunrise Café Ltd",
"tax_id": "GB123456789",
"months_trading": 42,
"sector": "hospitality"
},
"contact": {
"name": "James Smith",
"email": "james@sunrisecafe.co.uk",
"phone": "+447700900123"
},
"financing": {
"requested_amount": 2500000,
"currency": "GBP",
"purpose": "inventory"
},
"metadata": { "case_id": "A-9931" }
}'
const res = await fetch("https://api.lenditas.co.uk/v1/applications", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.LENDITAS_API_KEY}`,
"Content-Type": "application/json",
"Idempotency-Key": crypto.randomUUID()
},
body: JSON.stringify({
business: { legal_name: "Sunrise Café Ltd", tax_id: "GB123456789", months_trading: 42 },
contact: { name: "James Smith", email: "james@sunrisecafe.co.uk" },
financing:{ requested_amount: 2500000, currency: "GBP", purpose: "inventory" }
})
});
const solicitud = await res.json();
console.log(solicitud.id); // app_8f2b1c4d9e
$ch = curl_init("https://api.lenditas.co.uk/v1/applications");
curl_setopt_array($ch, [
CURLOPT_POST => true,
CURLOPT_RETURNTRANSFER => true,
CURLOPT_HTTPHEADER => [
"Authorization: Bearer " . getenv("LENDITAS_API_KEY"),
"Content-Type: application/json"
],
CURLOPT_POSTFIELDS => json_encode([
"business" => ["legal_name" => "Sunrise Café Ltd", "tax_id" => "GB123456789", "months_trading" => 42],
"contact" => ["name" => "James Smith", "email" => "james@sunrisecafe.co.uk"],
"financing" => ["requested_amount" => 2500000, "currency" => "GBP", "purpose" => "inventory"]
])
]);
$solicitud = json_decode(curl_exec($ch), true);
{
"id": "app_8f2b1c4d9e",
"status": "received",
"business": { "legal_name": "Sunrise Café Ltd", "tax_id": "GB123456789" },
"financing": { "requested_amount": 2500000, "currency": "GBP" },
"metadata": { "case_id": "A-9931" },
"created_at": "2026-11-18T14:32:07Z"
}
/v1/applications/{id}Returns the full application. Use it to show the status in your own dashboard; to find out about changes the moment they happen, listen for webhooks instead of polling in a loop.
{
"id": "app_8f2b1c4d9e",
"status": "under_review",
"business": { "legal_name": "Sunrise Café Ltd", "months_trading": 42 },
"financing": { "requested_amount": 2500000, "currency": "GBP" },
"documents": [
{ "type": "bank_statement", "status": "received", "source": "open_banking" },
{ "type": "id_document", "status": "pending", "source": "upload" }
],
"updated_at": "2026-11-18T16:04:51Z"
}
/v1/applications/{id}/documentsMost of the paperwork arrives on its own through open banking when the merchant connects their bank. This endpoint is for whatever is left over: photo ID, a particular invoice or whatever we ask for in each case.
It is sent as multipart/form-data. Accepts PDF, JPG and PNG up to 10 MB.
curl -X POST https://api.lenditas.co.uk/v1/applications/app_8f2b1c4d9e/documents \
-H "Authorization: Bearer $LENDITAS_API_KEY" \
-F "type=id_document" \
-F "file=@dni.pdf"
An application moves through these statuses. The changes are decided by our underwriting team: through the API they can be read, not modified.
| Status | What it means |
|---|---|
received | The application is registered and attributed to your channel. |
documents_pending | Documents are still missing from the merchant. |
under_review | Our team is assessing the trading activity and the cash flows. |
offer_available | There is an offer ready for the merchant. |
accepted | The merchant has accepted the offer. |
declined | The application is not going ahead. |
expired | The application expired without a response. |
When an application changes status, we send a POST to the URL you give us. It is the recommended way to keep your own system up to date.
application.status_changedPOST https://tu-plataforma.com/webhooks/lenditas
Lenditas-Signature: t=1763478291,v1=5f8c2a9d1e4b7306c5a8f2d1e4b73065
{
"id": "evt_3c7a9f1e2d",
"type": "application.status_changed",
"created_at": "2026-11-18T16:04:51Z",
"data": {
"application_id": "app_8f2b1c4d9e",
"status": "offer_available",
"previous_status": "under_review",
"metadata": { "case_id": "A-9931" }
}
}
Every delivery carries the header Lenditas-Signature, with the timestamp and an HMAC-SHA256 of the body using the webhook secret. Always check it before treating the notification as genuine.
const crypto = require("crypto");
function firmaValida(cuerpoCrudo, cabecera, secreto) {
const [t, v1] = cabecera.split(",").map(p => p.split("=")[1]);
// anything older than 5 minutes is rejected
if (Math.abs(Date.now() / 1000 - Number(t)) > 300) return false;
const esperada = crypto
.createHmac("sha256", secreto)
.update(`${t}.${cuerpoCrudo}`)
.digest("hex");
return crypto.timingSafeEqual(Buffer.from(v1), Buffer.from(esperada));
}
Respond 200 as soon as you receive the notification, and process afterwards. If you take more than 10 seconds or return an error, we retry with increasing backoff for 24 hours.
Errors use the usual HTTP codes and return a body in the same format, so you can handle them all the same way.
{
"error": {
"type": "validation_failed",
"message": "The amount requested is outside the permitted range.",
"param": "financing.requested_amount",
"request_id": "req_7d2e1a9c4b"
}
}
| Code | Type | When it happens |
|---|---|---|
| 400 | invalid_request | The JSON is malformed. |
| 401 | unauthorized | The key is missing or invalid. |
| 403 | forbidden | Your key does not have permission for that application. |
| 404 | not_found | The application does not exist. |
| 409 | duplicate_request | There was already a request with that Idempotency-Key and a different body. |
| 422 | validation_failed | A required field is missing or its value is invalid. |
| 429 | rate_limited | You have exceeded the rate limit. |
| 500 | server_error | A failure on our side. Always include the request_id if you get in touch. |
The default limit is 120 requests per minute and per key. Every response tells you where you stand:
RateLimit-Limit: 120
RateLimit-Remaining: 117
RateLimit-Reset: 41
If your volume needs more, it is adjusted during onboarding. When creating applications, always send a Idempotency-Key unique per operation: if the connection drops and you retry with the same key, we return the original application instead of creating a duplicate.
Tell us what platform you have and which merchants you work with. We'll give you sandbox access and define the technical scope with you.
Tell us about your business and we'll prepare your offer.
Leave us your details and we'll be in touch to assess your proposal.