The ContinuityApp API

The ContinuityApp API is organized around REST. Our API is designed to have predictable, resource-oriented URLs and to use HTTP response codes to indicate API errors. JSON will be returned in all responses from the API, including errors.

API can be accessed via HTTP basic authentication, and OAuth2. We strongly encourage you to use OAuth2 based authentication for your production applications, and use HTTP basic authentication for testing purposes.

Authentication

OAuth2

OAuth2 is the preferred way to interact with the ContinuityApp API.

Before starting using OAuth2 you will need to register your App, and obtain a Client ID and Secret Key: this can be easily done at the Create an application page.
You will use this data to obtain an access token, and you will use this access token to sign all your requests to the ContinuityApp API. Access token has no expiration date.

You will be required to provide a redirect URL: you can specify a valid URL like http://hostname/oauth_redirect or urn:ietf:wg:oauth:2.0:oob for command line applications. Providing urn:ietf:wg:oauth:2.0:oob as redirect URL users will be provided with an authorization code to be copy/pasted into your application.

OAuth for Open Source

We support a variant of OAuth Flows to allow Open Source developers to distribute software without worring about Secret Tokens.
If you want to write an Open Source software based on ContinuityApp APIs, or you just want to learn more, drop us a line to support@continuityapp.com.

HTTP Basic

HTTP basic authentication is the insecure way to interact with the ContinuityApp API.
We support this kind of authentication just for testing purposes and to speed up you development time, but we strongly encourage you to invest some efforts into adopting OAuth2 for your production environments.

API Key can be found at Your Apps page. API Key won't be provided in clear, and you will be required to re-create it every time you will loose it.

ContinuityApp IDs, JSON, Javascript and other languages

We use Twitter Snowflake to generate Unique IDs across all our services.
All the ContinuityApp IDs are rapresented as 64 bits integers, but since Javascript and other languages cannot support numbers with more than 53-bits, we are serving our IDs as Integers and Strings (identified by a _str suffix). If your language or parser can't correctly handle 64 bits Integers use the String-rapresented IDs.

ContinuityApp is a Hosted Continuous Integration and Continuous Deployment service.Speed up your development, leaving all the boring parts to us, and reclaim your joy to code while increasing your code quality.