How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Al-Farabi Kazakh National University

Al-Farabi Kazakh National University user API

The user API from Al-Farabi Kazakh National University — 38 operation(s) for user.

Documentation Provider Profile APIs.io OpenAPI GitHub

Al-Farabi Kazakh National University user API is one of 51 APIs that Al-Farabi Kazakh National University publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include User. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 47 operations across 38 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, https://open.kaznu.kz/api.

47 operations 38 paths 4 schemas 2 DELETE21 GET3 PATCH19 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://open.kaznu.kz/api
Authentication
HTTP Basic
Contact
dl@kaznu.kz
Resource Areas
1

Authentication & Security 1

Al-Farabi Kazakh National University user API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (Basic). By default, every request must be authenticated.

Paths & Operations 47

Across 38 paths, the API surfaces 47 operations — 2 DELETE, 21 GET, 3 PATCH, 19 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

user 47
GET
/user/v1/account/password_reset/
HTTP end-point for GETting a description of the password reset form.
user_v1_account_password_reset_list → 200
POST
/user/v1/account/password_reset/token/validate/
HTTP end-point to validate password reset token.
user_v1_account_password_reset_token_validate_create → 201
GET
/user/v1/account/registration/
HTTP end-points for creating a new user.
user_v1_account_registration_list → 200
POST
/user/v1/account/registration/
Create the user's account.
user_v1_account_registration_create → 201
GET
/user/v1/accounts
GET /api/user/v1/accounts?username={username1,username2} GET /api/user/v1/accounts?email={useremail} (Staff Only) GET /api/user/v1/accounts?lmsuserid={lmsuserid} (Staff Only)
user_v1_accounts_list → 200
POST
/user/v1/accounts/cancel_retirement/
POST /api/user/v1/accounts/cancelretirement/
user_v1_accounts_cancel_retirement → 201
POST
/user/v1/accounts/deactivate_logout/
POST /api/user/v1/accounts/deactivatelogout/
user_v1_accounts_deactivate_logout_create → 201
POST
/user/v1/accounts/name_change/
POST /api/user/v1/accounts/namechange/
user_v1_accounts_name_change_create → 201
POST
/user/v1/accounts/name_change/{username}/confirm/
POST /api/user/v1/account/namechange/{username}/confirm
user_v1_accounts_name_change_confirm 1 param → 201
POST
/user/v1/accounts/replace_usernames/
POST /api/user/v1/accounts/replaceusernames/ { "usernamemappings": [ {"currentusername1": "desiredusername1"}, {"currentusername2": "desiredusername2"} ] } POST Parameters A POST request must include…
user_v1_accounts_replace_usernames_create → 201
POST
/user/v1/accounts/retire/
POST /api/user/v1/accounts/retire/
user_v1_accounts_post → 201
POST
/user/v1/accounts/retire_misc/
POST /api/user/v1/accounts/retiremisc/
user_v1_accounts_post → 201
POST
/user/v1/accounts/retirement_cleanup/
POST /api/user/v1/accounts/retirementcleanup/
user_v1_accounts_cleanup → 201
POST
/user/v1/accounts/retirement_partner_report/
POST /api/user/v1/accounts/retirementpartnerreport/
user_v1_accounts_retirement_partner_report_create → 201
PUT
/user/v1/accounts/retirement_partner_report/
PUT /api/user/v1/accounts/retirementpartnerreport/
user_v1_accounts_retirement_partner_report_update → 200
POST
/user/v1/accounts/retirement_partner_report_cleanup/
POST /api/user/v1/accounts/retirementpartnerreportcleanup/
user_v1_accounts_retirement_partner_cleanup → 201
GET
/user/v1/accounts/retirement_queue/
GET /api/user/v1/accounts/retirementqueue/ {'cooloffdays': 7, 'states': ['PENDING', 'COMPLETE'], 'limit': 500}
user_v1_accounts_retirement_queue → 200
GET
/user/v1/accounts/retirements_by_status_and_date/
GET /api/user/v1/accounts/retirementsbystatusanddate/ ?startdate=2018-09-05&enddate=2018-09-07&state=COMPLETE
user_v1_accounts_retirements_by_status_and_date → 200
POST
/user/v1/accounts/search_emails
POST /api/user/v1/accounts/searchemails Content Type: "application/json" { "emails": ["edx@example.com", "staff@example.com"] }
user_v1_accounts_search_emails → 201
PATCH
/user/v1/accounts/update_retirement_status/
PATCH /api/user/v1/accounts/updateretirementstatus/
user_v1_accounts_update_retirement_status_partial_update → 200
GET
/user/v1/accounts/{username}
GET /api/user/v1/accounts/{username}/
user_v1_accounts_read 1 param → 200
PATCH
/user/v1/accounts/{username}
PATCH /api/user/v1/accounts/{username}/
user_v1_accounts_partial_update 1 param → 200
POST
/user/v1/accounts/{username}/deactivate/
POST /api/user/v1/accounts/{username}/deactivate/
user_v1_accounts_deactivate_create 1 param → 201
POST
/user/v1/accounts/{username}/image
POST /api/user/v1/accounts/{username}/image
user_v1_accounts_image_create 1 param → 201
DELETE
/user/v1/accounts/{username}/image
DELETE /api/user/v1/accounts/{username}/image
user_v1_accounts_image_delete 1 param → 204
GET
/user/v1/accounts/{username}/retirement_status/
GET /api/user/v1/accounts/{username}/retirementstatus/ Returns the RetirementStatus of a given user, or 404 if that row doesn't exist.
user_v1_accounts_retirement_status_read 1 param → 200
GET
/user/v1/accounts/{username}/verification_status/
IDVerification Status endpoint
user_v1_accounts_verification_status_list 1 param → 200
GET
/user/v1/accounts/{username}/verifications/
IDVerificationStatusDeetails endpoint to retrieve more details about ID Verification status
user_v1_accounts_verifications_list 1 param → 200
GET
/user/v1/forum_roles/{name}/users/
Forum roles are represented by a list of user dicts
user_v1_forum_roles_users_list 3 params → 200
GET
/user/v1/me
GET /api/user/v1/me
user_v1_get → 200
POST
/user/v1/preferences/email_opt_in/
Post function for updating the email opt in preference.
user_v1_preferences_email_opt_in_create → 201
GET
/user/v1/preferences/time_zones/
Use Cases
user_v1_preferences_time_zones_list → 200
GET
/user/v1/preferences/{pref_key}/users/
DRF class for listing a user's preferences
user_v1_preferences_users_list 3 params → 200
GET
/user/v1/preferences/{username}
GET /api/user/v1/preferences/{username}/
user_v1_preferences_read 1 param → 200
PATCH
/user/v1/preferences/{username}
PATCH /api/user/v1/preferences/{username}/
user_v1_preferences_partial_update 1 param → 200
GET
/user/v1/preferences/{username}/{preference_key}
GET /api/user/v1/preferences/{username}/{preferencekey}
user_v1_preferences_read 2 params → 200
PUT
/user/v1/preferences/{username}/{preference_key}
PUT /api/user/v1/preferences/{username}/{preferencekey}
user_v1_preferences_update 2 params → 200
DELETE
/user/v1/preferences/{username}/{preference_key}
DELETE /api/user/v1/preferences/{username}/{preferencekey}
user_v1_preferences_delete 2 params → 204
GET
/user/v1/user_prefs/
DRF class for interacting with the UserPreference ORM
user_v1_user_prefs_list 2 params → 200
GET
/user/v1/user_prefs/{id}/
DRF class for interacting with the UserPreference ORM
user_v1_user_prefs_read 1 param → 200
GET
/user/v1/users/
DRF class for interacting with the User ORM object
user_v1_users_list 2 params → 200
GET
/user/v1/users/{id}/
DRF class for interacting with the User ORM object
user_v1_users_read 1 param → 200
POST
/user/v1/validation/registration
POST /api/user/v1/validation/registration/
user_v1_validation_registration_create → 201
GET
/user/v2/account/registration/
HTTP end-points for creating a new user.
user_v2_account_registration_list → 200
POST
/user/v2/account/registration/
Create the user's account.
user_v2_account_registration_create → 201
GET
/user/{api_version}/account/login_session/
HTTP end-points for logging in users.
user_account_login_session_list 1 param → 200
POST
/user/{api_version}/account/login_session/
POST /user/{apiversion}/account/loginsession/
user_account_login_session_create 1 param body → 200400403

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are IDVerificationDetails (6 properties), user_api.User (6 properties), UserPreference (4 properties), CountryTimeZone (2 properties). Each schema is shown below with its type and property counts.

