Skip to main content
The Lending API lets a financial platform offer Cr3dentials-underwritten loans to its customers. Every call goes from your platform to Cr3dentials: you send applications, acceptances and events, and we answer with decisions, loan views and the money steps your platform performs. Cr3dentials never calls your core systems and never moves money in your accounts.

How it works

Basics

Authentication

The Lending API uses OAuth 2.0 client credentials. Tokens last 900 seconds; request a new one on a 401.
Send the token on every call:

Idempotency

Every POST needs an Idempotency-Key header of 1 to 255 visible ASCII characters. For events, use the event_id as the key.

Errors and retries

A 400 lists each bad field in details, by name only, never its value.

Webhooks

Webhooks are optional. If your platform can receive HTTPS POSTs, register a webhook URL with us and we send these as they happen: Each is signed with HMAC-SHA256: verify X-Signature against X-Timestamp and the raw body, as the API Reference describes. Delivery is at least once, so deduplicate by event_id. Everything a webhook carries is also in the loan and application views, so a platform that can’t receive webhooks reads those instead.