ISYNTH · API & MCP
API and field reference
Look up fields and request structures for your integration. For a first connection, start with the relevant guide for workflow and permissions.
Column names, meaning and units
Keep original column names and map them to standard fields. Preserve units already present in cells; declare a column unit for bare numbers when known. Leave unreported facts blank and keep names and structures as reported.
| Source column | Standard field | Source unit |
|---|---|---|
| Substrate | reactant_1_structure | — |
| Temperature | temperature | K |
| Yield | product_yield_percent | % |
When cells already include units, no column unit declaration is needed. Use the same column_mapping and source_units for validation and upload.
Explore the tabular data specification →Retrieval fields
These fields define search conditions. For upload columns and meanings, consult the tabular data specification or call get_reaction_contract.
Loading…
Developer reference
Schemas let software validate requests; they are not forms to fill out. Open the interface you need. get_schema returns the same definitions.
Raw API definitions (JSON)