How Do I Format Data for a Performance Data API Integration?
Last updated: November 17, 2026
Every request your developers post to a Performance Data API integration has to match the settings saved on that integration's Data Format page, down to the spelling and capitalization of each key. A request that doesn't match will be rejected with a 400 response listing what went wrong.
Required permissions:
The Integrations: Edit permission is required to view and edit a Performance Data API integration's Data Format page.
Find the Format Your Data Must Follow
Head to Admin --> Data --> Integrations.
Click on the integration's name on the Enabled tab.
Click on Data Format in the side menu.
Check whether JSON or CSV is selected under Data Format. This is the format every request must use.
Check whether Records or Daily Totals is selected under Data Schema. With Records, each entry is one activity. With Daily Totals, each entry is one employee's total for one day.
Copy every key listed in the Field Key column of the Field Mappings table and share them with your developers.
Structure JSON Data
Send a list of objects: Each object in the list is one entry. A single object on its own will be read as one entry.
Include every field key: Each object needs every key from the Field Key column, spelled and capitalized exactly as it is on the Data Format page.
Flatten nested data: If your keys sit inside nested objects or lists, set up the JSON Transformer section on the Data Format page before sending data.
A Records request with the keys id, email, date, and talk_time would look like this:
[
{"id": "call-1001", "email": "jordan@example.com", "date": "2026-11-17T14:30:00-05:00", "talk_time": 12.5},
{"id": "call-1002", "email": "riley@example.com", "date": "2026-11-17T15:05:00-05:00", "talk_time": 8}
]Structure CSV Data
Start with a header row: The first row must list every key from the Field Key column, spelled and capitalized exactly the same way. Column order doesn't matter.
Add one row per entry: Each row after the header is one activity or one daily total, with values separated by commas.
The same Records data sent as a CSV would look like this:
id,email,date,talk_time
call-1001,jordan@example.com,2026-11-17T14:30:00-05:00,12.5
call-1002,riley@example.com,2026-11-17T15:05:00-05:00,8Format Dates and Numbers
Dates and times: Use a standard format such as 2026-11-17 or 2026-11-17T14:30:00-05:00. Unix timestamps are also accepted. Times without a time zone offset will be read as UTC.
Date fields: Keys set to Date in the Field Type drop-down menu only keep the day, so any time included will be dropped.
Numbers: Symbols such as dollar signs and commas will be removed, so "$1,250.00" will be read as 1250.