Authorization

Wafeq implements the OAuth 2.0 authorization framework.

Endpoints

GET /oauth/authorize/
POST /oauth/token/
POST /oauth/token/revoke/

Authorization Code Flow

Prerequisites

This guide assumes that you already have created an app.

Examples

You can find example apps implementing the authorization code flow in the oauth2-client-examples repository.

List of scopes

Scope	Description
basic	Basic access to organization info
users	Access to organization list of users
bulk_invoices	Bulk sending invoices api
chart_of_accounts.read	Read-only access to chart of accounts data
chart_of_accounts.write	Read and Write access to chart of accounts data
bank_accounts.read	Read-only access to bank_accounts data
bank_accounts.write	Read and Write access to bank accounts data
contacts.read	Read-only access to contacts data
contacts.write	Read and Write access to contacts data
tax_rates.read	Read-only access to tax_rates data
tax_rates.write	Read and Write access to tax_rates data
invoices.read	Read-only access to invoices data
invoices.write	Read and Write access to invoices data
expenses.read	Read-only access to expenses data
expenses.write	Read and Write access to expenses data
bills.read	Read-only access to bills data
bills.write	Read and Write access to bills data
reports	Read-only access to reports
payroll.read	Read-only access to payroll data
payroll.write	Read and Write access to payroll data
payment.read	Read-only access to payments data
payment.write	Read and Write access to payments data

Request User Authorization

The first step is to request authorization from the user, so your app can access the Wafeq resources in behalf that user.
To do so, your application must build and send a GET request to the /oauth/authorize/ endpoint with the following parameters:

Query Param	Value
client_id	Required: The Client ID generated after registering your application.
response_type	Required: Set to `code`.
redirect_uri	Required: The URI to redirect to after the user grants or denies permission. This URI needs to have been entered in the Redirect URI allowlist that you specified when you registered your application. The value of redirect_uri here must exactly match one of the values you entered when you registered your application, including upper or lowercase, terminating slashes, and such.
scope	Required: A space-separated list of scopes.
state	Optional, but strong recommended: This provides protection against attacks such as cross-site request forgery. See RFC-6749.

If you're implementing the PKCE extension, you must include these additional parameters.

Query Param	Value
code_challenge_method	Required: Set to `S256`
code_challenge	Required: Set to the code challenge that your app calculated.

In order to generate the code_challenge, your app should hash the code verifier using the SHA256 algorithm.
The code verifier is a random string between 43 and 128 characters in length. It can contain letters, digits,
underscores, periods, hyphens, or tildes.

Response

User accepts

Query Params	Value
code	An authorization code that can be exchanged for an Access Token.
state	The value of the `state` parameter supplied in the request.

Example,

https://your-domain.com/callback?code=NApCCg..BkWtQ&state=34fFs29kd09

User denies

Query Params	Value
error	The reason authorization failed, for example: `access_denied`.
state	The value of the state parameter supplied in the request.

Example,

https://your-domain.com/callback?error=access_denied&state=34fFs29kd09

Request Access Token

If the user accepted your request, then your app is ready to exchange the authorization code for an Access Token.
It can do this by making a POST request to the /token/ endpoint.

The body of this POST request must contain the following parameters encoded in application/x-www-form-urlencoded:

Request Body Parameter	Value
grant_type	Required: This field must contain the value `authorization_code`.
code	Required: The authorization code returned from the previous request.

If you're implementing the PKCE extension, you must include these additional parameters.

Request Body Parameter	Value
client_id	Required: The Client ID generated after registering your application.
code_verifier	Required: The value of this parameter must match the value of the code_verifier that your app generated in the previous step.

The request must also include the following HTTP headers:

Header Parameters	Value
Authorization	Required: Base 64 encoded string that contains the Client ID and Client Secret Key. The field must have the format: `Authorization: Basic <base64 encoded client_id:client_secret>`
Content-Type	Required: Always set to `application/x-www-form-urlencoded`.

Response

Key	Value Type	Value Description
access_token	string	An Access Token that can be provided in subsequent calls
refresh_token	string	An Refresh token which is used to fetch a new `access_token` to be then used in making authenticated API calls.
token_type	string	How the Access Token may be used: always `Bearer`.
expires_in	int	The time period (in seconds) for which the Access Token is valid.

Example:

curl --location \
    --request POST https://app.wafeq.com/oauth/token/ \
    --header 'Authorization: Basic NTMwO...3MWJi' \
    --header 'Content-Type: application/x-www-form-urlencoded' \
    --data-urlencode 'redirect_uri=https://your-domain.com/callback' \
    --data-urlencode 'grant_type=authorization_code' \
    --data-urlencode 'code=83YqX...mlezV'

The response will be similar to this:

{
   "access_token": "NgA6ZcYI...ixn8bUQ",
   "refresh_token": "NgAagA...Um_SHo",
   "token_type": "Bearer",
   "expires_in": 3600
}

Request a refreshed Access Token

Access tokens are deliberately set to expire after a short time, after which new tokens may be granted by supplying the refresh token originally obtained during the authorization code exchange.
In order to refresh the token, a POST request must be sent with the following body parameters encoded in application/x-www-form-urlencoded:

Request Body Parameter	Value
grant_type	Required: Set it to `refresh_token`.
refresh_token	Required: The refresh token returned from the authorization code exchange.

If you're implementing the PKCE extension, you must include these additional parameters.

Request Body Parameter	Value
client_id	Required: The Client ID generated after registering your application.

The request must also include the following HTTP headers:

Header Parameters	Value
Authorization	Required: Base 64 encoded string that contains the Client ID and Client Secret Key. The field must have the format: `Authorization: Basic <base64 encoded client_id:client_secret>`
Content-Type	Required: Always set to `application/x-www-form-urlencoded`.

Example:

curl --location \
    --request POST https://app.wafeq.com/oauth/token/ \
    --header 'Authorization: Basic NTMwO...3MWJi' \
    --header 'Content-Type: application/x-www-form-urlencoded' \
    --data-urlencode 'grant_type=refresh_token' \
    --data-urlencode 'refresh_token=0uOmz...GNu77'

The response will be similar to this:

{
   "access_token": "NgA6ZcYI...ixn8bUQ",
   "token_type": "Bearer",
   "expires_in": 3600
}