Skip to main content
POST
Rerank milestones
Gives the milestones in orderedIds (1–200 unique ids) ranks 0, 1, 2, … in order and returns them in that order as { milestones }. Every id must name a milestone before any is ranked; otherwise 404 resource_missing and nothing is written. The credential needs both the projects:manage and objectives:read scopes, and objectives:read and projects:manage granted at the deployment root; otherwise 403 permission_denied names the first missing permission and nothing is written. The body is strict: unknown fields are 400 bad_request. Success is 200. With a key, a same-key retry within 24 hours returns the recorded result while the caller still holds both permissions at the deployment root; otherwise 409 idempotency_result_unavailable, and the write never runs twice. Reconcile an unknown outcome with List milestones.

Authorizations

Authorization
string
header
required

An External App: the JWT it obtains from POST /oauth/token with OAuth2 client_credentials. Pass as Authorization: Bearer <jwt>. An app's static companion key also authenticates as the app, but is deprecated and is not protected by Idempotency-Key.

Headers

Idempotency-Key
string

Optional logical intent key. A same-key retry within 24 hours returns the recorded result without writing again.

Required string length: 1 - 255

Body

application/json

Milestone IDs in their new order (1-200, unique); every ID must name a milestone before any is ranked.

orderedIds
string[]
required

Milestone IDs in their new order; each gets rank 0, 1, 2, … At most 200.

Required array length: 1 - 200 elements

The milestone ID, as the planning reads return it.

Required string length: 1 - 200

Response

Rerank milestones

data
object
required
meta
object
required