{% extends "_layout.html" %} {% set title = "Terms not accepted" %} {% set status = "403 Forbidden" %} {% set description = "There is an agreement you have not accepted, and it covers something this request needs." %} {% set also_on_a_job = true %} {% block main %}

There is a terms document you have not accepted, and it covers something this request needs.

This one you can fix yourself. blocked_by lists every document in the way, by its terms id.

What to do

  1. Name each document by its title in GET /v1/me’s terms, found by its id.
  2. Open each one’s page from POST /v1/auth/browser with {"terms_id": "<id>"}, read it, and sign it there.
  3. Then retry the original request unchanged.

You may also decline, and you may change your mind later. Declining is a recorded answer, not a failure state.

What each document costs

The documentWhat is blockedHow you will have noticed
a "service" document Everything — no create or submit of any kind. GET /v1/me reports can_submit: false, and blocked_type is this type’s URI.
an agreement on a resource Only what names or derives from the covered resource. can_submit stays true. This refusal arrives at create for a resource the job names, while staging against the job’s resource set, and on a fetch or a log stream of what derives from it.

For a fetch or a log stream, an acceptance of an earlier version of the document counts.

The body

{
  "type":       "https://sc.example.com/server-errors/terms-not-accepted",
  "title":      "Terms not accepted",
  "status":     403,
  "detail":     "This flow names a PDK covered by an agreement you have not accepted.",
  "instance":   "/v1/jobs",

  "blocked_by": ["gf22-nda", "gf22-export"],       // REQUIRED

  "trace_id":   "4bf92f3577b34da6a3ce929d0e0e4736"
}
Member
blocked_byREQUIRED Each document in the way, by its terms id, as a list. The same shape GET /v1/me’s authorized entries and the artifact listing carry. A document’s page comes from POST /v1/auth/browser.

A terms id is an opaque key — gf22-nda is a slug somebody typed. Do not parse it. Every document carries a human title in GET /v1/me.

Where it comes from

Every gate. At POST /v1/jobs and at submit, for a service document and for a resource the job names; while the job stages, against what the manifest’s read reports, where it ends the job rejected with this on its error; and at GET /v1/jobs/{id}/artifacts/{artifact_id} and …/logs, for what the artifact or log derives from.

{% include "_help.html" %}

What this is not

entitlement-denied means your account does not hold the resource at all. This means you hold it and have not signed for it.

artifact-not-approved (403) is a per-object decision on a specific output, not a document you can accept. It needs a human approval process, not a click.

{% endblock %}