Skip to main content
GET
/
lead
/
{lead_id}
/
status
Update lead status (GET / pixel)
curl --request GET \
  --url https://{tenant}.techea.eu/api/v1/lead/{lead_id}/status
{
  "lead_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "event": "registration",
  "status": "received"
}
Functionally equivalent to the POST variant. Use this endpoint if your platform fires pixel-style callbacks — simple GET requests without a body.

​
Security

This endpoint requires a signed token to prevent unauthorized status updates. When TECHEA sends a lead to your platform, the postback URL is provided with a pre-signed token query parameter valid for that lead only: 
GET https://{tenant}.techea.eu/api/v1/lead/{lead_id}/status?token={signed_token}&event=registration
The token is an HMAC signature of lead_id + advertiser_id using a shared secret. Requests without a valid token are rejected with 401 Unauthorized.
Do not construct this URL manually. Always use the postback URL provided by TECHEA when the lead is delivered to your platform.

​
Event types

EventWhen to send
registrationCustomer completed registration
loan_issuedLoan approved and disbursed
loan_rejectedCustomer rejected after evaluation
loan_paidLoan fully repaid
loan_defaultedCustomer defaulted

Path Parameters

​
lead_id
string<uuid>
required

Query Parameters

​
event
enum<string>
required

Event type reported by the advertiser:

  • registration: customer registered with the advertiser
  • approved: product approved and issued
  • rejected: advertiser rejected the customer
  • completed: product lifecycle completed (e.g. fully repaid)
  • defaulted: customer defaulted
Available options:
registration,
approved,
rejected,
completed,
defaulted
​
ref
string

Advertiser's internal reference for this lead

Response

Status update received and processed

​
lead_id
string<uuid>
​
event
enum<string>

Event type reported by the advertiser:

  • registration: customer registered with the advertiser
  • approved: product approved and issued
  • rejected: advertiser rejected the customer
  • completed: product lifecycle completed (e.g. fully repaid)
  • defaulted: customer defaulted
Available options:
registration,
approved,
rejected,
completed,
defaulted
​
status
enum<string>
  • received: status update recorded and publisher notification triggered
  • ignored: update received but already processed (duplicate)
Available options:
received,
ignored