WorkspaceDarkLight
Contents

Developers

Build on Creditcrest

Every product is an HTTP API. JSON in, evidence out, nothing kept.

QuickstartAPI reference

Request
curl -s -X POST https://app.creditcresttechnologies.com.au/v1/statement \
  -H "authorization: Bearer $CREDITCREST_KEY" \
  -H 'content-type: text/csv' \
  --data-binary @statement.csv
Response · 200trimmed
{
  "income": {
    "verifiedMonthly": 5026.67
  },
  "commitments": {
    "monthly": 2150
  },
  "expenses": {
    "monthly": {
      "essential": 3497.94,
      "discretionary": 162.68
    }
  }
}
QuickstartRead a statement in three calls. GuidesChain products the way a loan does. API reference105 endpoints across 23 products. ChangelogWhat was added, and when.

How it behaves

Stateless
Nothing sent is stored. A request is read, answered and dropped.
Evidence attached
Figures come back with the transactions, rules or provisions behind them.
Versioned
Everything is under /v1. The changelog lists each addition.
Plain errors
A 4xx with a JSON body that says what to send instead.

Access

A sandbox key is one call, POST /v1/keys/sandbox, and lasts 30 days. Live keys are issued per lender, for the products it uses: hello@creditcresttechnologies.com.au. How keys work.