Skip to main content
Version: Mentor 2.6

Updating Organizations' Details

Organization administrators and system administrators can update an organization's details such as name and description.

Additionally, system administrators can also configure organizations that are related through an Associated policy. To learn more about the types of policies that can be configured, see Policy Architecture.

note
  1. After receiving the application's link through email, organization administrators must sign up on the application. See the Organization Administrator section to learn more.
  2. Log in using {{url}}/user/v1/account/login to generate an access_token.

HTTP Request

Method: PATCH

{{url}}/user/v1/organization/update/{organization_id}

Path ParameterData TypeDescriptionRequired
organization_idInteger

Users should specify the organization ID to update the organization's details.

Example: 12

True

Request Body

Payload ParameterData TypeDescriptionRequired
nameString

Updated organization's name.

Example: "ShikshaLokam"

False
descriptionString

Updated description of the organization.

Example: "Empowering educational leadership."

False
related_orgsArray of integers

Only system administrators can specify the IDs of organizations that are related through an Associated policy.

Example: [3,4]

False

Request Header

KeyValueDescriptionRequired

X-auth-token

bearer {{access_token}}

The access_token received from the login response.

True

accept-language

{{hi}}

The response obtained will be in Hindi. If not provided, the response will be in English (default).

False

Response

If successful, this method returns a 200 OK response code. If the organization does not exist, this method returns a 400 Bad Request response.

Response ParameterData TypeDescription
responseCodeStringA success response.
messageStringA success message.
resultArray of strings[ ]
metaObject
  • The formsVersion key specifies the versions of User service forms.
  • The correlation key specifies the API request ID.

Deactivating Organizations

System administrators can deactivate organizations that no longer exists.

HTTP Request

Method: POST

{{url}}/user/v1/admin/deactivateOrg/{organization_id}

Path ParameterData TypeDescriptionRequired
organization_idInteger

ID of the organization that you want to deactivate.

Example: 12

True

Request Body

This method does not require a request body.

Request Header

KeyValueDescriptionRequired

X-auth-token

bearer {{access_token}}

The access_token received from the login response.

True

accept-language

{{hi}}

The response obtained will be in Hindi. If not provided, the response will be in English (default).

False

Response

If successful, this method returns a 202 Accepted response code. If the organization is already deleted, this method returns a 400 Bad Request response.

Response ParameterData TypeDescription
responseCodeStringA success response.
messageStringA success message.
resultArray of objectsThe deactivated_users key specifies the number of users at the organization whose accounts are deactivated.
metaObject
  • The formsVersion key specifies the versions of User service forms.
  • The correlation key specifies the API request ID.

Deactivating Users

If a user leaves the organization, the organization administrator can deactivate the user's account.

note
  1. After receiving the application's link through email, organization administrators must sign up on the application. See the Organization Administrator section to learn more.
  2. Log in using {{url}}/user/v1/account/login to generate an access_token.

HTTP Request

Method: POST

{{url}}/user/v1/org-admin/deactivateUser

Request Body

Body ParameterData TypeDescriptionRequired
idArray of integers

ID of users whose accounts you want to deactivate.

Example: [1,2]

True
emailArray of strings

Instead of user IDs, you can also specify the email IDs of users whose accounts you want to deactivate.

Example: [john@shikshalokam.org, clara@shikshalokam.org]

True

Request Header

KeyValueDescriptionRequired

X-auth-token

bearer {{access_token}}

The access_token received from the login response.

True

accept-language

{{hi}}

The response obtained will be in Hindi. If not provided, the response will be in English (default).

False

Response

If successful, this method returns a 202 Accepted response code. If the user is already deleted, this method returns a 400 Bad Request response code.

Response ParameterData TypeDescription
responseCodeStringA success response.
messageStringA success message.
resultArray of strings[ ]
metaObject
  • The formsVersion key specifies the versions of User service forms.
  • The correlation key specifies the API request ID.