OAuth Basics

Quipt’s web services rely on OAuth 1.0 revision A as the authorization framework.

Web based application:
oauth-web-based

Step 1 – Initiate

This begins the OAuth 1.0a authorization process for a Quipt user. The response includes the request ‘token’ and ‘secret’ to be used in later steps.

URLhttps://app.getquipt.com/oauth/initiate
 
Methodpost

Header:

Sample Response:

Step 2 – Authorize

Redirect the user to the Quipt authorization page. If the user accepts the authorization the user will be redirected to the defined ‘oauth_callback’.

URLhttps://app.getquipt.com/#/oauth/authorizing?oauth_token={token}
 
Methodget

Parameters:

Name Description Type Required
{token} The 'oauth_token' value returned by 'Step 1 – Initiate'. String Yes

Authorization

After completing the authorization the user will be redirected to the ‘oauth_callback’ URL defined during ‘/oauth/initiate’. 2 query string parameters will be appended to the URL. Defined in the following table.

Parameters:

Name Description Type Required
{oauth_token} The request token, as provided by 'Step 1 – Initiate'. It may be used as a state check. String Yes
{oauth_verifier} The code in include in the call to '/oauth/token'. String Yes

Step 3 – Token

To ensure same client is authorizing the application a final step is required to provide the verifier_code when calling ‘/oauth/token’. The successful response is the access ‘token’ and ‘secret’. These are the values that should be used to call Quipt API.

URLhttps://app.getquipt.com/oauth/token
 
Methodpost

Header:

Sample Response:

OAuth Basics

Quipt’s web services rely on OAuth 1.0 revision A as the authorization framework.

Web based application:
oauth-web-based

Step 1 – Initiate

This begins the OAuth 1.0a authorization process for a Quipt user. The response includes the request ‘token’ and ‘secret’ to be used in later steps.

URLhttps://app.getquipt.com/oauth/initiate
 
Methodpost

Header:

Sample Response:

Step 2 – Authorize

Redirect the user to the Quipt authorization page. If the user accepts the authorization the user will be redirected to the defined ‘oauth_callback’.

URLhttps://app.getquipt.com/#/oauth/authorizing?oauth_token={token}
 
Methodget

Parameters:

Name Description Type Required
{token} The 'oauth_token' value returned by 'Step 1 – Initiate'. String Yes

Authorization

After completing the authorization the user will be redirected to the ‘oauth_callback’ URL defined during ‘/oauth/initiate’. 2 query string parameters will be appended to the URL. Defined in the following table.

Parameters:

Name Description Type Required
{oauth_token} The request token, as provided by 'Step 1 – Initiate'. It may be used as a state check. String Yes
{oauth_verifier} The code in include in the call to '/oauth/token'. String Yes

Step 3 – Token

To ensure same client is authorizing the application a final step is required to provide the verifier_code when calling ‘/oauth/token’. The successful response is the access ‘token’ and ‘secret’. These are the values that should be used to call Quipt API.

URLhttps://app.getquipt.com/oauth/token
 
Methodpost

Header:

Sample Response: