Skip to main content
Null Field Responses

There are a few reasons you may be seeing null field responses for a specific integration

Updated over a week ago

An API response from Merge can return null values for certain common model fields. This might happen for a couple of reasons:

  1. Common Model support - The specific integration does not support the field in our Common Model (find what fields are available in each integrations: here).

  2. Third-party support - The field is supported, but not filled out in the third-party platform.

  3. Sync status - The data is not yet available to Merge. If the information is currently syncing from the third-party platform to Merge, the field values can appear as null. As best practice, Merge recommends waiting until a sync is DONE.

    GET /sync-status endpoint

    You can find documentation regarding the sync-status endpoint here.

  4. Field Scopes - The given field has been disabled through the configuration scope of the integration (Help Center article). Note: this feature is only available to customers on our Core, Professional, and Enterprise plans.

  5. Permissioning - The permissions associated with the user authenticating do not grant them visibility to these field values (i.e. they are not an admin or their API key has restricted access).


  1. Clicking the 'Resync all' button on the Linked Account page can help with some cases - but only use this sparingly and when needed!

2. If you are still unsure why you are seeing null data in your response, you are welcome to reach out to [email protected]!

Did this answer your question?