Submit a Core form as a technician
Provisioning forms only — a lookup-kind form (see the catalogue) has no run to start and is refused with 400. Same approval gate and compiled workflow as the Core app’s run page. submitter is your signed-in person and is recorded on the request; credential delivery (email / ticket) follows the form’s configuration using that email. secret — onboarding’s one-time credential — is returned once, here only: it is never stored, so an Idempotency-Key replay of this call returns "secret": null with an idempotentReplayNote. Requires the core:run key scope.
Authorizations
Organisation API key. Scoped operations carry x-triggr-scope; the scopes themselves are described in x-triggr-scopes.
Headers
OPTIONAL — omit it and this operation behaves exactly as it always has. A unique value (a UUID) you choose per request. A retry with the same key and the same method, path and body within 24 hours gets the first response replayed (status and body, with Idempotent-Replayed: true) instead of running again; the same key with a different request is refused with 422. A 5xx is not stored, so that retry runs. A one-time credential is never stored: on a replay any secret is null, with an idempotentReplayNote explaining it.
1 - 255Path Parameters
Body
Response
OK
running, awaiting_approval Present only on an Idempotency-Key replay whose original response carried a one-time credential: says that the value is shown only in the original response and how to issue a fresh one
The one-time credential, shown ONCE. null on an Idempotency-Key replay — see idempotentReplayNote

