anchor.diff:     * **Full** - All Standard fields, plus fields rarely referenced
   
   
  -   * **Restricted** - Opaque fields accessible only to the SnapBundle platform's cloud-side code and *never transmitted over the wire* under any circumstance. These fields are *never updatable* by the developer. If a `view` query parameter is set to **Restricted**, it returns **Standard**.
  +   * **Restricted** - Opaque fields accessible only to the SnapBundle platform's cloud-side code and 
  +   *never transmitted over the wire* under any circumstance. These fields are *never updatable* by the developer. If a `view` 
  +query parameter is set to **Restricted**, it returns **Standard**.
   
   #### Requesting a Specific Serialization View
  -Every **GET** endpoint is serialized using the **Standard* JSON view by default, but can be overrode by the developer by including a `view` query string parameter set to the case-sensitive name of one of the serialization views.
  -
  -The query string parameter `view` must be a case-sensitive value matching one of the following: {`Published`, `Minimum`, `Standard`, or `Full`}. _Any value outside of this range automatically defaults to `Standard`. 
  +Every **GET** endpoint is serialized using the **Standard* JSON view by default, but can be overrode by the developer by 
  +including a `view` query string parameter set to the case-sensitive name of one of the serialization views.
  +
  +The query string parameter `view` must be a case-sensitive value matching one of the following: {`Published`, `Minimum`, 
  +`Standard`, or `Full`}. _Any value outside of this range automatically defaults to `Standard`. 
   
   **NOTE:** The default serialization view for any POST that returns a response is `Standard` and cannot be changed at this time.
   
  
positive.code: The fastest way to obtain support is by emailing <engineering@tagdynamics.net>.
  
  # Group Registration Endpoints
  Every SnapBundle Account belongs to a _security realm_. By default, the registration endpoint will extract the domain name from your email address. However, if you are using a popular email service like GMail or Yahoo, you **must** provide a custom realm name at registation. Use the **Realm Availability** endpoint to see if your desired realm name is available.   
  
  Once you've identified a realm name, your ready to complete registration. Registering for an SnapBundle Account and then confirming the email address associated with the Account registration are the only perquisites for using the platform. These two steps are required before any endpoints that require authentication can be successfully accessed.
  
  ## Understanding Realms
  The SnapBundle™ platform is a multi-tenant system by design. Each Account operates within its own _security realm_ in order to keep one Account's data separate from another Account's data. By default, the security realm is established _based on the Account registration email address' top level domain_. For example, registering for an Account with the email address developer@tagdynamics.com would result in the automatic assignment of the _tagdynamics.com_ realm, if it is available. It is possible to override this default behavior by including a _realm_ attribute in the JSON document submitted to the registration endpoint.
  
  > If you are an Individual or a Developer registering with a popular email address from say yahoo.com, gmail.com, etc. then it is strongly recommended that you register using a unique, custom realm. This approach will allow the use of a individual email, e.g. you@yahoo.com, even though a realm like yahoo.com is prohibited. If you are an Enterprise, it is strongly recommended you omit the realm, which will automatically register your email address domain as your realm.
  
  ## Realm Availability [/registration/realm/{realm}]
  ### Check to see if the named realm is available for registration [GET]
  
negative.code:                 "code" : 1,
                  "message" : "urn:uuid:66b7d3e9-69e1-499e-a867-9c4a939c6f7d"
              }
  
  + Response 400 (application/json)
  
      + Body
  