Platforms
Platforms
Pick a platform to see its auth, its endpoints, what it maps and the traps.
Every platform answers the same ten resources with the same shapes, or with a 501 when it has nothing to give. What changes underneath is the API, the header the token travels in, how a page says there is a next one, and which operations exist at all. The pages are short on purpose. The part worth reading is the gotcha list on each one.
| About | |||
|---|---|---|---|
| GitHub | github | REST v3 for everything except review threads, which need GraphQL for their resolved flag. The reference the others are measured against. | Authorization: token |
| GitLab | gitlab | API v4 with Private-Token auth, project ids resolved and cached for you, iid as the number, and a group fallback for owners that aren't users. | Private-Token |
| Gitea | gitea | API v1 with limit instead of per_page, empty strings and nulls where fields are missing, and Codeberg or any Forgejo through baseURL. | Authorization: token |
| GitBucket | github + baseURL | The GitHub provider pointed at a GitBucket /api/v3. What GitBucket doesn't serve fails with a sentence, not a 404. | Authorization: token |
| Artifacts | artifacts | Git storage behind the Cloudflare API. Repos, files and history read like on any forge, and the forge part is a 501. | Authorization: Bearer |