Skip to content

What the spec and the traffic disagree on

GET
/v1/api-endpoints/drift
curl --request GET \
--url https://beta-api.plune.ai/v1/api-endpoints/drift \
--header 'Authorization: Bearer <token>'

Two lists, of the project or of one API (apiId): the endpoints a spec describes that nobody has seen for 30 days or ever, and the ones traffic shows that no spec describes.

apiId
string

One API of the project (GET /v1/apis); another project’s, or one that is not there, is 404

Both sides

Media type application/json
object
staleDays
required
integer
Allowed values: 30
notSeen
required

In a spec, and last seen more than staleDays days ago

Array<object>
object
id
required
string
projectId
required
string
apiId
required

The API it belongs to (#2398); one endpoint a method and path shape within an API

string
method
required
string
Allowed values: GET PUT POST DELETE OPTIONS HEAD PATCH TRACE
path
required

A template, /orders/{orderId}; one endpoint a method and path shape, whatever its parameters are called

string
source
required

Where the catalog learnt of it; a description replaces traffic once one names it

string
Allowed values: spec code traffic manual
trust
required

derived - inferred from examples or traffic (x-cairn-derived); confirmed - a written spec or a person says so

string
Allowed values: confirmed derived
inSpec
required

A spec, the code or a person describes it - not only traffic. The drift tells its two sides apart by it

boolean
summary
required
string
nullable
auth
required

The auth scheme names it asks for; [] public, null not known

Array<string>
nullable <= 10 items
lastSeenAt
required

When traffic last showed it

string format: date-time
nullable
lastSeenEnvironment
required

Where traffic last showed it

string
nullable
createdBy
required
string
createdAt
required
string format: date-time
updatedAt
required
string format: date-time
coverage
required

How many live cases test it; GET /v1/api-endpoints/{id} names them

integer
health
required

How its live cases stand by their newest results, in a requirement’s words: failing - one failed or broke; passing - all passed; partial - some passed; notRun - none passed; noCases - none

string
Allowed values: failing passing partial notRun noCases
neverSeen
required

In a spec, and never seen: fresh from an import or written by hand - not drift until traffic is recorded (#2398)

Array<object>
object
id
required
string
projectId
required
string
apiId
required

The API it belongs to (#2398); one endpoint a method and path shape within an API

string
method
required
string
Allowed values: GET PUT POST DELETE OPTIONS HEAD PATCH TRACE
path
required

A template, /orders/{orderId}; one endpoint a method and path shape, whatever its parameters are called

string
source
required

Where the catalog learnt of it; a description replaces traffic once one names it

string
Allowed values: spec code traffic manual
trust
required

derived - inferred from examples or traffic (x-cairn-derived); confirmed - a written spec or a person says so

string
Allowed values: confirmed derived
inSpec
required

A spec, the code or a person describes it - not only traffic. The drift tells its two sides apart by it

boolean
summary
required
string
nullable
auth
required

The auth scheme names it asks for; [] public, null not known

Array<string>
nullable <= 10 items
lastSeenAt
required

When traffic last showed it

string format: date-time
nullable
lastSeenEnvironment
required

Where traffic last showed it

string
nullable
createdBy
required
string
createdAt
required
string format: date-time
updatedAt
required
string format: date-time
coverage
required

How many live cases test it; GET /v1/api-endpoints/{id} names them

integer
health
required

How its live cases stand by their newest results, in a requirement’s words: failing - one failed or broke; passing - all passed; partial - some passed; notRun - none passed; noCases - none

string
Allowed values: failing passing partial notRun noCases
notInSpec
required

Seen in traffic, and in no spec

Array<object>
object
id
required
string
projectId
required
string
apiId
required

The API it belongs to (#2398); one endpoint a method and path shape within an API

string
method
required
string
Allowed values: GET PUT POST DELETE OPTIONS HEAD PATCH TRACE
path
required

A template, /orders/{orderId}; one endpoint a method and path shape, whatever its parameters are called

string
source
required

Where the catalog learnt of it; a description replaces traffic once one names it

string
Allowed values: spec code traffic manual
trust
required

derived - inferred from examples or traffic (x-cairn-derived); confirmed - a written spec or a person says so

string
Allowed values: confirmed derived
inSpec
required

A spec, the code or a person describes it - not only traffic. The drift tells its two sides apart by it

boolean
summary
required
string
nullable
auth
required

The auth scheme names it asks for; [] public, null not known

Array<string>
nullable <= 10 items
lastSeenAt
required

When traffic last showed it

string format: date-time
nullable
lastSeenEnvironment
required

Where traffic last showed it

string
nullable
createdBy
required
string
createdAt
required
string format: date-time
updatedAt
required
string format: date-time
coverage
required

How many live cases test it; GET /v1/api-endpoints/{id} names them

integer
health
required

How its live cases stand by their newest results, in a requirement’s words: failing - one failed or broke; passing - all passed; partial - some passed; notRun - none passed; noCases - none

string
Allowed values: failing passing partial notRun noCases
Example
{
"staleDays": 30,
"notSeen": [],
"neverSeen": [
{
"id": "6f1c2b3a-0000-4000-8000-000000002192",
"projectId": "u-shop::default",
"apiId": "4b6f3c1e-8d2a-4f5b-9c7e-1a2b3c4d5e6f",
"method": "GET",
"path": "/orders/{orderId}",
"source": "spec",
"trust": "confirmed",
"inSpec": true,
"summary": "One order",
"auth": [
"bearerAuth"
],
"lastSeenAt": null,
"lastSeenEnvironment": null,
"createdBy": "6f1c2b3a-0000-4000-8000-0000000000a2",
"createdAt": "2026-11-04T09:00:00.000Z",
"updatedAt": "2026-11-04T09:05:00.000Z",
"coverage": 0,
"health": "noCases"
}
],
"notInSpec": [
{
"id": "6f1c2b3a-0000-4000-8000-000000002192-seen",
"projectId": "u-shop::default",
"apiId": "4b6f3c1e-8d2a-4f5b-9c7e-1a2b3c4d5e6f",
"method": "POST",
"path": "/orders",
"source": "traffic",
"trust": "derived",
"inSpec": false,
"summary": null,
"auth": null,
"lastSeenAt": "2026-11-03T10:00:00.000Z",
"lastSeenEnvironment": "beta",
"createdBy": "6f1c2b3a-0000-4000-8000-0000000000a2",
"createdAt": "2026-11-04T09:00:00.000Z",
"updatedAt": "2026-11-04T09:05:00.000Z",
"coverage": 0,
"health": "noCases"
}
]
}

No / invalid token or session

No such API in your project

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