Approve a portfolio job only after reviewing its stored immutable plan. The approval is tied to that plan's digest, so a changed selection requires a new review. When independent approval is required, the requesting actor cannot approve the same work.
| Method | Resource | Scope | Idempotency-Key |
|---|---|---|---|
GET |
/v2/portfolio/jobs/{jobId} |
domains:read |
Not required by this route |
POST |
/v2/portfolio/jobs/{jobId}/approve |
domains:operate |
Required |
POST |
/v2/portfolio/jobs/{jobId}/start |
domains:operate |
Required |
IN THIS ARTICLE
01 Review the stored job
- Read the job ID returned by creation. Compare its items, skipped selection, operation payloads and provider routing with the intended change.
- Record the stored
plan_digest, current status, requesting actor and approval requirement. - For charged operations, check current quote validity, available funds and the intended billing responsibility. A routing plan is not a guarantee that every future provider call will succeed.
- Ensure a separate authorised reviewer understands the operational effect of the whole selection. For example, disabling automatic renewal affects a future renewal preference; changing nameservers can interrupt current services.
- If the job is awaiting approval, the independent actor submits
plan_digestto itsapproveendpoint.
02 Start and monitor execution
After approval, or when independent approval is not required, confirm the job is in the state accepted by start. POST with its own idempotency key only when the work should begin. A stored scheduling timestamp is not a reason to send an early start and assume the server will wait.
Save the worker reference and monitor both job and item states. Work proceeds in bounded batches, so one provider or domain may fail after another succeeds. Do not report a whole-portfolio success until all intended items and any dispatched child work have been reconciled.
Common questions
Why is my approval rejected?
Check the job state, digest and requesting actor. A stale or mismatched digest does not approve the stored plan, and the same actor cannot satisfy its independent approval requirement.
Can I create another key to approve my own request?
Use an independent authorised reviewer. The approval mechanism exists to obtain a second review, not merely a different credential label.
Does every item require separate human approval?
The portfolio plan records its approval requirement, and individual downstream services may enforce additional controls. Review the applicable response instead of assuming one approval removes every service-level restriction.
What if the selection needs to change?
Preserve the current job as evidence and create a new reviewed plan. Do not attempt to alter the digest or substitute different operations during the approval request.