- URL:
- https://<root>/services/types/extensions
- Methods:
GET- Operations:
- Register, Unregister, Update
- Version Introduced:
- 10.1
Access requirements
Required privileges
The Sever 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.
Note that administrators assigned a custom role must also have the administrative View all content privilege assigned to them to access the API directory as an administrator. Additonally, any custom roles that include a webhook-related privilege must also include the general Publish server-based layers content privilege.
Tokens
This API requires token-based authentication. A token is automatically generated for administrators who sign in to the Server 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 Portal Directory API. For security reasons, all POST requests made to the Server Administrator API must include a token in the request body.
Description
The extensions resource is a collection of all the custom server object extensions that have been uploaded and registered with the server. You can register new server object extensions using the Register Extension operation. When updating an existing extension, you need to use the Update Extension operation. If an extension is no longer required, you can use the Unregister operation to remove the extension from the site.
Request parameters
| Parameter | Description |
|---|---|
| The response format. The default response format is Values: |
Example usage
The follwoing 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, soe2, ...],
"<soe_file_2>: [ soe3, ...]
}JSON Response example
{
"SimpleRESTSOE.soe": [
{
"Name": "SimpleRESTSOE",
"DisplayName": "Simple REST SOE",
"CLSID": "arcgissamples.soe.SimpleRESTSOE",
"Description": "Simple REST SOE.",
"Properties": {},
"Info": {
"SupportsREST": "true",
"SupportsSOAP": "false",
"AllWebCapabilities": "",
"DefaultWebCapabilities": ""
},
"Resources": {}
}
],
"EchoSoe.soe": [
{
"Name": "EchoSOE",
"DisplayName": "Echo SOE",
"CLSID": "com.esri.sss.soe.EchoSoe",
"Description": "Echos input",
"Properties": {},
"Info": {
"SupportsMSD": "true",
"AllWebCapabilities": "echo",
"DefaultWebCapabilities": "echo"
},
"Resources": {
"WSDL": "EchoSOE.wsdl"
}
}
]
}