Skip to main content

Authorization

Follow this guide to create a new Clever credential that will allow Nexla to authenticate to and exchange data with your Clever account.
clever_api_auth.png

Clever

Prerequisites​

Before creating a Clever credential, you need to obtain a District App Token from your Clever account. The District App Token is required to authenticate with the Clever API v3.0.

To obtain your District App Token, you need to have a Clever account with a district that has authorized your application. Once a district authorizes your application, you can generate a District App Token. The token is generated when a district authorizes your application, and you can copy it from the district's Overview page in the Clever UI. The District App Token is sent in the Authorization: Bearer {token} header to authenticate all API requests to the Clever API v3.0. For detailed information about token setup and authentication, refer to the Clever API documentation.

Create a Clever Credential​

  • To create a new Clever credential, after selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – Clever

CleverCred.png

Credential Name & Description​

  1. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

    Resource descriptions are recommended but are not required. They should be used provide information about the resource purpose, data freshness, etc. that can help the owner and other users efficiently understand and utilize the resource.

District App Token Authentication​

  1. Enter your Clever District App Token in the District App Token field. This is the token generated when a district authorizes your application. You can copy the token from the district's Overview page in the Clever UI by clicking on a district. The District App Token is sent in the Authorization: Bearer {token} header to authenticate all API requests to the Clever API v3.0.

    Keep your District App Token secure and do not share it publicly. The token provides access to your Clever district data and should be treated as sensitive information. The District App Token is sent in the Authorization: Bearer {token} header for all API requests to the Clever API v3.0. To obtain a token, a district must authorize your application first. For detailed information about obtaining and managing tokens, see the Clever API documentation.

Save the Credential​

  1. Once all of the relevant steps in the above sections have been completed, click the Save button at the bottom of the overlay to save the configured credential.

  2. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation and can be selected for use with a new data source or destination.