Clever District Admin API provides district administrators with comprehensive access to manage educational data across multiple schools, enabling centralized administration of student information, teacher accounts, and educational application integrations.
Power end-to-end data operations for your Clever District Admin API with Nexla. Our bi-directional Clever District Admin connector is purpose-built for Clever District Admin, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Clever District Admin or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Clever District Admin workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
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.
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
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
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.
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Clever District Admin connector tile, then select the credential that will be used to connect to the Clever District Admin instance, and click Next; or, create a new Clever District Admin credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Clever District Admin endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.
Fetch All Tokens
This endpoint retrieves API tokens for the authenticated district administrator. Use this endpoint when you need to access token information or manage API tokens for district administrators.
This endpoint automatically retrieves API tokens for the authenticated district administrator. No additional configuration is required beyond selecting this endpoint template.
The endpoint uses GET requests to https://clever.com/oauth/tokens. The endpoint URL is automatically constructed based on the Clever OAuth base URL.
The endpoint does not use pagination and returns the complete token information in a single request.
The endpoint will return API tokens for the authenticated district administrator. The response data is extracted from the root-level object in the API response ($), and Nexla will process the entire response structure.
The endpoint uses a static URL (iteration.type: static.url) and does not require pagination. The response data path is $, which extracts the entire root-level object from the API response. For detailed information about retrieving tokens, see the Clever API documentation.
Fetch All Districts
This endpoint retrieves a list of districts this district administrator manages. This endpoint uses a two-step process: first, it fetches an access token, then uses that token to retrieve district data. Use this endpoint when you need to access district information for all districts managed by the district administrator.
This endpoint automatically retrieves all districts managed by the district administrator. No additional configuration is required beyond selecting this endpoint template.
The endpoint uses a two-step process: first, it makes a GET request to https://clever.com/oauth/tokens to fetch an access token, then it uses that access token in the Authorization: Bearer {access_token} header to make a GET request to https://api.clever.com/v3.0/districts?limit=10000 to retrieve district data.
The endpoint uses token-based pagination for the second step, automatically fetching additional pages as needed using the starting_after query parameter. When a response includes data items, Nexla automatically uses the ID of the last item as the starting_after parameter in the subsequent request to fetch the next page of results.
The endpoint will return all districts managed by the district administrator. The response data is extracted from the data array in the API response ($.data[*]), with each district record processed individually.
This endpoint uses a chained API call pattern where the first step fetches an access token and the second step uses that token to retrieve district data. The second step supports pagination through the starting_after token mechanism. When a response includes data items, Nexla automatically uses the ID of the last item from the data array as the starting_after parameter in the subsequent request to fetch the next page of results. The endpoint uses token-based pagination (iteration.type: paging.next.token) through the starting_after mechanism. The response data path is $.data[*], which extracts all items from the data array in the API response. The endpoint limits results to 10,000 items per request. For detailed information about retrieving districts, see the Clever API documentation.
Fetch All Sections
This endpoint retrieves a list of all sections. This endpoint uses a two-step process: first, it fetches an access token, then uses that token to retrieve section data. Use this endpoint when you need to access section information, class sections, or section metadata for all districts managed by the district administrator.
This endpoint automatically retrieves all sections from all districts managed by the district administrator. No additional configuration is required beyond selecting this endpoint template.
The endpoint uses a two-step process: first, it makes a GET request to https://clever.com/oauth/tokens to fetch an access token, then it uses that access token in the Authorization: Bearer {access_token} header to make a GET request to https://api.clever.com/v3.0/sections?limit=10000 to retrieve section data.
The endpoint uses token-based pagination for the second step, automatically fetching additional pages as needed using the starting_after query parameter. When a response includes data items, Nexla automatically uses the ID of the last item as the starting_after parameter in the subsequent request to fetch the next page of results.
The endpoint will return all sections from all districts managed by the district administrator. The response data is extracted from the data array in the API response ($.data[*]), with each section record processed individually.
This endpoint uses a chained API call pattern where the first step fetches an access token and the second step uses that token to retrieve section data. The second step supports pagination through the starting_after token mechanism. When a response includes data items, Nexla automatically uses the ID of the last item from the data array as the starting_after parameter in the subsequent request to fetch the next page of results. The endpoint uses token-based pagination (iteration.type: paging.next.token) through the starting_after mechanism. The response data path is $.data[*], which extracts all items from the data array in the API response. The endpoint limits results to 10,000 items per request. For detailed information about retrieving sections, see the Clever API documentation.
Fetch All Users
This endpoint retrieves a list of contact, district admin, staff, student, and/or teacher users in all districts this district administrator manages. This endpoint uses a two-step process: first, it fetches an access token, then uses that token to retrieve user data. Use this endpoint when you need to access user information, user roles, or user metadata for all districts managed by the district administrator.
This endpoint automatically retrieves all users from all districts managed by the district administrator. No additional configuration is required beyond selecting this endpoint template.
The endpoint uses a two-step process: first, it makes a GET request to https://clever.com/oauth/tokens to fetch an access token, then it uses that access token in the Authorization: Bearer {access_token} header to make a GET request to https://api.clever.com/v3.0/users?limit=10000 to retrieve user data.
The endpoint uses token-based pagination for the second step, automatically fetching additional pages as needed using the starting_after query parameter. When a response includes data items, Nexla automatically uses the ID of the last item as the starting_after parameter in the subsequent request to fetch the next page of results.
The endpoint will return all users from all districts managed by the district administrator. The response data is extracted from the data array in the API response ($.data[*]), with each user record processed individually.
This endpoint uses a chained API call pattern where the first step fetches an access token and the second step uses that token to retrieve user data. The second step supports pagination through the starting_after token mechanism. When a response includes data items, Nexla automatically uses the ID of the last item from the data array as the starting_after parameter in the subsequent request to fetch the next page of results. The endpoint uses token-based pagination (iteration.type: paging.next.token) through the starting_after mechanism. The response data path is $.data[*], which extracts all items from the data array in the API response. The endpoint limits results to 10,000 items per request. For detailed information about retrieving users, see the Clever API documentation.
Fetch All Schools
This endpoint retrieves all schools in all districts this district administrator manages. This endpoint uses a two-step process: first, it fetches an access token, then uses that token to retrieve school data. Use this endpoint when you need to access school information, school settings, or school metadata for all districts managed by the district administrator.
This endpoint automatically retrieves all schools from all districts managed by the district administrator. No additional configuration is required beyond selecting this endpoint template.
The endpoint uses a two-step process: first, it makes a GET request to https://clever.com/oauth/tokens to fetch an access token, then it uses that access token in the Authorization: Bearer {access_token} header to make a GET request to https://api.clever.com/v3.0/schools?limit=10000 to retrieve school data.
The endpoint uses token-based pagination for the second step, automatically fetching additional pages as needed using the starting_after query parameter. When a response includes data items, Nexla automatically uses the ID of the last item as the starting_after parameter in the subsequent request to fetch the next page of results.
The endpoint will return all schools from all districts managed by the district administrator. The response data is extracted from the data array in the API response ($.data[*]), with each school record processed individually.
This endpoint uses a chained API call pattern where the first step fetches an access token and the second step uses that token to retrieve school data. The second step supports pagination through the starting_after token mechanism. When a response includes data items, Nexla automatically uses the ID of the last item from the data array as the starting_after parameter in the subsequent request to fetch the next page of results. The endpoint uses token-based pagination (iteration.type: paging.next.token) through the starting_after mechanism. The response data path is $.data[*], which extracts all items from the data array in the API response. The endpoint limits results to 10,000 items per request. For detailed information about retrieving schools, see the Clever API documentation.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Clever District Admin data sources can also be manually configured to ingest data from any valid Clever District Admin API endpoint, including endpoints not covered by the pre-built templates, chained API calls to fetch data from multiple endpoints, or custom authentication headers. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers. Clever District Admin API endpoints typically follow the pattern https://api.clever.com/v3.0/{endpoint_path} or https://clever.com/oauth/{endpoint_path}.
The endpoint requires Basic Authentication with your District Admin Token, which is handled automatically by your credential configuration. Some endpoints may require first fetching an access token and then using that token for subsequent requests. Clever District Admin API responses typically use a data array to contain the actual data for list endpoints, or a root-level object for single resource endpoints. For detailed information about Clever District Admin API endpoints and available APIs, see the Clever API documentation.
Once all of the relevant settings have been configured, click the Save button to save your data source configuration. Nexla will now begin ingesting data from the configured endpoint according to the configured schedule and endpoint settings.
