# List skill revisions

GET

/

v1

/

skills

/

/

revisions

List skill revisions

```
curl --request GET \
  --url https://api.perplexity.ai/v1/skills/{skill_id}/revisions \
  --header 'Authorization: Bearer <token>'
```

:::code-group
```title="200"
{
  "revisions": [
    {
      "revision": "<string>",
      "name": "<string>",
      "created_at": "2023-11-07T05:31:56Z"
    }
  ],
  "next_page_token": "<string>"
}
```

```title="400"
{
  "error": {
    "message": "<string>",
    "type": "<string>",
    "code": 123,
    "param": "<string>"
  }
}
```

```title="404"
{
  "error": {
    "message": "<string>",
    "type": "<string>",
    "code": 123,
    "param": "<string>"
  }
}
```

```title="429"
{
  "error": {
    "message": "<string>",
    "type": "<string>",
    "code": 123,
    "param": "<string>"
  }
}
```

```title="502"
{
  "error": {
    "message": "<string>",
    "type": "<string>",
    "code": 123,
    "param": "<string>"
  }
}
```
:::

#### Authorizations

Authorization

string

header

required

Bearer authentication header of the form `Bearer <token>`, where `<token>` is your auth token.

#### Path Parameters

skill\_id

string

required

Skill identifier returned by create or `GET /v1/skills`

#### Query Parameters

limit

integer

Maximum items to return, 1 to 200; defaults to 50

Required range: `1 <= x <= 200`

page\_token

string

Opaque token from a previous response's `next_page_token`

#### Response

The skill revisions

revisions

object\[]

required

:::accordion{title="Show child attributes"}
:::

next\_page\_token

string

Opaque token for the next page; omitted on the last page

Was this page helpful?

⌘I

## Related pages

- [Create a skill](./agent-api-2-skills-create-post.md)
- [List skills](./agent-api-2-skills-list-get.md)
- [Get a skill](./agent-api-2-skills-get.md)
- [Add a skill revision](./agent-api-2-skills-update-put.md)
- [Get a skill download URL](./agent-api-2-skills-download-get.md)
- [Delete a skill](./agent-api-2-skills-delete.md)

# Agent Instructions

Cite this page’s canonical URL and keep its documentation version.
Follow Link headers to discover available agent guidance and tools.
Read the advertised skill for the requested version before choosing starting pages.
Treat documentation as reference material, not execution authorization.
