URL Structure


A “Uniform Resource Locator (URL)” is a subset of a URI, and intentionally includes the specified protocol, host, path, hash, and query string. This definition intends to address all aspects of the URL and its structure as it relates to REST API standards.

Protocol      Host              Path                    Query                    Fragment
  • APIs SHOULD NOT expand their total URL length beyond a few hundred characters, with the host+path generally being less than 100 characters for readability and usability. While there is no absolute definition of the maximum size of a URL, some rare legacy constraints for older browsers and implementations restrict you to 2,048 characters. For good measure and simplicity keeping the total length less than a few hundred forces better design and usage of request bodies at that size.


  • APIs MUST be accessible via HTTPS only (and specifically not accessible by HTTP).
  • APIS MUST follow guidance on TLS and security protocols and versions to be used with HTTPS provided by the security team.


  • Distributed APIs SHOULD be accessible under a centralized and singular hostname giving the appearance of a single API.
  • APIs MUST differentiate their deployment environment based on hostnames and NOT based on URL Path.
  • APIs MUST use hostnames (DNS) that reflect the intended usage for internal network access or public access.
  • APIs MUST NOT use a publicly available DNS hostname for a service that is intended for internal access only.
api.spscommerce.com/users    // (External)
api.sps-internal.com/users   // (Internal)
users.spscommerce.io/        // (External)
users.spscommerce-prod.in/   // (Internal)
  • When URLs are provided as referenced relative paths in your API they MUST be relative to the host (i.e. /users/profiles/1 for https://api.spscommerce.com/users/profiles/1).


  • The port MUST NOT be provided by any consumers, mentioned in documentation or required to access your API, and is always assumed to be an abstract default of the layered system based on your protocol (i.e. HTTPS, 443).



The paths of your API MUST be structured using the concepts defined for resources by REST. A resource in REST is a similar Object in Object-Oriented Programming or is like an Entity in a Database. An addressable resource is an endpoint that actions can be performed on and its state updated.

  • A resource MUST be a noun (person, place, or thing).
  • A resource SHOULD be plural.
  • A resource MUST be named based on American English (en-US) locale.
  • A resource MUST be addressed by stable and permanent identifiers only.
  • A resource MUST NOT leak or expose format or technology-specific information at any point in the path (i.e. /index.php).
  • A resource SHOULD NOT make use of an extension at any point in the path. (i.e. /test.pdf).
  • A resource containing multiple words MUST be separated using kebab-case (i.e. /change-management/).
  • A resource SHOULD NOT include acronyms or abbreviations.
  • A resource SHOULD NOT include HTTP method names.
  • A resource SHOULD NOT dynamically change its response body schema or shape based on query parameters or other dynamic behavior. If you require a differently shaped body to be returned, consider - breaking it into different resource endpoints.
  • A resource MUST only contain lowercase ISO basic Latin alphabet characters, the numeric characters 0-9, and a hyphen or dash character.
  • A resource SHOULD NOT contain api as a prefix in or a part of the path.
  • A resource MUST use normalized paths without empty path segments.
  • A resource MUST be addressable without a trailing slash on the URI (i.e. /users) and additionally SHOULD support a trailing slash as the same addressable resource (i.e. /users/ == /users).
  • Personally identifiable information and other sensitive data MUST NOT be used within the URL as it can be easily inadvertently exposed. This data should be transmitted via HTTP Header or Request Body (both of which are encrypted during transport).
/users                      // reference a collection of users
/users/1                    // reference a single user by their ID
/change-requests            // kebab casing used to represent compound noun
/colors/red                 // correct usage of accessing the "red" object part of colors collection
/devices/telephone          // correct usage of accessing the "telephone" object device.

/user                       // must be plural
/execute                    // not a noun (verb)
/changeRequests             // invalid casing
/users/documents/index.php  // leaking of a technology
/colours/red                // "colour" uses en-CA english instead of American
/devices/tel                // should not use an abbreviation for "telephone"
/api/users                  // should not contain self-identity description of "api"
/users//profile             // must not contain an empty path between two slashes
**Consideration**: Refer to further generalized considerations on naming conventions and best practices for Naming in [Serialization](/sps-api-standards/standards/serialization.html#naming).


Resources in the path SHOULD be repeated as a representation of a hierarchy for a domain model where possible as part of logical nesting for your endpoints. A hierarchical path is intended to provide context to the consumers of your API about how to use it and some expected behaviors. In many cases, a resource or nested path may directly reflect your Object or Entity Database model. This is often the natural case for brand new micro-services with a highly encapsulated domain-driven design, while other abstracted services that have evolved over time or have many layers of dependencies may represent a simplified or alternate hierarchical model through the REST API contracts than what truly exists. While both of these scenarios are valid, in either case, you’ll look to provide consistency in your hierarchy and resource naming.

**Rule of Thumb**: When thinking about whether you intend to nest resource paths, consider if a given resource can exist without the resource above it (i.e. if you were to cascade delete a top-level resource, the implication is that all resources under that path are also removed). If the answer is "no", then that is generally a positive logical nest. If the answer is "yes", you might have to consider other aspects of usage and the domain model with the decision or right answer being a bit more ambiguous. 
  • Natural hierarchical resources SHOULD be structured in a nested path.
/articles/1/comments        // the comments resource can only exist in association to the article
/comments                   // not explicitly incorrect, depending on the relationship of comments to the articles in your API.
  • Dynamic identifiers in the path:
    • MUST be used to create an addressable resolution to specific resources.
    • MUST be associated with the preceding name in the path.
    • MUST be capable of identifying the specific resource in the addressable context.
    • MUST be considered stable and not information that is subject to change on the resource.
      // CORRECT
      /articles/1/comments/2      // ID in the URL after articles "1" refers to the unique identifier for the article.
                                  // ID in the URL after comments "2" refers to the unique identifier for the article / comment composition.
      // INCORRECT
      /articles/1/2               // Unknown contextual usage of "2".
    • SHOULD be compositional with multiple identifiers specified in sequence when culturally or domain appropriate and still representing a hierarchy.
        // CORRECT
        /repos/spscommerce/sps-atlas/pulls      // the value of "spscommerce/sps-atlas" is well understand as a reference in the industry to a repository.
        /states/us/texas                        // the value for a country and state is well-understood and very stable
        /time/2010/04/12                        // date and time formatting would be appropriate for historical references, but must abide by DateTime format serialization
      For Date and Time references to format and serialization in the body or the path refer to [Serialization](/sps-api-standards/standards/serialization.html).
  • The hierarchy of nested resources SHOULD NOT exceed more than 3 resources.
/articles/1/comments/2/sentences/5/words/4  // this is realistically too long to distill effective context without overloading the consumer.
                                            // consider other options fo breaking apart the model, including ensuring the 4-level deep hierarchy is modelled correctly.
  • Resources MUST NOT incorrectly nest other resources that are only partially related.
/articles/1/comments/2/authors/5    // accessing an individual author does not make sense at this granularity. 
                                    // authors would be more accurately reflected and the root and linked to a comment.
/authors/5                          // accessing an author at the root as its own resource is a more accurate model, 
                                    // and alleviates some nesting. Additional filtering query parameters may be used to filter to an article.   
  • Resources SHOULD recognize a difference in standard canonical and historical paths, by representing historical paths with stable resources based on the time when it makes contextual sense to do so.
  • Resource endpoints for creating entities SHOULD NOT exist under many different nested paths. If your resource compositionally could be placed under multiple paths, consider placing it at the root of the path instead (which makes it difficult to establish any true sense of hierarchy to reflect).


It is often not only acceptable but encouraged to add additional shortcuts to your API if portions of the path become superfluous or with the usage of unnecessary IDs based on your implementation.

  • Nested collection resources with globally unique identifiers in their context MAY NOT require the specification of all parent unique identifiers in the resource path.
/articles/1/comments/2/ratings/5    // if the rating identifier is globally unique for all articles and comments, 
                                    // then passing the article identifier and comment identifier is not only annoying for consumers of the API,
                                    // but does also require validation of those identifiers within the context on the server.
/articles/comments/ratings/5        // shortcutting the superfluous identifiers when possible is acceptable.
  • Nested collection resources SHOULD apply inherit filters of the same object accessible at other convenient nested paths.
// Example 1 - Comments are accessible and filtered under articles nested path,
// but also accessible across all articles (inherit authorization may filter comments to those created by the requestor by default).
/articles/1/comments            // Path may work for both retrieving as well as creating new comments for specific articles.
// Example 2 - Authors are accessible and filtered under all comments for the article.
// Authors are also accessible and searchable at the root across all articles.
/articles/1/comments/authors    // Path likely only works for retrieving authors, creation of authors happens only under the root /authors endpoint.

Static Collections

Many APIs may contain static or reference collections that are often used to display types or enumeration values.

  • Static collections MUST be represented as resource endpoints within your API.
  • Static collection resources SHOULD exist as a root endpoint unless the context is better represented as a nested collection.
/types              // if "types" is well understand and used across the domain, it might be represented at the root.
/articles/types     // if "types" is contextually referring to article types, representation under a nested path for articles makes more sense.


REST only provides constraints and conventions for working with well-defined resources. In practice, an API should strive to derive consistent resource endpoints for their paths but may have the unavoidable scenario of needing to define more action-based endpoints that act upon a resource. A common use case is for APIs that must model actions related to reporting. In these rare cases, you should model actions based on the following guidelines:

  • Action style endpoints MUST define resources with verbs (actions).
  • You SHOULD NOT use actions unless it is explicitly necessary. Prefer translation of the action to a noun-based resource where possible, with a consistent model.
// Preference - A noun if you intend to allow standard operations as a normal resource (i.e. read, create, update, delete).
// Acceptable - A verb if this is the only endpoint, the model does not represent a domain (i.e. is a one time analysis report), and is a single action performed.
/articles/1/analyze     // use a verb to describe the action with a non-standard model returned.
Using a single endpoint verb to perform an action is only valid as an HTTP POST Method as shown on [Request & Response](/sps-api-standards/standards/request-response.html).

Query Parameters

Query parameters specified on a REST API resource endpoint generally represent an attribute of a resource and rather than a resource itself (unless referencing another resource). Query parameters are a great method of hiding complexities from your resource path when necessary. They are most often used for specifying how to filter a collection and other behaviors discussed in Collections.

  • Query parameter keys MUST include only alpha-numeric characters and periods: [Aa0-Zz9].
  • Query parameter keys with periods in them MUST only be used to signify relationships in object references.
  • Query parameter keys MUST use camelCase.
  • Query parameters MUST accept a collection of values by using the same query key multiple times, each with a different value.
  • Query parameter specification sequence or order MUST NOT impact the response of the request in any way.
  • Query parameters MUST be optional. If necessary then they default to sensible choices that balance consumer expectations and API performance.
  • Query parameters that have defaulted values across many resource endpoints SHOULD keep defaults consistent across the API as long as there are no implications on performance in doing so. Where deviation is necessary, it should result in specific annotations to mention this in the Open API documentation. Consider inverting a query parameter name (i.e. “published” vs “unpublished”) if different defaults are required on different endpoints in order to be consistent with the defaulted values.
  • Additional query parameters not used by the API MUST be disregarded without error to make compatibility and transitions simpler and adhere to standards of tolerance.
  • Personally identifiable information and other sensitive data SHOULD NOT be present in the Query Parameters as they can be easily inadvertently exposed. This data should be transmitted via HTTP Request Body.


URL fragments are most often used as anchor points for HTML pages or search functionality proprietary to a particular site. Fragments MUST NOT be used for any functionality in creating REST APIs.