anchor.diff:  
   # ConCaVa API
   
  -The ConCaVa API allows you to configure ConCaVa metadata.
  -
  -TODO:
  -
  -- Users
  -    - GET /v1/users/login
  -        - ~~200~~
  -        - 401
  -    - ~~POST~~
  -        - ~~200~~
  -        - ~~400~~
  -- Templates
  -    - GET
  -    - POST
  -    - PUT
  -    - DELETE
  -- Attributes
  -    - GET
  -    - POST
  -    - PUT
  -    - DELETE
  -    - PUT /v1/attributes/reorder
  -- Devices
  -    - GET
  -    - POST
  -    - PUT
  -    - DELETE
  -- Filters
  -- Orders
  -- Includes
  +The ConCaVa API allows you to manage ConCaVa metadata.
  +
  +## Query parameters [/query-params]
  +
  +### Filtering [GET /v1/devices?filter=template_id:2]
  +
  +Use the `filter` query parameter. Use `key:value` pairs. Comma separated.
  +
  ++ Request
  +
  +    + Headers
  +            
  +            Authorization: Basic <base64 encoded <email>:<password>>
  +
  ++ Response 200 (application/json)
  +
  +        [
  +            {
  +                "id": 3,
  +                "template_id": 1,
  +                ...
  +            },
  +            {
  +                "id": 4,
  +                "template_id": 2,
  +                ...
  +            },
  +            {
  +                "id": 5,
  +                "template_id": 3,
  +                ...
  +            },
  +            ...
  +        }
  +
  +### Ordering [GET /v1/devices?order=name]
  +
  +Use the `order` query parameter. Comma separated.
  +For a descending order prefix with a dash, like: `-udid`.
  +
  ++ Request
  +
  +    + Headers
  +            
  +            Authorization: Basic <base64 encoded <email>:<password>>
  +
  ++ Response 200 (application/json)
  +
  +        [
  +            {
  +                "name": "Template A",
  +                "udid": "0000000000000001",
  +                ...
  +            },
  +            {
  +                "name": "Template B",
  +                "udid": "0000000000000002",
  +                ...
  +            },
  +            ...
  +        }
  +
  +### Including relationships [GET /v1/devices?include=template]
  +
  +Use the `include` query parameter. Comma separated.
  +Use dots for including sub relations, like: `template.attributes`.
  +
  ++ Request
  +
  +    + Headers
  +            
  +            Authorization: Basic <base64 encoded <email>:<password>>
  +
  ++ Response 200 (application/json)
  +
  +        {
  +            "id": 4,
  +            "udid": "0000000000000001",
  +            ...
  +            "template": {
  +                "id": 2,
  +                "user_id": 1,
  +                "name": "My Template",
  +                "created_at": "2016-07-12 15:21:05",
  +                "updated_at": "2016-07-12 15:21:05"
  +            }
  +        }
  +
  +## Error responses [/errors]
  +
  +General error responses that apply to all resources. These examples are for the devices.
  +
  +### Create Device [POST /v1/devices]
  +
  ++ Request (application/json)
  +
  +        {
  +            "name": "John Doe"
  +        }
  +        
  ++ Response 400 (application/json)
  +
  +        {
  +            "messages": {
  +                "email": ["The email field is required."],
  +                "password": ["The password field is required."]
  +            }
  +        }
  +
  +### Delete Device Of Other Account [DELETE /v1/devices/1]
  +
  ++ Request
  +
  +    + Headers
  +    
  +            Authorization: Token <token>
  +
  ++ Response 401 (application/json)
  +
  +        {
  +            "status": 401,
  +            "code": 0,
  +            "message": "Not allowed to delete entity."
  +        }
  +        
  +### Delete Non-Existing Device [DELETE /v1/devices/1234]
  +        
  ++ Request
  +
  +    + Headers
  +    
  +            Authorization: Token <token>
  +            
  ++ Response 404 (application/json)
  +
  +        {
  +            "status": 404,
  +            "code": 0,
  +            "message": "Entity not found."
  +        }
   
   ## Users [/v1/users]
  +
  +Relationships: `devices`, `templates`, and `tokens`.
   
   ### Log In User [GET /v1/users/login]
   
  
positive.code:             "created_at": "2016-07-12 14:41:48",
              "updated_at": "2016-07-12 14:41:48",
          }
  
  ### Register User [POST]
  
  
negative.code: + Response 200 (application/json)
  
          {
              "id": 1,
              "name": "John Doe",
              "email": "john@example.com",
              "is_active": true,
  