When to Use REST and SOAP - Latest

Spectrum Spatial Guide

Product type
Software
Portfolio
Locate
Product family
Spectrumâ„¢ software
Product
Spectrumâ„¢ software > Spatial > Spectrum Spatial
Version
Latest
ft:locale
en-US
Product name
Spectrum Technology Platform
ft:title
Spectrum Spatial Guide
Copyright
2025
First publish date
2007
ft:lastEdition
2026-05-14
ft:lastPublication
2026-05-14T15:28:23.501000
L1_Product_Gateway
Locate
L2_Product_Segment
Location Intelligence
L3_Product_Brand
Precisely Spectrum Spatial
L4_Investment_Segment
LI Enterprise
L5_Product_Group
Enterprise LI
L6_Product_Name
Spectrum Spatial

Spectrum supports web service requests using REST and SOAP. They both offer similar capabilities, such as rendering, listing and describing maps and features. While our SOAP API offers more capabilities, the REST API is the more commonly used framework due to its use of JavaScript.

An important difference between the two protocols is that REST uses a named resource in a request. SOAP will accept either a named resource or parameters that are written out in the request.

A named map has the information about the map already defined and stored in the repository. At render time you cannot change the layer order or hide a layer, for example. If that is an important capability for you, choose SOAP and do not use named maps. But there are other options.

One way to use REST and have some ability to control layer rendering is to have multiple named maps where each one defines one layer.

If you want to use SOAP services in a JavaScript application, consider creating your own URL. This proxy will parse the request containing the named map and formulate it into a SOAP request containing the individual layers.

Proxies are an important component when using the Javascript API. For more information see Working with the JavaScript API section in this guide.