--- title: "POST /plans/{id}/approve: Approve and get the pay link | distribution.tech" description: "Sign a plan at the terms_fingerprint from plan_quote, under the brand terms a person at the brand accepted for this key, and get the Stripe Checkout link." canonical: https://distribution.tech/docs/api/post-plans-id-approve generator: md-live-route generated: 2026-10-21T10:13:15.124Z --- # POST /plans/{id}/approve: Approve and get the pay link | distribution.tech - [Getting started](https://distribution.tech/docs) - [API reference](https://distribution.tech/docs/api) - [MCP and agents](https://distribution.tech/docs/agents) - [Changelog](https://distribution.tech/docs/changelog) Search the docs Docs - Using the API › - [API reference](https://distribution.tech/docs/api) - [Authentication](https://distribution.tech/docs/api/authentication) - [Scopes](https://distribution.tech/docs/api/scopes) - [Errors](https://distribution.tech/docs/api/errors) - Inventory and audience › - [GET /audience](https://distribution.tech/docs/api/get-audience) - [GET /inventory](https://distribution.tech/docs/api/get-inventory) - Creators › - [GET /creators](https://distribution.tech/docs/api/get-creators) - [GET /creators/{id}](https://distribution.tech/docs/api/get-creators-id) - [POST /creators/{id}/price-request](https://distribution.tech/docs/api/post-creators-id-price-request) - Campaigns › - [GET /campaigns](https://distribution.tech/docs/api/get-campaigns) - [POST /campaigns](https://distribution.tech/docs/api/post-campaigns) - [GET /campaigns/{id}](https://distribution.tech/docs/api/get-campaigns-id) - [PATCH /campaigns/{id}](https://distribution.tech/docs/api/patch-campaigns-id) - [DELETE /campaigns/{id}](https://distribution.tech/docs/api/delete-campaigns-id) - [POST /campaigns/{id}/archive](https://distribution.tech/docs/api/post-campaigns-id-archive) - [POST /campaigns/{id}/creator-guidelines](https://distribution.tech/docs/api/post-campaigns-id-creator-guidelines) - Plans › - [POST /plans/{id}/approve](https://distribution.tech/docs/api/post-plans-id-approve) - [POST /plans/{id}/dates](https://distribution.tech/docs/api/post-plans-id-dates) - [POST /plans/{id}/lines](https://distribution.tech/docs/api/post-plans-id-lines) - [GET /plans/{id}/quote](https://distribution.tech/docs/api/get-plans-id-quote) - [DELETE /plans/{id}/lines/{line\_id}](https://distribution.tech/docs/api/delete-plans-id-lines-line-id) - [POST /plans/{id}/lines/{line\_id}/swap](https://distribution.tech/docs/api/post-plans-id-lines-line-id-swap) - Proof and results › - [GET /evidence](https://distribution.tech/docs/api/get-evidence) - [GET /results](https://distribution.tech/docs/api/get-results) - Company context › - [GET /brain](https://distribution.tech/docs/api/get-brain) - Feedback › - [GET /feedback](https://distribution.tech/docs/api/get-feedback) - [POST /feedback](https://distribution.tech/docs/api/post-feedback) 1. [distribution](https://distribution.tech/) 2. / [Docs](https://distribution.tech/docs) 3. / [API reference](https://distribution.tech/docs#api) 4. / Plans API reference, Plans # Approve and get the pay link POST /plans/{id}/approve Sign a plan at the terms\_fingerprint from plan\_quote, under the brand terms a person at the brand accepted for this key, and get the Stripe Checkout link. Copy page as markdown [View .md](https://distribution.tech/docs/api/post-plans-id-approve.md) ## Overview Sign a plan at the terms\_fingerprint from plan\_quote, under the brand terms a person at the brand accepted for this key, and get the Stripe Checkout link the brand or its finance person pays (card or Link up to $10,000, US bank account at any size). Only inside the key's mandate: a refusal names the limit (no mandate, expired, signing not allowed, terms not accepted, channel, plan maximum, monthly cap) and how much over, so you can take it to a person. A plan that changed since the quote is refused with terms\_changed: quote again. A plan over the campaign's budget is refused with over\_budget and its over\_by\_cents, always: nobody can approve an overage, the brand included, so remove a creator or ask a person at the brand to raise the budget, then quote again. Signing a signed plan returns its order and resumes payment; it never signs twice. Needs an idempotency\_key. Scope: plans:approve. MCP tool: approve\_plan. Endpoint `POST https://app.distribution.tech/api/v1/plans/{id}/approve` Scope `plans:approve` Changes data Yes, send an Idempotency-Key header MCP tool [approve\_plan](https://distribution.tech/docs/mcp/tools/approve-plan) ## Parameters | Name | In | Type | Required | Description | | --- | --- | --- | --- | --- | | `id` | path | string (uuid) | Yes | | | `Idempotency-Key` | header | string | Yes | 8 to 128 letters, digits or . \_ : -. Retry with the same key and the same request to get the same answer; it never runs twice. | ## Request body | Name | Type | Required | Description | | --- | --- | --- | --- | | `terms_fingerprint` | string | Yes | The terms\_fingerprint from /plans/{id}/quote. | | `confirm_over_budget_cents` | integer | No | Retired and ignored if sent. No plan over its campaign's budget is approved, so nothing confirms an overage: remove a creator or raise the budget. | JSON body, every field ``` { "terms_fingerprint": "", "confirm_over_budget_cents": 0 } ``` ## Request with curl Set `DISTRIBUTION_API_KEY` to a key from Developers with the `plans:approve` scope, and each path variable to an id from an earlier answer. The body carries the required fields. curl ``` curl -X POST "https://app.distribution.tech/api/v1/plans/$PLAN_ID/approve" \ -H "Authorization: Bearer $DISTRIBUTION_API_KEY" \ -H "Idempotency-Key: $(uuidgen)" \ -H "Content-Type: application/json" \ -d '{ "terms_fingerprint": "" }' ``` ## Response `200` OK. The body has these fields: | Name | Type | Required | Description | | --- | --- | --- | --- | | `plan_id` | string (uuid) | No | | | `status` | "approved" | No | | | `approved_at` | string (date-time) | No | | | `already_signed` | boolean | No | | | `order` | object or null | No | | | `payment` | object | No | | 200 response body, every field with its type ``` { "plan_id": "", "status": "approved", "approved_at": "", "already_signed": false, "order": {}, "payment": { "next": "checkout", "pay_url": "", "options": [ { "rail": "checkout", "label": "", "clears": "" } ] } } ``` ## Errors | Status | When | | --- | --- | | `400` | A parameter is not valid: details.problems names each field and what it accepts. | | `401` | No API key, an unknown one, or a revoked one. | | `403` | The key lacks the scope, or the mandate refuses (mandate\_refused, with the limit and how much over). | | `404` | No plan, line or creator of yours has that id. | | `409` | conflict (with a reason), idempotency\_conflict, or in\_progress (Retry-After). | | `422` | unprocessable: the body is readable but a value cannot be used (a blank or too long name, a campaign that cannot be planned yet); details.problems names each field when there are several. | | `429` | Too many requests for this key in the current minute (60); Retry-After and RateLimit-Reset say when to try again. On POST /campaigns and on POST /plans/current/lines when it starts a plan: the brand's 3 new campaigns in 24 hours are used (details.reason daily\_campaign\_limit); details.resets\_at and Retry-After say when the limit reopens, a rolling 24 hours from the first of them, not a calendar day; archiving or deleting a campaign does not give its slot back. On GET /creators and GET /creators/{id}: a creator read limit is used (details.reason per\_minute, daily\_lists, daily\_reveals, daily\_seen or locked). daily\_seen is your workspace's one pool of 300 creator views a day (300 different creators shown or opened since midnight UTC), shared by the app and every API key of the brand: details.scope workspace and details.limit 300; a creator already seen today, in the app or through any key, still opens and costs nothing. The other reasons are this key's own limit (details.scope key) or the brand's ceiling over all its keys (details.scope api). | | `500` | internal: the request failed on our side. Retry it with the same Idempotency-Key. | | `503` | unavailable: writes are not available right now (for an approval: payments are not open yet). | ## Related endpoints - [`POST /plans/{id}/dates`](https://distribution.tech/docs/api/post-plans-id-dates): Move a plan's dates - [`POST /plans/{id}/lines`](https://distribution.tech/docs/api/post-plans-id-lines): Add a creator - [`GET /plans/{id}/quote`](https://distribution.tech/docs/api/get-plans-id-quote): A plan as you sign it - [`DELETE /plans/{id}/lines/{line_id}`](https://distribution.tech/docs/api/delete-plans-id-lines-line-id): Remove a creator - [`POST /plans/{id}/lines/{line_id}/swap`](https://distribution.tech/docs/api/post-plans-id-lines-line-id-swap): Swap a creator ## Get access Keys are created in Developers once your brand is approved. [Connect an agent](https://distribution.tech/distribution#access) to ask for access, then read [the agent guide](https://distribution.tech/docs/agents) for the full flow. On this page - [Overview](#overview) - [Parameters](#parameters) - [Request body](#request-body) - [Request with curl](#curl) - [Response](#response) - [Errors](#errors) - [Related endpoints](#related) - [Get access](#access) [![distribution.tech](https://distribution.tech/brand/wordmark-light.svg)![distribution.tech](https://distribution.tech/brand/wordmark.svg)](https://distribution.tech/) Your agent buys your distribution. Distribution we run for - ClickUp - Gushwork - Tab Platform - [How it works](https://distribution.tech/how-it-works) - [Network](https://distribution.tech/network) - [Workspace](https://app.distribution.tech/login) - [For your agents](https://distribution.tech/distribution) Solutions - [Product launch](https://distribution.tech/solutions/product-launch) - [Funding announcement](https://distribution.tech/solutions/funding-announcement) - [Feature release](https://distribution.tech/solutions/feature-release) - [For brands](https://distribution.tech/for-brands) - [For creators](https://distribution.tech/for-creators) Resources - [Blog](https://distribution.tech/blog) - [Launch playbook](https://distribution.tech/playbook) - [X creator rates](https://distribution.tech/rates/x-creators) Company - [Customers](https://distribution.tech/customers) - [Pricing](https://distribution.tech/pricing) - [Changelog](https://distribution.tech/changelog) - [Build a distribution plan](https://app.distribution.tech/login) - [Join the creator network](https://distribution.tech/for-creators#apply) - [Log in](https://app.distribution.tech/login) Legal - [Privacy](https://distribution.tech/privacy) - [Terms](https://distribution.tech/terms) © 2026 distribution.tech [Contact: team@distribution.tech](mailto:team@distribution.tech)Cookie settings Light Dark System