The mission’s accepted strategy as a file
const url = 'https://beta-api.plune.ai/v1/missions/example/export/strategy?format=md';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url 'https://beta-api.plune.ai/v1/missions/example/export/strategy?format=md' \ --header 'Authorization: Bearer <token>'The latest accepted strategy (#2194) as Markdown (format=md, the default) or PDF (format=pdf), named <mission>-strategy-v<version>.md or .pdf: the sections of the plan, each item with what it rests on - a source of the mission by its title or address, never an id that only Plune can open. A snapshot to keep in a repository or a wiki; the main copy stays in Plune. On every tier, Free too, and to anyone in the project, a reader too. 404 until a strategy is accepted. Twelve a minute. Sent with Content-Disposition: attachment, Cache-Control: no-store and X-Content-Type-Options: nosniff; nothing is written to the project’s feed.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The mission’s id
Query Parameters
Section titled “Query Parameters ”Markdown or PDF
Responses
Section titled “ Responses ”The file
Example
# Test strategy: Shop checkout
Version 1, accepted 2026-11-04.
Exported from Plune. A snapshot: the main copy stays in Plune, where it is changed - a new export replaces this file.
## Objectives
- A customer can pay for a cart and gets a receipt (doc-section: docs/checkout.md#goal)
## Scope
### In scope
- The cart, payment by card and by voucher, the receipt email (doc-section: docs/checkout.md#scope)
### Not tested
- The warehouse back office: another team owns it and tests it (doc-section: docs/checkout.md#out-of-scope)
## Approach
- The API first, from the OpenAPI file; then the three UI flows of the checkout (endpoint: POST /cart)
## Methodology profile
- Test levels: system, acceptance- Quality characteristics (ISO/IEC 25010:2023): functional-suitability, security- Techniques: equivalence-partitioning, boundary-value, state-transition- Split: API 60%, UI 30%, manual 10%
- A URL and an OpenAPI file, no repository: no component level (url: https://shop.example.com/openapi.json)
## Risks
- **high** (level 6: likelihood medium, impact high) A card is charged twice when the payment page is reloaded (endpoint: POST /payments)- **low** (level 2: likelihood low, impact medium) A voucher past its date is taken (assumption, to confirm)
## Entry criteria
- Staging is up and a test account exists (assumption, to confirm)
## Exit criteria
- Whether a refunded voucher counts as used (waits on question 6f1c2b3a-0000-4000-8000-000000002190 (open))Headers
Section titled “Headers ”Example
attachment; filename="Shop-checkout-strategy-v1.md"; filename*=UTF-8''Shop-checkout-strategy-v1.mdA format that is not md or pdf
object
Example generated
{ "error": "example"}No / invalid token or session
No such mission in your project, or no strategy accepted for it yet
object
Example generated
{ "error": "example"}Rate-limited: the per-route throttle, or the per-minute request limit of the plan an API token counts by (#1442; the body names the plan, #2092). Retry-After carries the seconds until the window rolls over.
object
Example generated
{ "error": "example"}Headers
Section titled “Headers ”Seconds until the window rolls over