Skip to main content
POST
Create a trigger link

Authorizations

x-api-key
string
header
required

Body

application/json

Mint a trigger link for a hook topic.

ttl_seconds is REQUIRED (no default ⇒ the key must be present) and STRICT ("3600", 3600.0, 3600.5 and bools all reject under one regime): a positive int is a timed link, null is a permanent link, and 0/negative is a loud 400 — expiry is the creator's explicit choice with no default and no product ceiling. execution_key is the api-key identity the link's dispatch is gated on — the link dies with the key — and the creator must be allowed to delegate it; each hook the dispatch reaches still fires as its OWN bound key. require_api_key makes the link's door demand an authenticated principal ON TOP of the token — one the authentication backend admits, and, when that principal is governed by a ROLE, one the ordinary hooks-tag level pass admits at the request's method (read for GET, write for POST); the governing policy is the OWNER's for an owned key, so a key escapes that pass exactly when its governing policy is admin or carries no role pointer. The default is token-only — the QR-on-a-wall case. topic must be non-empty, the same rule the stored record enforces, so the mint door never writes a link its own restore would refuse. tool_kwargs (optional) is stored on the link and merged into every fired hook's input BELOW that hook's own static tool_kwargs, so it supplies only the arguments the hook's author left unpinned — a colliding key stays the author's.

execution_key
string
required
Minimum string length: 1
topic
string
required
Minimum string length: 1
ttl_seconds
integer | null
required
name
string | null
require_api_key
boolean
default:false
tool_kwargs
Tool Kwargs · object | null

Response

Success.

data
any
required