Retry without the uncertainty.
Separate logical jobs from processing attempts and make duplicate handling, partial outcomes, and uncertain commits understandable.
Read the guideImport Notes · Topic
Data import
Contracts, record identity, and the handoff from external values to destination changes. Start with an explicit schema, then decide how corrections and repeated jobs behave.
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
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 guideConnect the ideas to a workflow
Use these readings to define a small, testable handoff: an approved source, explicit destination fields, and a correction path for ambiguous values. Keep the original representation visible while checking the proposed transformation.
Explore the import categories for source-specific decisions or follow the local developer quickstart to see a complete synthetic mapping and validation result.