Update all import mappings in bulk
Replaces all field mappings for an import in a single request. This is the primary way to configure how CSV columns map to entity fields.
What this does:
- Deletes all existing mappings for the import
- Creates new mappings from your request
- Automatically adds dependency mappings (e.g., if you map OrganizationMember, it will also create Organization mapping if needed)
- Validates that all column IDs exist in the import
- Triggers re-validation of all mappings
- Returns the updated mappings in AI format
AI Mapping Format: Each mapping specifies an entity type and its field mappings:
{
"mappings": [
{
"type": "Employee",
"fields": {
"firstName": { "mapTo": "column-uuid-here" },
"lastName": { "mapTo": "column-uuid-here" },
"email": { "mapTo": "column-uuid-here" },
"role": {
"mapTo": "column-uuid-here",
"valueMappings": { "Manager": "manager", "Developer": "developer" }
}
},
"customLookupFields": ["email"] // optional: fields to use for finding existing records
}
]
}
Field Mapping Properties:
mapTo: Required - The UUID of the CSV column (get column IDs from GET /{importId})defaultValue: Optional - Default value if CSV cell is emptyvalueMappings: Optional - Map CSV values to entity values (e.g., “Yes” → true, “Manager” → “manager”)
Custom Lookup Fields: Specify which fields should be used to find existing records for updates. If a record matches on these fields, it will be updated; otherwise, a new record will be created.
- Can include both built-in fields (e.g., “email”, “firstName”) and custom fields (e.g., “customField_abc123”)
- If not specified, uses the entity’s default
requiredToUpdatefields - Example: Use “email” for Employees, or a custom “externalId” field for Projects
Important Notes:
mapTomust be a column UUID from the import (get from GET /{importId} response), not a column name- All column IDs must exist in the import
- Dependencies are automatically created (e.g., Organization for OrganizationMember, Project for Task)
- Custom fields are referenced as
customField_{fieldId}in field names - After updating, run a dry-run to validate mappings before execution
/imports-management/{importId}/mappingsAuthorizationOAuth2 access token · headerrequiredapi:writeAuthorizationBearer token (JWT) · headerrequiredimportIdstringrequiredUnique identifier of the import
fieldsToReturnstringComma-separated list of top-level response fields to return. Overrides the endpoint compact default unless responseShape=full is used.
responseShapestringAdvanced override. Omit for the endpoint compact default. Use full only when you need the complete endpoint response, including nested fields that are not selectable with fieldsToReturn.
compactfullLT-Response-ShapestringAdvanced override. Set to full only when you need the complete endpoint response, including nested fields that are not selectable with fieldsToReturn.
fullapplication/jsonmappingsobject[]requiredArray of mapping configurations in AI format. Each mapping specifies an entity type and how CSV columns map to entity fields. This replaces all existing mappings for the import.
Show propertiesHide properties
objectcustomLookupFieldsstring[]Optional array of field names to use for finding existing records. Can include built-in fields (e.g., "email", "firstName") or custom fields (e.g., "customField_abc123"). If a record matches on these fields, it will be updated; otherwise, a new record will be created. If not provided, uses the entity's default requiredToUpdate fields.
fieldsobjectField mappings object. Keys are entity field names (or "customField_{fieldId}" for custom fields). Values are objects with: mapTo (required, CSV column UUID), defaultValue (optional), and valueMappings (optional, for enum conversions).
typestringEntity type to import: "Employee", "Organization", "OrganizationMember", "Project", "Task", or "TaskComment"
Mappings updated successfully
mappingsany[]requiredUpdated mappings in AI format, including any automatically added dependency mappings (e.g., Organization mapping if OrganizationMember was specified). Use these mappings to verify the final configuration.
successbooleanrequiredIndicates whether the mapping update was successful. If true, all mappings have been saved and validated.
Invalid mapping structure or column IDs
Unauthorized - Invalid or missing authentication token
Forbidden - Insufficient API scopes or permissions
Import not found