Webhooks

Webhooks notify your systems when supported runs reach a terminal state. Osmosis sends a JSON POST to the workspace URL you configure for training, evaluation, and benchmark run completion events.

Setup

Open Workspace Settings → Webhooks (owners and admins only):

Enter your Webhook URL. It must use HTTPS on port 443 and resolve to a public address. URLs that point at private or internal networks are rejected.
Turn on Deliver events and click Save.
Click Send test payload to confirm your receiver gets a webhook.test event.

Turn off Deliver events to pause deliveries without losing the URL. To remove the webhook, clear the Webhook URL and click Save.

Events

Event	Sent when
`training_run.completed`	A training run reaches a terminal status
`eval_run.completed`	An evaluation run reaches a terminal status
`benchmark_run.completed`	A benchmark run reaches a terminal status
`webhook.test`	You click Send test payload

Payload

Every request is a POST with Content-Type: application/json and this envelope:

{
  "event": "training_run.completed",
  "timestamp": "2026-07-15T22:14:05.123456+00:00",
  "data": {}
}

`training_run.completed` and `eval_run.completed`

The data object has the same shape for both events:

Field	Description
`id`	Run ID
`name`	Run name
`status`	Terminal run status, such as `finished`, `failed`, or `stopped`
`started_at`	Start time in ISO 8601 format, or `null` if the run never started
`completed_at`	Completion time in ISO 8601 format, or `null` when unavailable
`duration_seconds`	Total run duration in seconds, or `null` when no duration is available
`model_name`	Model name used by the run, or `null`
`dataset`	Dataset `{ "id", "name" }`, or `null`
`rollout`	Rollout `{ "id", "name" }`, or `null`
`platform_url`	Link to the run detail page
`latest_metrics`	Training: the latest logged value for each available metric. Evaluation: final aggregate results, including `reward_stats` when available

Training run example:

{
  "event": "training_run.completed",
  "timestamp": "2026-07-15T22:14:05.123456+00:00",
  "data": {
    "id": "a1b2c3d4-0000-0000-0000-000000000000",
    "name": "my-training-run",
    "status": "finished",
    "started_at": "2026-07-15T20:01:12+00:00",
    "completed_at": "2026-07-15T22:14:03+00:00",
    "duration_seconds": 7971,
    "model_name": "Qwen3-8B",
    "dataset": { "id": "d1e2f3a4-0000-0000-0000-000000000000", "name": "my-dataset" },
    "rollout": { "id": "r1s2t3u4-0000-0000-0000-000000000000", "name": "my-rollout" },
    "platform_url": "https://platform.osmosis.ai/my-workspace/training/a1b2c3d4-0000-0000-0000-000000000000",
    "latest_metrics": {
      "rollout/raw_reward": 0.82,
      "eval/validation/reward": 0.79,
      "train/entropy_loss": 1.24,
      "rollout/response_lengths": 512,
      "rollout/total_lengths": 1930,
      "rollout/truncated_ratio": 0.03
    }
  }
}

For evaluation runs, latest_metrics contains aggregate results instead:

"latest_metrics": {
  "total_runs": 200,
  "graded": 198,
  "passed": 154,
  "failed": 44,
  "skipped": 2,
  "pass_rate": 0.78,
  "pass_threshold": 0.5,
  "score": 0.71,
  "reward_stats": {
    "mean": 0.71,
    "median": 0.74,
    "std": 0.18,
    "min": 0.05,
    "max": 0.98,
    "pass_at_k": { "1": 0.78, "4": 0.91 }
  },
  "total_tokens": 1834520,
  "total_duration_ms": 5421000
}

`benchmark_run.completed`

Field	Description
`id`	Benchmark run ID
`name`	Run name
`status`	Terminal run status, such as `finished`, `failed`, or `stopped`
`benchmark_name`	Benchmark name
`started_at`	Start time in ISO 8601 format, or `null` if the run never started
`completed_at`	Completion time in ISO 8601 format, or `null` when unavailable
`duration_seconds`	Total run duration in seconds, or `null` when no duration is available
`platform_url`	Link to the benchmark run detail page
`agents`	One result summary per agent in the run

Each object in agents contains:

Field	Description
`id`	Benchmark run agent ID
`agent_index`	Agent’s zero-based position in the run configuration
`label`	Agent display label
`model`	Model identifier, or `null`
`tasks`	Number of tasks represented in the result summary
`attempts`	Number of attempts represented in the result summary
`passed`	Number of passing attempts
`pass_rate`	Passing attempts divided by attempts, or `null` when `attempts` is zero

{
  "event": "benchmark_run.completed",
  "timestamp": "2026-07-15T22:14:05.123456+00:00",
  "data": {
    "id": "b1c2d3e4-0000-0000-0000-000000000000",
    "name": "terminal-bench-smoke",
    "status": "finished",
    "benchmark_name": "Terminal-Bench 2.1",
    "started_at": "2026-07-15T21:40:00+00:00",
    "completed_at": "2026-07-15T22:14:03+00:00",
    "duration_seconds": 2043,
    "platform_url": "https://platform.osmosis.ai/my-workspace/benchmarks/runs/b1c2d3e4-0000-0000-0000-000000000000",
    "agents": [
      {
        "id": "c1d2e3f4-0000-0000-0000-000000000000",
        "agent_index": 0,
        "label": "codex",
        "model": "openai/gpt-5.2",
        "tasks": 10,
        "attempts": 10,
        "passed": 7,
        "pass_rate": 0.7
      }
    ]
  }
}

`webhook.test`

Field	Description
`workspace`	Workspace name
`message`	Confirmation message

Delivery

Each attempt times out after 5 seconds. Failed deliveries are retried up to 2 times with backoff.
Retries can produce duplicate deliveries. For run-completion events, make processing idempotent using the pair event + data.id.
Any 2xx response counts as delivered. Redirects are not followed.
Delivery is best effort. A webhook delivery failure does not affect the run, and Osmosis does not guarantee that every event will reach your receiver.

Security

Webhook requests are currently unsigned, so the payload alone does not prove that a request came from Osmosis. Use a dedicated, high-entropy HTTPS URL that is not published elsewhere, validate the JSON schema and expected event values before processing, and apply the idempotency rule above. Do not trigger privileged actions solely from unvalidated payload fields. If signed authentication is required, place the webhook behind a gateway you control and enforce your own receiver policy.

Get started

Runs

Resources

Workspace

Setup

Events

Payload

`training_run.completed` and `eval_run.completed`

`benchmark_run.completed`

`webhook.test`

Delivery

Security

​Setup

​Events

​Payload

​training_run.completed and eval_run.completed

​benchmark_run.completed

​webhook.test

​Delivery

​Security

Setup

Events

Payload

`training_run.completed` and `eval_run.completed`

`benchmark_run.completed`

`webhook.test`

Delivery

Security