Skip to main content
Redirection based OAuth journeys offer secure access to third-party apps such as Quicko, just like Google OAuth app can be used to get access to users google profile, contacts, calendar, emails etc. Following steps explain a standard OAuth journey:
1

User navigates to your OAuth Login Page

User navigates to your OAuth Login Page
2

Upon successful login control is passed back with a request_token

Upon successful login control is passed back with a request_token to the registered redirect URL
3

Quicko exchanges short lived request_token with a long lived access_token

Quicko exchanges short lived request_token with a long lived access_token
4

Quicko can now import data using APIs

Quicko can now import data using APIs provided by you using access_token
NoteAn optional redirect param should be supported by your OAuth login endpoint, which will be used to navigate the user after a successful login attempt. Redirect URL request parameter must be Base64 encoded, eg: https://join.quicko.com will be used like:

​
Authorize Endpoint

The authorize endpoint is used to exchange a request token for a resource owner’s access token.
​
request_token
string
required
The short-lived request token obtained from the OAuth login page

​
API Reference