Skip to main content
POST
Validate Import
Run validation on the import session using the specified column mapping. Returns a summary of valid/error rows plus paginated row-level validation results. Use errors_only=true to focus on rows that need attention.
You can optionally include value_mappings to pre-resolve category values the user remapped by hand (e.g. mapping "Camión" → "truck" for the vehicle_type column).

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"

Query Parameters

integer
default:"1"
Page number (1-indexed)
integer
default:"50"
Rows per page (1–500)
boolean
default:"false"
When true, only return rows with validation errors

Body Parameters

object
required
Column mapping to use for validation: {target_column: source_column | null}Example: {"origin": "origin", "destination": "destination", "weight": "weight_kg"}
object
User-defined value remappings for category columns. Map of {target_column: {raw_value: canonical_value}}.Leave it out to keep the value mappings of the previous validation (the ones GET /status returns), so validating again with only the column mapping does not lose them. Send {} to clear them.Example: {"vehicle_type": {"Camión": "truck", "Furgoneta": "van"}}
object
Session context to store before validating, so the rows validate with it, for example the facility of a wastes file: {"facility_id": "…"}. String values; only the template’s required and submit context fields are accepted. Values are checked as on create (facility access, transport direction), and a field the template makes immutable keeps the value it has. Omit it to keep the session’s context.

Response

string
UUID of the import session
integer
Total number of data rows
integer
Number of rows that passed validation
integer
Number of rows with at least one validation error
object
Error counts per column key. Example: {"weight": 2, "date": 1}
object
Warnings about the overall data shape (e.g. missing columns)
array[object]
Paginated row-level validation output
integer
Current page number
integer
Rows per page
integer
Total number of pages

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.
Cause: The session’s project is no longer one your organization can import into (for example, the organization was unlinked from it). Every step of the session answers this, not only the submit. Create a new session on a project you work in.

400 Bad Request

Cause: context names a field the session’s template does not take

409 Conflict

Cause: context changes a field the template makes immutable once set

Confirm Mapping

Persist the mapping before validating

Submit Import

Submit the validated session for processing

Get Unique Values

Inspect category values before validation

Import Overview

Full workflow guide