setlist.fm /1.0/user/{userId} API

swagger: '2.0'
info:
  description: '<p>

    The setlist.fm API has been designed to give you easy access to setlist data in order to build fancy websites and

    other applications. Before starting to use the API, be sure to ...

    <ol>

    <li>... understand how setlist.fm works (the <a href="https://www.setlist.fm/faq">FAQ</a> and the

    <a href="https://www.setlist.fm/guidelines">Guidelines</a> are a good starting point),</li>

    <li>... read this documentation carefully and</li>

    <li>... <a href="https://www.setlist.fm/settings/api">apply for an API key</a> (link for logged in users only) - if

    you''re no registered user yet, then <a href="https://www.setlist.fm/signup">register first</a> (it''s free).</li>

    </ol>

    </p>

    <p>

    If this documentation isn''t enough or if you''ve got other things you''d like to tell us about the API, visit the

    <a href="https://www.setlist.fm/forum/setlistfm/setlistfm-api">API Forum</a>.

    </p>

    <p>

    Note that the setlist.fm API is, according to the <a href="https://www.setlist.fm/help/api-terms">API terms of

    service</a>, only free for non-commercial projects. If you''re interested in using the API for commercial purposes,

    <a href="https://www.setlist.fm/contact">contact us</a>.

    </p>


    <h2>About this Service</h2>

    <p>

    This service provides methods to get both setlists and components of setlists such as artists, cities, countries or

    venues.

    </p>


    <h2>Supported Content Types</h2>

    <p>

    The REST service currently supports XML (default) and JSON content.

    </p>

    <p>

    To receive a JSON response, set the <code>Accept</code>

    <a href="https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.1">header</a> to <em>application/json</em>.

    </p>


    <h2>Internationalization</h2>

    <p>

    <small>(Please note that this is an experimental feature and does not work for all cities!)</small>

    </p>

    <p>

    Most of the featured methods honor the <code>Accept-Language</code>

    <a href="https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.4">header</a>. This header is used for

    localizing cities and countries. The default language is English (en), but you can provide any of the languages

    Spanish (es), French (fr), German (de), Portuguese (pt), Turkish (tr), Italian (it) or Polish (pl).

    </p>

    <p>

    E.g. if you search a setlist for a concert that took place in Vienna and you pass &quot;de&quot; as header, you''ll

    get <em>&quot;Wien, &Ouml;sterreich&quot;</em> instead of <em>&quot;Vienna, Austria&quot;</em>.<br/>

    This also works if you use a different language than the country''s native language.

    </p>

    <p>

    E.g. for a concert in New York, you''ll get <em>&quot;Nueva York, Estados Unidos&quot;</em> instead of <em>&quot;New

    York, United States&quot;</em> if you pass &quot;es&quot; as language.

    </p>


    <h2>API Keys</h2>


    API keys (<a href="https://www.setlist.fm/settings/api">application form</a>) must be included in the request with

    the <code>x-api-key</code> header.


    <h2>Version History</h2>

    <table class="table table-bordered table-versions">

    <thead>

    <tr>

    <th>Version</th>

    <th>Docs</th>

    <th>End of Service</th>

    </tr>

    </thead> <tbody>

    <tr>

    <td><strong>1.0</strong></td>

    <td><a href="/docs/1.0">Docs</a></td>

    <td>-</li>

    </tr>

    <tr>

    <td><strong>0.1</strong></td>

    <td></td>

    <td>December 31, 2017</li>

    </tr>

    </tbody>

    </table>'
  version: '1.0'
  title: setlist.fm /1.0/artist/{mbid} /1.0/artist/{mbid} /1.0/user/{userId} API
basePath: /rest
schemes: []
tags:
- name: /1.0/user/{userId}
paths:
  /1.0/user/{userId}:
    get:
      tags:
      - /1.0/user/{userId}
      summary: Get a user by userId.
      description: 'Get a user by userId. (deprecated)


        Note: This endpoint always returns a result, even if the user doesn''t exist'
      operationId: resource__1.0_user__userId__getUser_GET
      produces:
      - application/xml
      - application/json
      parameters:
      - name: userId
        in: path
        required: true
        type: string
        description: the user's userId
      responses:
        '200':
          schema:
            description: ''
            $ref: '#/definitions/json_User'
          headers: {}
          examples:
            application/json:
              userId: '...'
              fullname: '...'
              lastFm: '...'
              mySpace: '...'
              twitter: '...'
              flickr: '...'
              website: '...'
              about: '...'
              url: '...'
          description: Success
definitions:
  json_User:
    type: object
    title: user
    properties:
      userId:
        description: ''
        type: string
      fullname:
        description: never set (deprecated)
        type: string
      lastFm:
        description: never set (deprecated)
        type: string
      mySpace:
        description: never set (deprecated)
        type: string
      twitter:
        description: never set (deprecated)
        type: string
      flickr:
        description: never set (deprecated)
        type: string
      website:
        description: never set (deprecated)
        type: string
      about:
        description: never set (deprecated)
        type: string
      url:
        description: ''
        type: string
    example:
      userId: '...'
      fullname: '...'
      lastFm: '...'
      mySpace: '...'
      twitter: '...'
      flickr: '...'
      website: '...'
      about: '...'
      url: '...'
    description: This class represents a user.