Custom Fields allow you to extend Bindbee’s unified models with additional fields specific to your use case. This feature enables you to extract any data available in the third party API response and include it in your unified model response.
Custom Fields can be configured at two levels:
When the same custom field name exists at both levels, the connector-level field takes precedence.
Creating a Custom field involves two main steps:
Step 1: Create New Field
Step 2: Configure Field Mappings
Name of custom field must be unique and naming should follow snake_case
After creating the field, you’ll be redirected to the mapping configuration screen where you can set up both Connector Level
and Organization Level
mappings.
</>
button to view the raw JSON response and click the desired fieldIf your JSON Path (JMESPath) expression is incorrect, then while requesting
the custom_fields
via APIs, you will not receive an error. Instead, the API
will respond with "INVALID_JSON_PATH"
mapped to the incorrectly configured
field. Ensure that all JMESPath expressions are valid to retrieve the intended
data correctly.
</>
button to view the raw JSON response and click the desired fieldYou can add multiple mappings to a single custom field by clicking the “Add New” button and repeating the process for different connectors or integrations.
To include custom fields in your API responses, add the query parameter include_custom_fields=true
to your requests:
if you are trying to get Custom Fields for employees
model your request will look like this:
Example response with custom fields:
Naming Conventions
JSON Path(JMESPath) Expressions
Organization vs Connector Level Mapping
For more details on How to write custom JMESPath Expression visit JMESPath Documentation