Skip to main content

​
Format Requirements

RequirementValue
EncodingUTF-8
DelimiterComma (,)
HeadersFirst row must contain column headers matching field names exactly
QuotingUse double quotes for fields containing commas or newlines
Date FormatISO 8601 date (2024-01-15)
DateTime FormatISO 8601 datetime (2024-01-15T10:30:00)
Boolean Valuestrue or false (case-insensitive)
UUID FormatStandard UUID (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)
Empty ValuesLeave field empty for optional null values
Decimal NumbersUse period as decimal separator (e.g., 1234.56)

​
Example

first_name,last_name,date_of_birth,social_security_number,personal_address_line_1,personal_address_city,personal_address_state,personal_address_zip,phone_number,personal_email
Jane,Doe,1990-01-15,1234,123 Main St,San Francisco,CA,94102,4155551234,jane@example.com
John,Smith,1985-06-20,5678,456 Oak Ave,Los Angeles,CA,90001,3105559876,john@example.com

​
Common Pitfalls

Column headers must match field names exactly — including underscores and casing. Refer to the API Reference for the correct field names for each template.
Use ISO 8601 format only. Dates like 01/15/2024 or Jan 15, 2024 will be rejected. Use 2024-01-15 instead.
Avoid leading/trailing whitespace in headers and values. Some SFTP clients or export tools add invisible whitespace that causes field matching to fail.
If exporting from Excel, ensure you save as “CSV UTF-8” not “CSV”. The latter may include a BOM (byte order mark) that interferes with header parsing.