anchor.diff:  Returns a list of database entries. The result can be adjusted by additional, but optional parameters.
   
   + Parameters
  -    + organization (string, optional) - Only search within a given `organization` for entries
  -    + application (string, optional) - Only search within a given `application` for entries
  -    + scope (string, optional) - Only search within a given `scope` of an `application` for entries
  -    + offset (number, optional) - How many entries to skip for the output, can be used for pagination.
  +    + organization: `apache` (string, optional) - Only search within a given `organization` for entries
  +    + application: `tomcat` (string, optional) - Only search within a given `application` for entries
  +    + scope: `server.xml` (string, optional) - Only search within a given `scope` of an `application` for entries
  +    + offset: `0` (number, optional) - How many entries to skip for the output, can be used for pagination.
           + Default: `0`
  -    + rows (number, optional) - How many entries will be added to the output at max.
  +    + rows: `1` (number, optional) - How many entries will be added to the output at max.
           + Default: `200`
       + sort (enum[string], optional) - How to sort the entries for the output.
           + Default: `asc`
  
positive.code:             Authorization: Bearer <token>
  
      + Attributes (object)
          + organization: `org.apache` (string, required)
  
              The organization which built the software for which the configuration is meant.
  
              Regex: ^[a-zA-Z0-9\.\-]+$
  
          + application: `hive` (string, required)
  
              The application for which the configuration is meant.
  
              Regex: ^[a-zA-Z0-9\.\-]+$
  
          + scope: `database` (string, required)
  
              Often different parts of an application have different configurations. Here the application specific scope can be defined.
  
              Regex: ^[a-zA-Z0-9\.\-]+$
  
          + slug: `sample-snippet-for-devs` (string, required)
  
              A unique slug that identifies the entry and configuration snippet further. It only needs to be unique within the namespace created by `organization`, `application` and `scope`.
  
              Regex: ^[a-zA-Z0-9\.\-]+$
  
          + title: `Sample snippet for developers` (string, required)
  
              A title for the entry that ideally explains already what the snippet is about.
  
              Regex: ^[^\n\r]{3,}$
  
          + description: `This is a sample conf snippet for Apaches Hive database module.` (string, required)
  
              An extended description for the entry that explains in detail what the snippet is about. It can also contain instructions on how to use the snippet.
  
              Regex: ^[\S\s]{3,}$
  
          + tags: `dev`, `developer`, `db-dev` (array[string], optional)
  
              A list of tags that shall be added to the entry. Tags may be used for search, so they ideally add additional information that is not already available by the other inputs.
  
              Regex: ^[a-z0-9\-\.]{3,20}$
  
          + configuration (object)
              + value: `sampleKey = sampleValue` (string, required)
  
                  The configuration for which a new database entry should be created. It can be of any supported format, in this example **ini** is used.
  
              + format: `ini` (string, required)
  
                  The format of the supplied configuration snippet. It has to be in the list of supported formats, see `/conversion/formats`.
  
  
negative.code: 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: `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: `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: `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)
  