Skip to content
Plune Plune Plune Docs

Link a case to a requirement

PUT
/v1/requirements/{id}/cases/{caseId}
 
curl --request PUT \
  --url https://beta-api.plune.ai/v1/requirements/example/cases/example \
  --header 'Authorization: Bearer <token>'

An owner’s or a member’s. Many-to-many: a requirement has many cases and a case many requirements; the link is seen from both sides (GET /v1/requirements/{id}, GET /v1/test-cases/{id}/requirements). Linking twice is one link (200 the second time, 201 the first). Both must be in the same project; a case in the Bin is not a case here. An archived requirement takes no new case (409).

Authorizations

Section titled “Authorizations ”

Parameters

Section titled “ Parameters ”

Path Parameters

Section titled “Path Parameters ”
id
required
string
caseId
required
string

Responses

Section titled “ Responses ”

200

Section titled “200 ”

Already linked; the requirement with its cases

201

Section titled “201 ”

Linked; the requirement with its cases

401

Section titled “401 ”

No / invalid token or session

403

Section titled “403 ”

You are in the project as a reader

404

Section titled “404 ”

No such requirement or case in your projects

Media type application/json
object
error
required
string
Example generated
{
  "error": "example"
}

409

Section titled “409 ”

The requirement is archived

Media type application/json
object
error
required
string
Example generated
{
  "error": "example"
}

429

Section titled “429 ”

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.

Media type application/json
object
error
required
string
Example generated
{
  "error": "example"
}

Headers

Section titled “Headers ”
Retry-After
integer

Seconds until the window rolls over