What is an import API?
Turn external records into clear, validated application data. A practical introduction to contracts, transformations, errors, and job lifecycles.
Read the guideDeveloper documentation
Good imports start
with clear contracts.
Small examples, explicit transformations, and understandable results. Start locally, then adapt the concepts to your own destination.
Example reference
Inspect the source shape, mapped fields, validation rules, and outcome record.
Open guideExample workflows
Connect record mapping, content review, and prompt versioning to a practical first test.
Open guideSee the change.
Understand the result.
The quickstart uses a fixed source dataset and runs mapping and validation in the browser. It does not make a network request, upload a file, or write into an application.
The downloadable examples give you the same source and outcome to inspect without running JavaScript.
Browse example filesAn error worth understanding
{
"source_record": 3,
"field": "external_id",
"code": "required",
"message": "Supply a stable customer identifier."
}From Import Notes
A little reading. A better workflow.
Map it. Validate it. Understand it.
Separate transformations from validation, make every conversion explainable, and design useful errors around an explicit destination contract.
Read the guide
Retry without the uncertainty.
Separate logical jobs from processing attempts and make duplicate handling, partial outcomes, and uncertain commits understandable.
Read the guide