webhook.create

Makes a temporary public URL that records every HTTP request sent to it, for webhook.read to fetch.

NetworkLater set2 units per callnot cachedMCP: webhook_createv1.0.0

When to use it

Use when another service has to call you back: to receive a webhook, wait for a callback from a job, or see exactly what a service sends. Give the returned url to that service, then collect what arrives with webhook.read. The inbox and everything in it are deleted when it expires.

Input

Field	Type	Description
`ttl_s`	`integer (≥ 60, ≤ 86400)`	Seconds until the inbox and its contents are deleted. Default one hour, at most 24 hours. Default: 3600.
`response_status`	`integer (≥ 200, ≤ 599)`	HTTP status the inbox URL answers with. 3xx is not accepted. Default: 200.
`response_body`	`string (≤ 2000 chars)`	Body the inbox URL answers with. Default: "".
`response_content_type`	`one of text/plain, application/json`	Default: "text/plain".

Output

Returns data with: id, url, token, expires_at, max_requests, max_body_bytes.

Request

curl -X POST https://agentops.tools/v1/webhook.create \
  -H 'content-type: application/json' \
  -d '{}'

Over MCP the tool is named webhook_create. Over A2A its skill id is webhook.create. Same input, same envelope.

Try it

Input (JSON)

Counts against your rate limit.

Sources

agentops.tools webhook inbox

Notes

An inbox keeps at most 100 requests, each with a body of at most 256 KB.
Anyone who has the url can send to it; only the token can read. Keep the token private.
The url accepts any method and any path below it, for example {url}/events.