PeerTube

api:cpy.re/peertube · v5.1.0 · source: apis.guru

The PeerTube API is built on HTTP(S) and is RESTful. You can use your favorite HTTP/REST library for your programming language to use PeerTube. The spec API is fully compatible with openapi-generator which generates a client SDK in the language of your choice - we generate some client SDKs automatically: - Python - Go - Kotlin See the REST API quick start for a few examples of using the PeerTube API. Authentication When you sign up for an account on a PeerTube instance, you are given the possibility to generate sessions on it, and authenticate there using an access token. Only one access token can currently be used at a time . Roles Accounts are given permissions based on their role. There are three roles on PeerTube: Administrator, Moderator, and User. See the roles guide for a detail of their permissions. Errors The API uses standard HTTP status codes to indicate the success or failure of the API call, completed by a RFC7807-compliant response body. HTTP 1.1 404 Not Found Content-Type: application/problem+json; charset=utf-8 { "detail": "Video not found", "docs": "https://docs.joinpeertube.org/api/rest-reference.html operation/getVideo", "status": 404, "title": "Not Found", "type": "about:blank" } We provide error type values for a growing number of cases, but it is still optional. Types are used to disambiguate errors that bear the same status code and are non-obvious: HTTP 1.1 403 Forbidden Content-Type: application/problem+json; charset=utf-8 { "detail": "Cannot get this

[![Connect-MCP](https://clawy.uk/mcp/badge/api%3Acpy.re/peertube.svg)](https://clawy.uk/mcp/s/api%3Acpy.re/peertube)