Developer blueprint
A clear contract.
A traceable response.
Plan how source records enter the system and how a mapping decision returns to your platform.
Integration blueprint. The examples below describe a proposed production contract. This website does not expose a live supplier or mapping API.
Start with the source.
Codes are identifiers. Keep them as strings, even when they look like numbers.
| Field | Type | Meaning | Example |
|---|---|---|---|
| supplier | string | Your stable supplier namespace. | supplier-a |
| code | string | Original supplier hotel code, including leading zeros. | 000726 |
| name | string | Property name as received. | The Marina House |
| country | string | Two-letter country code. | AE |
| city / address | string | Locality and address evidence. | Dubai / Marina Walk |
| lat / lng | number | Latitude [-90,90], longitude [-180,180]. | 25.0802 / 55.1409 |
| masterId | string, optional | An existing approved master identity. | TH-000123 or TRV-10001 |
| status | string, optional | Source profile status, independent of identity. | active / inactive |
Make the response useful.
Return the decision, source identity, reasons, and policy version together.
EXAMPLE REQUEST · JSON
{
"supplier": "supplier-a",
"supplierHotelCode": "000726",
"property": {
"name": "The Marina House",
"country": "AE",
"city": "Dubai",
"latitude": 25.0802,
"longitude": 55.1409
},
"policy": {
"version": "demo-1",
"reviewOnConflict": true
}
}ILLUSTRATIVE RESPONSE · JSON
{
"masterId": "TRV-10001",
"sourceKey": {
"supplier": "supplier-a",
"hotelCode": "000726"
},
"decision": "mapped",
"method": "deterministic-demo",
"score": 98,
"evidence": [
"name corroborated",
"country consistent",
"location corroborated"
],
"scoreIsProbability": false
}Illustrative response values explain the contract; they are not benchmark results or an active API response.
Production considerations
Design for the
next supplier update.
- Authenticate integrations and scope each credential to its tenant and suppliers.
- Use idempotency keys, batch checksums, schema validation, and versioned mappings.
- Retain reviewer decisions with an actor, timestamp, reason, source version and policy version.
- Stage changed evidence for review before replacing an approved relationship.
- Test precision and coverage on independently labeled samples before adopting a new model.
Bring your data together
A clearer identity starts here.
Explore the mapping workflow. Build a brief around your data.