- URL:
- https://<root>/system/interceptors/testURLPattern
- Methods:
POST- Version Introduced:
- 12.0
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 ArcGIS 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 ArcGIS Server Administrator API generate operation. For security reasons, all POST requests made to the ArcGIS Server Administrator API must include a token in the request body.
Description
The test operation allows administrators to test how a URL pattern will behave once a service interceptor is deployed. This operation returns a list of services that match the pattern and could potentially be intercepted.
Request parameters
| Parameter | Details |
|---|---|
(Required) | A sample URL pattern to be tested. For more information on URL patterns, see the URL Patterns documentation. Example |
| The response format. The default format is Values: |
Example usage
The following is a sample POST request for the test operation:
POST /<context>/system/interceptors/testURLPattern HTTP/1.1
Host: organization.example.com
Content-Type: application/x-www-form-urlencoded
Content-Length: []
urlPattern=MapServer&f=pjson&token=<ACCESS_TOKEN>JSON Response example
{
"pattern": "MapServer",
"count": 5,
"services": [
"/rest/services/Map/MapServer",
"/rest/services/SampleWorldCities/MapServer",
"/rest/services/USA/MapServer",
"/rest/services/VEG/MapServer",
"/rest/services/System/DynamicMappingHost/MapServer"
]
}