greatapis

Continuous Integration — entry 005 of 5

Travis CI

Verified Jul 2026

Travis CI's REST API reads and manages builds, repositories, branches, and jobs, and its docs specify a token-based Authorization: token "<token>" header rather than an OAuth redirect flow, reconfirming the stored API Key auth model. A live GET against api.travis-ci.com returned a structured JSON response (not a raw connection error), and the same request sent with an Origin header carried access-control-allow-origin: * on both the GET and its OPTIONS preflight, resolving the previously unknown CORS support to open. Travis CI's own pricing page still lists an "Open Source Only" free tier alongside paid Linux/FreeBSD plans, so it remains freemium rather than fully paid.

Travis CI's v3 API reads and manages builds, repositories, branches, and jobs over a hypermedia JSON format, where every object carries @type and @href fields pointing back into the API. A live GET this run against a public GitHub repo's build list returned real build history with no token, no signup, and no Authorization header of any kind.

ci-cddevopsautomationbuild-automationopen-source
Visit docs.travis-ci.com ↗Pricing ↗Status ↗More Continuous Integration
AuthenticationAPI KeySign up with the provider to obtain credentials.
HTTPSSupportedTraffic is encrypted in transit.
CORSEnabledCallable directly from browser JavaScript.
PricingFreemiumA usable free tier exists, with paid plans for more volume.
FormatsJSONResponses can be requested as JSON.

GreatAPIs Score

Score61out of 100
Authentication15/25API key required
Pricing17/20Freemium tier available
Docs0/20No docs or spec available
Formats9/15Single response format
Freshness20/20Verified within 6 months

Embed this badge

Scored 61 on greatapis.com
<a href="https://greatapis.com/api/travis-ci/"><img src="https://greatapis.com/badge/travis-ci.svg" alt="Scored 61 on greatapis.com"></a>

Auth quickstart

  1. Public-repo reads need no key at all — a live GET this run against /repo/travis-ci%2Ftravis-web/builds?limit=1 with just the Travis-API-Version: 3 header returned real build data with access-control-allow-origin: *, no Authorization header present.
  2. Writes, and reads against a private repository, do need the stored API Key auth: get a token via travis login --pro (or the GitHub OAuth exchange at /auth/github) and send it as Authorization: token "<token>". A live GET this run against a repo slug that doesn't exist returned the exact same 404 repository not found (or insufficient access) message a real private repo would give an unauthenticated caller — the API deliberately doesn't distinguish the two, so a bare 404 here never confirms whether a repo exists.
Stored keyNo key stored

Your key is stored only in this browser (localStorage) and sent directly to the API — never to greatapis.

List the most recent build for a public repository

GEThttps://api.travis-ci.com/repo/travis-ci%2Ftravis-web/builds?limit=1

Travis-API-Version: 3

200 application/json

{"@type":"builds","@href":"/repo/travis-ci%2Ftravis-web/builds?limit=1","@pagination":{"limit":1,"offset":0,"count":24096,"is_first":true,"is_last":false,"next":{"@href":"/repo/travis-ci%2Ftravis-web/builds?limit=1&offset=1"}},"builds":[{"@type":"build","@href":"/build/278462667","id":278462667,"number":"28769","state":"errored","duration":626,"event_type":"cron","started_at":"2026-07-09T20:19:10Z","finished_at":"2026-07-09T20:24:06Z","private":false,"repository":{"@type":"repository","@href":"/repo/4375425","id":4375425,"name":"travis-web","slug":"travis-ci/travis-web"},"branch":{"name":"master"},"commit":{"sha":"6fc98e92be2fc377343f20122d9973e4e4d93295","message":"Merge pull request #3036 from travis-ci/Release_260204"},"jobs":[{"id":640002777},{"id":640002778},{"id":640002779}]}]}

Trimmed for length — the live response also carries @representation, @permissions, tag, stages, and created_by on the build, and first/last/prev cursor links alongside next in @pagination. count (24,096) is the repo's entire build history, not the size of this page; next.@href is a ready-to-fetch relative path, not a bare offset token.

Developer reference

Gotchas & limits

  • The repo slug must be URL-encoded (%2F for the slash) — a live GET this run with a literal slash (/repo/travis-ci/travis-web/builds) returned a 404 with {"@type":"error","error_type":"not_found","error_message":"resource not found (or insufficient access)"}, not the build list.
  • Travis-API-Version: 3 is required on every request — a live GET this run without it returned a bare 404 {"file":"not found"} from what looks like a legacy static-file router, with none of the v3 hypermedia envelope.
  • travis-ci.org is retired — a live GET this run against the old .org host returned 404 with an empty {} body and no @type envelope at all. api.travis-ci.com is the only live host now, for both open-source and private repos.
  • Every object is wrapped in a hypermedia envelope (@type, @href, and often @representation/@permissions) — plan to unwrap one extra layer versus a typical flat REST response.
  • A nonexistent repo and a private repo you can't access return the identical 404 {"error_type":"not_found","error_message":"repository not found (or insufficient access)"} — confirmed live this run against a made-up slug — so this endpoint alone can't tell you which case you're in.

Featured in

1 collection
CORS-ready browser APIs

People comparing Travis CI also look at…

All 5 →

Travis CI vs Azure DevOps Health

Despite its name, this is the Azure Resource Health control-plane API (part of Azure Resource Manager), which reports the real-time and historical availability status of individual Azure resources rather than anything DevOps-pipeline-specific. Every call goes through management.azure.com and is authenticated like any other ARM provider — a Microsoft Entra ID (Azure AD) OAuth2 bearer token in the Authorization header, not a plain API key. A live unauthenticated GET against its availabilityStatuses endpoint returned a structured JSON error with access-control-allow-origin: * rather than a raw connection failure, confirming the service and its CORS support are live.

Compare →

Travis CI vs Bitrise

Bitrise's REST API drives its mobile-focused CI/CD platform: triggering builds, reading build and workflow logs, and managing apps, webhooks, and cache across a project's pipelines. A live unauthenticated GET against api.bitrise.io/v0.1/me returned a clean 401 Unauthorized JSON body while still carrying access-control-allow-origin: * on both the request and an OPTIONS preflight, confirming the personal-access-token auth model and resolving its previously unknown CORS support to open. Its own pricing page offers a free Hobby tier for individual developers alongside paid team plans, so this is a freemium product, not a flat-fee one.

Compare →

Travis CI vs 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.

Compare →

Travis CI vs CircleCI

Travis CI supports CORS, while CircleCI doesn't — pick Travis CI for direct browser calls.

Compare →