anchor.diff:  Returns detailed information about the entry with the specified key (path). If the optional parameter `raw` is supplied, a raw configuration is returned instead of the normal response.
   
   + Parameters
  -    + organization (string, required) - The `organization` who built the `application` for which the configuration of the entry is meant
  -    + application (string, required) - The `application` to which the configuration of the entry belongs to
  -    + scope (string, required) - The `application` specific `scope` to which the configuration of the entry belongs to
  -    + slug (string, required) - The identifier of the requested entry that is unique within the namespace created by `organization`, `application` and `scope`
  -    + raw (string, optional) - If this parameter is supplied, the API will attempt to return the requested configuration snippet in the given `raw` format (regex: ^[a-zA-Z0-9\-\.\_]+$)
  +    + organization: `apache` (string, required) - The `organization` who built the `application` for which the configuration of the entry is meant
  +    + application: `tomcat` (string, required) - The `application` to which the configuration of the entry belongs to
  +    + scope: `server.xml` (string, required) - The `application` specific `scope` to which the configuration of the entry belongs to
  +    + slug: `tomcat9-serverxml-example` (string, required) - The identifier of the requested entry that is unique within the namespace created by `organization`, `application` and `scope`
  +    + raw: `xml` (string, optional) - If this parameter is supplied, the API will attempt to return the requested configuration snippet in the given `raw` format (regex: ^[a-zA-Z0-9\-\.\_]+$)
   
   + Response 200 (application/json)
       + Attributes (object)
           + data (object) - The actual details about the entry
               + key (object) - The key and its separate parts
  -                + full (string) - The full key (path) of the entry
  -                + organization (string) - The organization of the application to which the snippet belongs to
  -                + application (string) - The application to which the snippet belongs to
  -                + scope (string) - The application internal scope for the configuration snippet
  -                + slug (string) - The identifying slug of the entry that is unique within the namespace created by `organization`, `application` and `scope`
  +                + full: `apache/tomcat/server.xml/tomcat9-serverxml-example` (string) - The full key (path) of the entry
  +                + organization: `apache` (string) - The organization of the application to which the snippet belongs to
  +                + application: `tomcat` (string) - The application to which the snippet belongs to
  +                + scope (string): `server.xml` - The application internal scope for the configuration snippet
  +                + slug (string): `tomcat9-serverxml-example` - The identifying slug of the entry that is unique within the namespace created by `organization`, `application` and `scope`
               + meta (object) - Additional information about the entry
  -                + title (string) - The descriptive title of the entry
  -                + description (string) - The extended description of the entry
  -                + author (string) - The name of the creator of the entry
  -                + created_at (number) - A timestamp of the creation date of the entry
  -            + value (array[object])
  -                + format (string) - A configuration format, e.g. **ini**
  -                + value (string) - The configuration snippet in above mentioned format
  +                + title: `Tomcat 9 configuration for server.xml` (string) - The descriptive title of the entry
  +                + description: `The server.xml is Tomcats main configuration file and therefore very important. ...` (string) - The extended description of the entry
  +                + author: `Namoshek` (string) - The name of the creator of the entry
  +                + created_at: `1475478234` (number) - A timestamp of the creation date of the entry
  +            + value (array[Converted Snippet])
  +                
   
   + Response 200 (text/plain)
  +
  +        <?xml version="1.0" encoding="UTF-8"?>
  +        <Server>
  +            ...
  +        </Server>
   
   + Response 400 (application/json)
       + Attributes (Error Response)
  
positive.code: 
  + Request (application/json)
      + Attributes (object)
          + username: `the_username` (string, required)
          
              The username must be between 3 and 20 signs long and may contain only letters a-z (lower- and upper-case), the numbers 0-9 and dots (.) as well as dashes (-).
  
              Regex: ^[a-zA-Z0-9\-\.]{3,20}$
              
          + password: `somePassword` (string, required)
          
              The password must be at least 8 signs long and contain at least one lower-case letter, one upper-case letter and one digit. 
              To harden security, the user is encouraged to use special characters as well.
  
              Regex: ^(?=.*[a-z])(?=.*[A-Z])(?=.*[0-9]).{8,}$
          
          + email: `an@email.com` (string, required)
          
              The user has to supply a valid email address.
          
  
negative.code: This method can be used to edit a user. If no `name` is supplied, the currently authenticated user is chosen as target. By using this method it is also possible to change the rank of users. Changing the rank as well as other users in general can only be done by admins (rank 100) though.
  
  + Parameters
      + name: `Namoshek` (string, optional) - The `username` of a user which is then taken as target for the operation
  
  + Request (application/json)
      + Headers
  