Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
<h1 class="main-title-custom">oAuth process</h1>


iCard Rest API uses oAuth2 for authorizing the HTTP requests. For more information please refer to the docs: The oAuth2 Token is sent in the header of every request. The Client ID and Client Secret are available in the iCard


Developer Portal OR you can get them when register.


oAuth Credentials

To generate your personal set of credentials for Sandbox, go to your iCard Account. There you can manage your already generated credentials as well as generate new ones. For Production ready application you must use with your valid QWAC Certificate.

Token generation

After obtaining your Client ID and Client Secret, generating an oAuth Token is standard


To generate a token, send an HTTP POST request to with:



You must use it when call authorize endpoint

Then choice provider: ex. iCard DW

After successfully create consent and confirm it with 2FA, you get a response like:

Last step is exchange “code” for client access token

POST /token HTTP/1.1
Content-Type: application/x-www-form-urlencoded


Authorization = "Basic " + base64 encoded value of concretinated Client ID and Client Secret using a semicolon for concretination.


grant_type = "client_credentials" or authorization_code" or "refresh_token"

scope = "webhooks" when using oAuth for the WebhookAPI


Content-Length: 229

code=code1234& \
grant_type=authorization_code& \
client_id=xxx1234& \
client_secret=xxxx1234& \

You will get response:

    "token_type": "Bearer",
    "expires_in": 86400,
    "access_token": "eyJ0eXA[....]VmQONULTFmkksuj6lw",
    "refresh_token": "def50200[....]2569a5a5978260c3c9ea5"