Bitrise API vs Travis CI API

Two free Continuous Integration APIs compared on access, reliability and developer ratings, using data from our daily health checks.

The verdict

Choose Bitrise API if you want faster responses.
Choose Travis CI API if its data fits your use case better; on access and reliability it's level with Bitrise API.

	Bitrise API	Travis CI API
What it does	Build tool and processes integrations to create efficient development pipelines.	Sync your GitHub projects with Travis CI to test your code in minutes.
Provider	Bitrise Swagger UI	Travis CI
API key	Required	Required
HTTPS	Yes	Yes
CORS (browser calls)	Unknown	Unknown
Status today	Online · 299 ms	Online · 999 ms
Uptime (30 days)	Up	Up
Developer rating	Not rated yet	Not rated yet
Price	Free / free tier	Free / free tier

Build tool and processes integrations to create efficient development pipelines.

Strengths

Sync your GitHub projects with Travis CI to test your code in minutes.

Strengths

Prototyping or a tutorial? Pick the one that needs no API key (neither does, so compare their free tiers).
Calling from a web page? You need CORS. Otherwise route requests through your own server or a serverless function.
Going to production? Favour HTTPS, a strong uptime record and a provider with clear rate limits and terms. Check each API's docs before you commit.
Still unsure? Both are free to try: send one request to each and compare the data you get back.

Both require authentication (apiKey and apiKey).