Parse a table and propose a column mapping
Dry run before /batch-tasks: shows how the columns map to template variables. Creates nothing and costs nothing. variables are the columns the table is expected to carry — what a caller supplies; for a template that computes some of its values, inputs (InputDescriptor) names what it computes from them. A computed value is never an expected column and is never reported unmatched, but a column named after one maps onto it as an explicit override.
Request
- Base URL: https://rendry.io/api/v1
- URL: https://rendry.io/api/v1/batch-tasks/preview
- Auth: one of:
- HTTP bearer
- HTTP bearer
- HTTP bearer
Headers
Browser/OAuth current member account selector. API keys/embed credentials are bound to their persisted account and reject another account. Omitting this header selects the browser actor personal account.
Request body
Response
Proposed mapping and the price of the run
Changes
No recorded changes to this operation across all 1 revision of this API.