Skip to main content
Bindbee normalizes every record it syncs into a unified model, so an employee from Workday and an employee from BambooHR arrive in your application in exactly the same shape. Raw data is the layer underneath. It is the payload Bindbee received from the third-party system before normalization, returned alongside the normalized fields on request. You need it in three situations:
  • Confirming how a value was normalized
  • Discovering a provider field the unified schema does not cover
  • Debugging a discrepancy a customer has reported
It is a diagnostic and discovery tool, not a data source to build on — Using raw data safely explains why.

​
Requesting raw data

Add include_raw_data=true to any list or retrieve request. It defaults to false.
The raw_data object appears on each record:
Reading it against the normalized fields shows exactly what happened: Active became ACTIVE, S became SINGLE, and badgeId has no unified equivalent. The first two are enum normalization; the third is what custom fields exist for.
Raw data is available on the 88 data endpoints across HRIS, ATS and LMS. It is not returned by the connector, integration, webhook, custom field or meta endpoints, since those describe Bindbee’s own resources rather than synced third-party records.

Custom fields

Map a raw value onto a stable key using JMESPath.

Get Raw Data

API reference for inspecting a connector’s upstream payload.

Preview

Test a JMESPath expression against a connector before saving it.

Enum values

Why a source value became the normalized one you see.