Context Dev · Company

Context API / Identify brand from transaction data

Endpoint specially designed for platforms that want to identify transaction data by the transaction title.

Private Gateway connection

Data below comes from the configured private Gateway. Provider activation remains governed by its evidence and policy gates.

unverifiedRequest shape unavailableUnverified

Published API evidence

Public metadata only. Response bodies, credentials, and internal review notes are never displayed.

No verification date is claimed. No response capture is claimed.

Request parameters

city query · optional
Optional city name to prioritize when searching for the brand.
country_gl query · optional
Two-letter ISO 3166-1 alpha-2 country code (GL parameter) used to localize search.
force_language query · optional
high_confidence_only query · optional
When set to true, the API will perform an additional verification steps to ensure the identified brand matches the transaction with high confidence.
maxSpeed query · optional
Optional parameter to optimize the API call for maximum speed. When set to true, the API will skip time-consuming operations for faster response at the cost of less comprehensive data.
mcc query · optional
Optional Merchant Category Code (MCC) to help identify the business category/industry.
phone query · optional
Optional phone number from the transaction to help verify brand match.
tags query · optional
Optional tags for tracking usage. Up to 20 tags, each 1 to 50 characters.
timeoutMS query · optional
Optional timeout in milliseconds for the request. If the request takes longer than this value, it will be aborted with a 408 status code. Maximum allowed value is 300000ms (5 minutes).
transaction_info query · required
Transaction information to identify the brand