Skip to main content

Authorization

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

Clever District Admin

Prerequisites​

Before creating a Clever District Admin credential, you need to obtain a District Admin Token from your Clever account. The District Admin Token is a Base64-encoded string of your client ID and client secret in the format Base64Encode(client_id:client_secret).

To obtain your District Admin Token, you need to have a Clever account with district administrator access. You need to have your client ID and client secret from your Clever application registration. The District Admin Token is created by Base64-encoding the string client_id:client_secret. The token is sent in the Authorization: Basic {token} header to authenticate all API requests to the Clever District Admin API. For detailed information about token setup and authentication, refer to the Clever API documentation.

Create a Clever District Admin Credential​

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

New Credential Overlay – Clever District Admin

CleverDistrictAdminCred.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 Admin Token Authentication​

  1. Enter your Clever District Admin Token in the District Token (Base64Encode(client_id:client_secret)) field. This is the Base64-encoded token created from your client ID and client secret in the format Base64Encode(client_id:client_secret). The District Admin Token is sent in the Authorization: Basic {token} header to authenticate all API requests to the Clever District Admin API.

    Keep your District Admin Token secure and do not share it publicly. The token provides access to your Clever district administrator account and should be treated as sensitive information. The District Admin Token is created by Base64-encoding the string client_id:client_secret where client_id and client_secret are your Clever application credentials. The token is sent in the Authorization: Basic {token} header for all API requests to the Clever District Admin API. 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.