anchor.diff:      
               x-apikey : test_api_key
               x-apisecret : test_api_secret
  -            Authorization : gamer_id:gamer_secret
  +            Authorization : Basic gamer_id:gamer_secret
   
   + Response 200 
   
  ++ Request
  +
  +    + Headers
  +    
  +            x-apikey : test_api_key
  +            x-apisecret : test_api_secret
  +            Authorization : Basic INVALID GAMER IDENTITY
  +
   + Response 401
   
           {
  
positive.code: |gamervfs|json| list of key/value associated to the gamer
  |matches|json| array of match currently in open state of the gamer
  
  ### Login [POST]
  
  + Request (application/json)
  
      + Headers
  
negative.code: 
  ## How Login works [/v1/gamer/login]
  
  The login route is used to authenticate a gamer, and get basic profile information about him.
  
  **Note:** If an existing gamer can't be found, a new one is created and returned.
  
  Login for authenticated gamers will use one of these authentication methods : 
  
  * Facebook Connect: use the `ID` and the `oauth token` from Facebook
  
  * Google+ Sign-in: use the `ID` and the `oauth token` from Google+
  
  * RAW: use the `gamer_id` and the `gamer_secret` from a previous login
  
  
  
  ### After login
  
  After login has been called, HTTP Basic Authentication will be used to authenticate every request.
  
  |Header     |               |
  |---        |---            |
  |x-apikey   |Your API key   |
  |x-apisecret|Your API secret|
  |Authorization| Basic `gamer_id:gamer_secret` base64 encoded|
  
  Both `gamer_id` and `gamer_secret` are returned by `/v1/gamer/login`.
  
  It is your responsibility to store these to help the user log in later (in RAW mode).
  
  
  ### Login [POST]
  
  ### Body description
  
  A JSON object must be sent in the request body with the following structure.
  
  