Continuous Integration — entry 003 of 5
Buddy
Buddy's REST API manages its visual CI/CD pipelines end to end — projects, actions, environments, runs, sandboxes, and Git operations — and is described as covering the same permission model as the web app itself. Its docs state plainly that authentication is performed with OAuth2, sending requests with a Bearer access_token, which this run reconfirmed live: an unauthenticated call to api.buddy.works/user returned a 401 "Wrong authentication data" response while still carrying access-control-allow-origin: * on both the request and its OPTIONS preflight, resolving the previously unknown CORS support to open. Buddy's own pricing page lists a free plan (limited pipeline minutes and one seat) alongside paid Pro and Hyper tiers, making it freemium rather than a flat fee.
GreatAPIs Score
Auth quickstart
- Register an app / run the OAuth flow to obtain a bearer token.
- Send it as an Authorization header
Authorization: Bearer <token>
Your key is stored only in this browser (localStorage) and sent directly to the API — never to greatapis.