Skip to main content
POST
Confirm Mapping
← Imports Persist the column mapping the user accepted (or adjusted) after reviewing suggestions. This transitions the session status from parsed 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

string
required
Your API key for authenticationExample: sk_live_1234567890abcdef
string
required
Your organization UUIDExample: a8315ef3-dd50-43f8-b7ce-d839e68d51fa

Path Parameters

string
required
UUID of the import sessionExample: "11111111-1111-1111-1111-111111111111"

Body Parameters

object
required
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_column is extracted automatically)
  • null to leave the target unmapped
Example: {"origin": "origin", "destination": "destination", "weight": "weight_kg", "date": "date"}

Response

string
UUID of the import session
object
The normalized flat mapping persisted on the session ({target: source_column | null})
string
Updated session status (typically mapped)

Example

Successful Response

Common Errors

401 Unauthorized

Cause: Missing or invalid API key

403 Forbidden

Cause: The authenticated user is not a member of the organization

404 Not Found

Cause: The import session does not exist or belongs to another organization. Both cases return the same response, so a session id from another organization is indistinguishable from one that does not exist.

422 Unprocessable Entity

Cause: Invalid or missing mapping object

Suggest Mapping

Get auto-suggested mappings first

Validate Import

Validate rows with the chosen mapping