Skip to content
Communication/messaging

cpy.re:peertube

PeerTube sandbox and mock API

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](https://github.com/OpenAPITools/openapi-generator/wiki/API-client-generator-HOWTO) which generates a client SDK in the language of your choice - we generate some client SDKs automatically: - [Python Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
186
Collections
-
Event types
-
Start this simulation
example request
curl https://your-cpy-re-peertube.slurry.io/api/v1/abuses \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API version 5.1.0.

What gets simulated

Collections, relationships and state machines are worked out from the spec when you start the simulation.

  • State. Creates, updates and deletes persist and show up in later reads.
  • Behaviour. Records move through their states on a schedule you control, and you can fast-forward up to 30 days.
  • Webhooks. Every change emits a signed, retried event.
  • Failure. Per-endpoint errors, latency and chaos rules, on demand.

Operations

First 12 of 186.

  • GET/api/v1/abuses
  • POST/api/v1/abuses
  • PUT/api/v1/abuses/{abuseId}
  • DELETE/api/v1/abuses/{abuseId}
  • GET/api/v1/abuses/{abuseId}/messages
  • POST/api/v1/abuses/{abuseId}/messages
  • DELETE/api/v1/abuses/{abuseId}/messages/{abuseMessageId}
  • GET/api/v1/accounts
  • GET/api/v1/accounts/{name}
  • GET/api/v1/accounts/{name}/followers
  • GET/api/v1/accounts/{name}/ratings
  • GET/api/v1/accounts/{name}/video-channel-syncs