---
title: Work With SeeLLM Jobs
description: Fetch a job, distinguish it from its implementation, and record an approved action through the Jobs API.
audience: [agent]
type: guide
version: v1
stability: stable
lastVerified: "2026-08-01"
prerequisites: [/docs/api/authentication/, /docs/api/jobs/]
related: [/docs/api/agent-hooks/, /docs/evidence-model/, /docs/agents/receive-agent-hooks/]
artifacts: []
---

## Prerequisites

- An API key with access to the organization’s jobs.
- A job ID from the dashboard, Jobs API, or an Agent Hook delivery.
- An implementation ID if you have one. It is optional for every implementation type.

## Recommended path

1. Get the job and read its evidence, recommended action, dashboard link, and available action URLs.
2. Treat the job as the work item and its patch, edge page, manual task, or hook delivery as an implementation detail.
3. Decide whether the job should move to `reviewed`, `approved`, `dismissed`, or another documented workflow status based on the evidence.
4. When an action is approved, post it with the correct `implementation_type`; include `implementation_id` when there is a concrete implementation to attach.

## Expected result

The job remains the user-facing workflow record while implementation status separately records whether execution shipped. Approving an action does not by itself prove that a patch or external workflow has shipped.

## Verify

Record an approved action with the documented endpoint and payload:

```bash
curl -X POST https://api.seellm.link/api/jobs/job_your_job_id/actions \
  -H "Authorization: Bearer sk_live_your_api_key_here" \
  -H "Content-Type: application/json" \
  -d '{
    "action_id": "approve_fix",
    "implementation_type": "patch",
    "implementation_id": "patch_123",
    "note": "Ship the answer-first patch."
  }'
```

Then fetch the same job with `GET /api/jobs/job_your_job_id` and confirm the returned job ID, status, and action state against the dashboard link in the job record.

## Troubleshooting

- If the implementation is not ready, omit `implementation_id` or use `manual`; do not invent an ID.
- If the action endpoint rejects the request, check the job ID, action ID, and bearer header against the [Jobs API](/docs/api/jobs/).
- If the evidence is insufficient, retain the job for review instead of claiming resolution.

## Related reference

- [Jobs API](/docs/api/jobs/)
- [Agent Hooks](/docs/api/agent-hooks/)
- [Evidence Model](/docs/evidence-model/)