These are primarily used for the VHD files backing the AzureVMs.Īppend blobs, which are optimized for append operations only. Page blobs are available with version and later. Page blobs, which are optimized for random read/write operations and which provide the ability to write to a range of bytes in a blob. This type of blob is the only blob type available with versions prior to. The Blob service defines three types of blobs:īlock blobs, which are optimized for streaming. A container is like a folder, containing a set of blobs every blob must reside in a container. The REST API for the Blob service exposes two resources: containers and blobs. The Blob service provides storage for entities, such as binary files and text files. The REST APIs for storage services expose the storage account as a resource. The storage account is the highest level of the namespace for accessing each of the fundamental services. Storage AccountĪll access to storage services takes place through the storage account. For more information, see Configuring the REST API.The Azure storage services support both HTTP and HTTPS however, using HTTPS is highly recommended. However, if you export and deploy the REST instance elsewhere, or if you needed to change the defaults, you will need to modify some configuration files. The REST API works out-of-the-box without any configuration. For more information, see REST API Admin. Services Directory can also be disabled through the console. The administration page is needed to refresh the site after adding, deleting, and updating services or after updating to a new version of the REST API. In addition to being a browser for your published data, Services Directory also provides access to an administrative console. For information on the rules of versioning, see REST API Versioning REST API Administration VersioningĪs the REST API evolves over time, different versions of the API will become available. You can request KML in several different ways, which is summarized in KML support. The list of supported formats includes html (HyperText Markup Language), json (JavaScript Object Notation), image, kmz (compressed KML, or Keyhole Markup Language), help, lyr (layer file), nmf (ArcGIS Explorer map file), jsapi (JavaScript), ve (Virtual Earth), and gmaps (Google Maps). The format is specified by using the query parameter f in the URL. The REST API supports responses in several formats. To get going, you can review Catalog, which is the root node for the API. You can find out additional details about all resources and operations supported by the REST API. Non-pooled services are not listed in Services Directory. One requirement of the REST API is that ArcGIS Server services must be configured as Pooled. Another set of service types that are supported as resources but have no associated operations include network, geodata, and globe services. The supported service types that include operations are map, geocode, geoprocessing, geometry, and image. Information, see Resources and Operations. 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. Each service is a resource and has a unique URL. The REST API has some level of support for each of the ArcGIS Server service types. You can browse the contents of an ArcGIS Server and obtain information such as service metadata and supported operations that can be useful in developing applications. Services Directory is a view of the ArcGIS Server REST API in HTML format. If you want to learn more about how the REST API works, you can start by following the examples in Getting Started.Įach ArcGIS Server comes with a Services Directory. Each request must contain all the information necessary for successful processing. The REST API is stateless, which means that REST does not keep track of transactions from one request to the next. From this base URL, you can traverse to any of the listed service and resources and operations associated with the service.