UserPreference
object
4 properties 3 required
user_api.User
object
6 properties
IDVerificationDetails
object
6 properties 3 required
CountryTimeZone
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

al-farabi-kazakh-national-university-user-api-openapi.yml Raw ↑

Other APIs Al-Farabi Kazakh National University publishes across the network.

Al-Farabi Kazakh National University agreements API
AE Profile APIs.io
Al-Farabi Kazakh National University bookmarks API
AE Profile APIs.io
Al-Farabi Kazakh National University certificates API
AE Profile APIs.io
Al-Farabi Kazakh National University change_email_settings API
AE Profile APIs.io
Al-Farabi Kazakh National University cohorts API
AE Profile APIs.io
Al-Farabi Kazakh National University commerce API
AE Profile APIs.io
Al-Farabi Kazakh National University completion API
AE Profile APIs.io
Al-Farabi Kazakh National University course_experience API
AE Profile APIs.io
Al-Farabi Kazakh National University course_home API
AE Profile APIs.io
Al-Farabi Kazakh National University course_live API
AE Profile APIs.io
Al-Farabi Kazakh National University course_modes API
AE Profile APIs.io
Al-Farabi Kazakh National University courses API
AE Profile APIs.io
#User
← Back to A APIs
API Details
ID
al-farabi-kazakh-national-university:al-farabi-kazakh-national-university-user-api
Base URL
https://open.kaznu.kz/api
Docs
https://open.kaznu.kz/
Provider
Al-Farabi Kazakh National University
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=al-farabi-kazakh-national-university-user-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/al-farabi-kazakh-national-university-user-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Al-Farabi Kazakh National University user API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.