ArcGIS Workflow Manager REST API - Overview


The ArcGIS Server REST API, short for Representational State Transfer, provides a simple, open Web interface to services hosted by ArcGIS Server. All resources and operations exposed by the REST API are accessible through a hierarchy of endpoints or Uniform Resource Locators (URLs) for each GIS service published with ArcGIS Server.

When using the REST API, you typically start from a well-known endpoint, which represents the server catalog. The table of contents for this Help system mimics the hierarchy of resources in the REST API. The default start URL for an ArcGIS Server installation is:

For example, to get to the root directory of ArcGIS Online services, the URL is:

From this base URL, you can traverse to any of the listed service and resources and operations associated with the service.

The REST API is stateless, which means that REST does not keep track of transactions from one request to the next. Each request must contain all the information necessary for successful processing.

Getting Started

If you want to learn more about how the REST API works, you can start by following the examples in Getting Started.

Resources and Operations

The REST API has some level of support for each of the ArcGIS Server service types. Each service is a resource and has a unique URL. Although a REST system always returns only representations of resources to the clients, for the sake of simplicity, the resources of the ArcGIS REST API are divided into two types: resources and operations.

The supported service types that include operations are map, geocode, geoprocessing, geometry, and image. Another set of service types that are supported as resources but have no associated operations include network, geodata, and globe services. One requirement of the REST API is that ArcGIS Server services must be configured as Pooled. Non-pooled services are not listed in Services Directory.

You can find out additional details about all resources and operations supported by the REST API. To get going, you can review Catalog, which is the root node for the API.