Fincheck

Changelog

Changes to the FincheckEngine API that affect your integration.

Changes to the FincheckEngine API that affect your integration, newest first.

30 September 2026

v2 responses and requests tightened

These changes apply to v2 integrations only. v1 is unchanged.

  • Offers. Matches no longer include company_logo_path, live_score, or userable. partner_type and probability_conditions are at the top level of each match, and live_quotes carries the partner's quote.
  • Typed requests. POST /lead and POST /offer must be sent as application/json (otherwise 415), with each field in its JSON type. Numeric strings such as "25000" and words such as "yes" are rejected with 422 naming the field.
  • Removed request fields. The singular partner_id on POST /lead and POST /offer, and live_score on POST /accept, are rejected with 422. Use partner_ids and live_quotes.
  • Response bodies. code is no longer returned; read the HTTP status. Errors use message throughout, and validation errors say Validation failed.
  • Lead lookups. GET /lead/{hashid} and GET /accept/{hashid}/link return only your own leads. Any other id returns 404.

See Upgrade to v2 for before-and-after examples.

29 September 2026

API v1 deprecated

API v1 is closed to new integrations and will be retired. No retirement date has been set yet; it will be announced here with advance notice.