What Do the Performance Data API Integration Error Messages Mean?
Last updated: November 17, 2026
When Ambition rejects a request to a Performance Data API integration, it returns a 400 response with a list of errors. Each error has a message and an ID that tells you what went wrong.
Required permissions:
No special permission is required to read Performance Data API error responses.
Invalid JSON (import_parse_json)
What it means: The body couldn't be read as JSON.
How to fix it: Check for missing brackets, quotes, or commas.
Invalid CSV (import_parse_csv)
What it means: The body couldn't be read as CSV.
How to fix it: Check the headers and the separators between values.
Error in import data composition (import_transform_data)
What it means: The data doesn't match the integration's Field Mappings, such as a missing or misspelled field key.
How to fix it: Make sure that all fields match the Data Format page.
Invalid Data Chunk, missing one or more attributes (import_chunk_data_invalid)
What it means: Part of the data is missing required fields.
How to fix it: Ensure that the records contain all fields from the Data Format page.
Internal service error. Please try again. (import_backup_call_failed):
What it means: A problem on Ambition's side prevented the data from being successfully received.
How to fix it: Send the request again.
Note:
A 404 response means the integration's route isn't active or the integration has an open issue, rather than a problem with your data.