Confirm Mapping
Confirm Mapping
Persist the user-chosen column mapping on the import session
POST
Confirm Mapping
Confirm Mapping
Persist the column mapping the user accepted (or adjusted) after reviewing suggestions. This transitions the session status fromparsed to mapped and makes the session resumable.
Confirming is optional — the Validate endpoint also accepts a mapping in the request body. However, confirming has two benefits: the mapping is persisted on the session (visible via List Sessions), and downstream calls behave consistently with what the user saw.
Request
Headers
Your API key for authenticationExample:
sk_live_1234567890abcdefYour organization UUIDExample:
a8315ef3-dd50-43f8-b7ce-d839e68d51faPath Parameters
UUID of the import sessionExample:
"11111111-1111-1111-1111-111111111111"Body Parameters
Map of
{target_column: source_column | suggestion_object | null}. Each key is a template column key. The value can be:- A string (source column name)
- A suggestion object from Suggest Mapping (the
source_columnis extracted automatically) nullto leave the target unmapped
{"origin": "origin", "destination": "destination", "weight": "weight_kg", "date": "date"}Response
UUID of the import session
The normalized flat mapping persisted on the session (
{target: source_column | null})Updated session status (typically
mapped)Example
Successful Response
Common Errors
401 Unauthorized
Cause: Missing or invalid API key403 Forbidden
Cause: The authenticated user is not a member of the organization404 Not Found
Cause: The import session does not exist or belongs to another organization422 Unprocessable Entity
Cause: Invalid or missing mapping objectRelated Endpoints
Suggest Mapping
Get auto-suggested mappings first
Validate Import
Validate rows with the chosen mapping

