Skip to main content
An httpRequestDefinition is a reusable HTTP request Roark fires to hand off outbound dialling to your own system. An agent endpoint whose outboundDialType is HTTP_REQUEST references one by name, and Roark calls it (substituting the number to dial) when a call should be placed.
It reconciles before agents, so an endpoint that references it in the same bundle resolves in one apply. Reference it only from a config-managed definition (declared in the bundle or a previous apply).

​
Signing secret

Roark mints an HMAC signing secret for each definition so your endpoint can verify a request genuinely came from Roark. It is not declared in your config: it is generated on create and returned exactly once, in the apply response’s signingSecret for that resource.
Capture the signingSecret from the apply response when the definition is first created: it cannot be read back afterwards. If you lose it, delete and re-apply the definition to mint a new one. Editing the other fields updates the definition in place and leaves the secret untouched.

​
Ownership

Once a definition is managed by config, it is read-only in the dashboard and over the API: PUT /v1/http-request-definition/{id} returns 409, and the response’s isConfigManaged is true. Change it in your config and re-apply, or detach it first to release it back to dashboard ownership.
Only outbound-dial definitions are managed here. Webhook and alert-delivery HTTP requests own their own lifecycle and are configured elsewhere.
For the full field reference of every kind, see the Config DSL reference schema.