Lendicity
API v1
Server-to-server or pixel

Commission Callback API

A simple URL your company calls when it earns a commission on a lead Lendicity sent you. The call is tied back to the originating request ID and the amount is added to that lead's revenue in Lendicity reporting.

Overview

When a lead we referred results in a commissionable event on your side (for example a funded account or a completed sale), call the callback URL with our request ID and the commission amount. Lendicity records the call, attributes the amount to the original lead, and includes it in revenue reporting alongside all other revenue for that lead.

The callback is a plain GET request, so it works equally well as a server-to-server call, a tracking pixel, or a simple link fired from your systems. The response is a tiny JSON confirmation you can safely ignore.

To get started, contact Lendicity to receive your own key and client identifier. The key is unique to your company and both values are required on every call. If a key is ever exposed, ask Lendicity to issue a replacement and the old one stops working immediately.

Endpoint

GEThttps://www.lendicity.com/api/public/v1/commission

A complete example with every parameter:

https://www.lendicity.com/api/public/v1/commission
  ?key=YOUR_SHARED_KEY
  &requestId=104201
  &client=YOUR_CLIENT_CODE
  &commission=12.50
  &ref=order-98765
  &status=funded

Parameters

Authentication

key
stringrequired The key Lendicity issues your company. For server-to-server calls you may instead send it as Authorization: Bearer <key> and omit the query parameter. Calls with a missing or wrong key are refused and nothing is recorded.

Commission details

requestId
integerrequired The Lendicity request ID the commission belongs to. This is the ID supplied to you with the original lead. Unknown IDs are refused with a clear error so integration problems surface early.
client
stringrequired Your client identifier, assigned by Lendicity. Unknown identifiers are refused, so a typo cannot land revenue in the wrong place.
commission
numberrequired The commission amount in dollars (for example 12.50). Zero or more, up to 4 decimal places, with a maximum of 100,000.
ref
stringoptional Your own reference for the event (order number, transaction ID, and so on). Strongly recommended: it is used for repeat protection, and the same client and reference is only ever recorded once.
status
stringoptional Free text describing the event, for example funded.
test
0/1 or true/falseoptional Set test=1 while integrating. Test calls are recorded against test traffic and stay out of revenue figures.

Responses

A successful first call returns HTTP 201:

{
  "ok": true,
  "id": "9c1f…",
  "requestId": 104201,
  "commission": 12.50,
  "duplicate": false,
  "test": false
}

Error responses:

401
Unauthorizedoptional Missing or incorrect key. Nothing is recorded.
404
Not foundoptional Unknown client identifier or unknown request ID.
422
Validation failedoptional A parameter is missing or invalid. The response includes per-field details.

Repeats & testing

If you send the same ref twice, the repeat is acknowledged with HTTP 200 and "duplicate": true, but the amount is only recorded once. If you do not send a ref, a repeat of the same client, request ID and amount within 24 hours is treated the same way.

Every call is stored exactly as received, together with the time and calling address, so any dispute can be checked later.

Before going live, fire a call with test=1 and confirm with Lendicity that it arrived. Test calls never affect revenue figures.