Cloud infrastructure/devops
gitea.io
Gitea API. sandbox and mock API
This documentation describes the Gitea API. Writes persist, data moves on a schedule and every change can fire a signed webhook.
- Operations
- 325
- Collections
- -
- Event types
- -
example request
curl https://your-gitea.slurry.io/api/v1/admin/cron \
-H "Authorization: Bearer slurry_sim_..."Your simulation gets its own hostname, key and IP allow-list. Built from API version 1.20.0+dev-93-g6886706f5.
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 325.
- GET/activitypub/user/{username}
- POST/activitypub/user/{username}/inbox
- GET/admin/cron
- POST/admin/cron/{task}
- GET/admin/hooks
- POST/admin/hooks
- GET/admin/hooks/{id}
- PATCH/admin/hooks/{id}
- GET/admin/orgs
- GET/admin/unadopted
- POST/admin/unadopted/{owner}/{repo}
- DELETE/admin/unadopted/{owner}/{repo}