Stepik.org has REST API in JSON format. API endpoints are listed on https://stepik.org/api/docs, and you can also make API call there (but this page is limited to GET
requests).
Stepik.org use the same API for its web front-end (JS app) and its iOS/Android applications. Therefore, almost all the platform features are supported in this API.
All API examples are up to date and working if the build status is passing
:
Stepik API schema is flat, i.e. there are no nested end-points.
Every request returns a list of objects, even if only one object was requested. This list can contain 0 or more elements.
For example: https://stepik.org/api/courses/1
returns not a single course, but a list with single course.
All responses to GET
requests are paginated. They contain extra meta
object with the information about pagination. It may look like this:
{
meta: {
page: 1,
has_next: true,
has_previous: false
},
requested_objects: [...]
}
If the next page exists, then it can be requested using get parameter ?page=...
. By default, if no parameter is given, it’s equal to 1.
For example: https://stepik.org/api/courses
is equal to https://stepik.org/api/courses?page=1
. Next page: https://stepik.org/api/courses?page=2
and so on.
Usual page size is equal to 20 elements, but it can vary due to API endpoint, user’s permissions etc. We do not recommend to rely on a constant page size.
Response may also contain multiple objects, related to the requested object.
For example: for registered user, response from https://stepik.org/api/courses
also includes user’s course enrollments
.
In order to call Stepik.org API as a registered user, you can use this user’s OAuth2 keys.
You can get your keys by creating an application on https://stepik.org/oauth2/applications/ (while being logged in), and you can also set redirect_uri
, Client type
and Authorization grant type
there.
Authorization endpoint (Authorization code, Implicit grant; redirect_uri needed): https://stepik.org/oauth2/authorize/.
Token endpoint (Authorization code, Password and Client credentials): https://stepik.org/oauth2/token/
.
You can then obtain access token using the following client credential flow:
curl -X POST -d "grant_type=client_credentials" -u"CLIENT_ID:CLIENT_SECRET" https://stepik.org/oauth2/token/
Response:
{"access_token": "ACCESS_TOKEN", "scope": "read write", "expires_in": 36000, "token_type": "Bearer"}
Example with access token:
curl -H "Authorization: Bearer ACCESS_TOKEN" "https://stepik.org/api/social-accounts?provider=github&uid=1216"
Response:
{"meta": {"page": 1, "has_next": false, "has_previous": false}, "social-accounts": []}
- Set
grant type = autorization_code
and setredirect_uri
in your application; - Redirect user to
https://stepik.org/oauth2/authorize/?response_type=code&client_id=CLIENT_ID&redirect_uri=REDIRECT_URI
; - User should authenticate or register, and grant permissions to application;
- It redirects to
redirect_uri
and receives theCODE
; - Application asks for
ACCESS_TOKEN
:curl -X POST -d "grant_type=authorization_code&code=CODE&redirect_uri=REDIRECT_URI" -u"CLIENT_ID:SECRET_ID" https://stepik.org/oauth2/token/
; - Application behaves as user, adding
Authorization: Bearer ACCESS_TOKEN;
to request headers. - Request to
https://stepik.org/api/stepics/1
returns the current user.
You can request multiple objects using the single API call by using ?ids[]=2&ids[]=3...
.
For example: to get courses with IDs = 2
, 67
, 76
and 70
; you can to call https://stepik.org/api/courses?ids[]=2&ids[]=67&ids[]=76&ids[]=70
.
This syntax is supported by all API endpoints.
Don’t make calls with large size of ids[]
. Such calls may be rejected by the server because of a large HTTP header.
- OAuth authorization example: oauth_auth_example.py
- VideoDownloader: stepik-oauth2-videodownloader
- iOS app: Stepik iOS app
- Android app: Stepik Android app
- Code Challenge submitter: submitter.py
- Video uploading (C#): CoursePublishing
- PyCharm Edu & IntelliJ integration: intellij-community
- IntelliJ Plugin for Code Challenges: intellij-plugins