Launch an Ironclad workflow programmatically using its schema-driven launch form API

Steps

1. GET the workflow schema for the target template ID with the ?form=launch query parameter to retrieve the launch form's field definitions (Field API Name, Field Type, Field Display Name, and required/conditionally-required flags).
2. Cross-check required and conditionally required launch-form fields against the workflow's design in Workflow Designer's Create tab to confirm what must be supplied.
3. POST to /public/api/v1/workflows with an attributes object containing values for every required and conditionally-required field (fields with defaults can be omitted to use the default) to launch the workflow synchronously; this requires the public.workflows.createWorkflows OAuth scope.
4. For high-volume launches, use the asynchronous bulk-launch endpoint instead of looping single synchronous launch calls.
5. Handle rejected launches caused by missing or incorrectly formatted attribute data for required fields - the API fails the request outright rather than partially launching the workflow.