Skip to content
GigAI

Process one job now

POST
/api/pipeline/process
curl --request POST \
  --url http://127.0.0.1:8765/api/pipeline/process \
  --header 'Content-Type: application/json' \
  --data '{ "job_identity": "https://boards.greenhouse.io/acme/jobs/101" }'

Process now: queue one assessed job for the pipeline. System data only: ids, codes, counts, numbers and timestamps. A job is named by its job_identity (the posting’s public link). No posting, resume, answer or story text, no title, no company. 202: the job’s steps (tailor, assess again, Scout ATS score, Scout label) are queued and this server’s runner runs them; the call never waits for a model. result is enqueued, noop_unchanged (done with these inputs), noop_already_queued or noop_failed (it failed with these inputs: retry it, or pass force). An explicit choice: the per-trigger cap does not apply and a job waiting for an approval is taken out of it; the daily cap of model calls still does. Read the outcome with GET /api/pipeline. runner false: this server runs no pipeline thread (run gigai scout pipeline run --once). 404 assessment_missing: assess the job first.

Request Bodyrequired

Section titled “Request Bodyrequired”
Media typeapplication/json
object
force

True: tailor again even when nothing the tailoring reads has changed.

boolean
job_identity
required

The posting’s link (a job that already has an assessment).

string
profile_id

The role that asks (default: the selected role). Recorded on a job’s first steps; it selects nothing.

string
Example
{
  "job_identity": "https://boards.greenhouse.io/acme/jobs/101"
}

Responses

Section titled “Responses”

200

Section titled “200”

Success.

Media typeapplication/json
object
schema_version
required
Allowed value: scout-pipeline-process:1
key
additional properties
any
Example
{
  "input_digest": "sha256:abababababababababababababababababababababababababababababababab",
  "job_identity": "https://boards.greenhouse.io/acme/jobs/101",
  "profile_id": "prof_1",
  "result": "enqueued",
  "runner": true,
  "schema_version": "scout-pipeline-process:1"
}

403

Section titled “403”

Forbidden / forbidden_origin: loopback peer and Host 127.0.0.1:<port> or localhost:<port> only (Origin too on writes).

Media typeapplication/json
object
error
required
object
allowed_keys
Array<string>
code
required
string
message
required
string
key
additional properties
any
Examplegenerated
{
  "error": {
    "allowed_keys": [
      "example"
    ],
    "code": "example",
    "message": "example"
  }
}

404

Section titled “404”

Target_unavailable, assessment_missing, profile_not_found, profile_unavailable

Media typeapplication/json
object
error
required
object
allowed_keys
Array<string>
code
required
string
message
required
string
key
additional properties
any
Example
{
  "error": {
    "code": "target_unavailable",
    "message": "..."
  }
}

415

Section titled “415”

Unsupported_media_type: writes need Content-Type: application/json.

Media typeapplication/json
object
error
required
object
allowed_keys
Array<string>
code
required
string
message
required
string
key
additional properties
any
Examplegenerated
{
  "error": {
    "allowed_keys": [
      "example"
    ],
    "code": "example",
    "message": "example"
  }
}

422

Section titled “422”

Invalid_value, wrong_type, unknown_key, posting_text_unavailable

Media typeapplication/json
object
error
required
object
allowed_keys
Array<string>
code
required
string
message
required
string
key
additional properties
any
Example
{
  "error": {
    "code": "invalid_value",
    "message": "..."
  }
}