- URL:
- https://<root>/services/types/extensions
- Methods:
GET- Operations:
- Register, Update, Unregister
- Version Introduced:
- 11.2
Access requirements
Required privileges
The Enterprise Administrator API requires privilege-based access. An administrator must be assigned a specific user privilege, or role, to access any given endpoint. Listed below are the user privileges or roles an administrator can be assigned that provides access to this endpoint. If multiple privileges are listed, only one needs to be assigned to gain access.
Tokens
This API requires token-based authentication. A token is automatically generated for administrators who sign in to the Enterprise Administrator API directory's HTML interface. Tokens generated in this way are stored for the entirety of the session.
Those accessing the API directory outside of the HTML interface will need to acquire a session token from the generate operation in the Enterprise Directory API. For security reasons, all POST requests made to the Enterprise Administrator API must include a token in the request body.
Description
The extensions resource returns all the custom server object extensions (.soe file) that have been uploaded and registered with the deployment. Each extension can be represented in JSON format.
Request parameters
| Parameter | Details |
|---|---|
| The response format. The default format is Values: |
Example usage
The following is a sample request URL used to access the extensions resource:
https://organization.example.com/<context>/admin/services/types/extensions?f=pjsonJSON Response syntax
{
"<soe_file_1>": [
{soe1 object},
{soe2 object}
],
"<soe_file_2>": [
{soe1 object},
{soe2 object}
]
}