Get a user by userId in setlist.fm

What this operation does

Get a user by userId.

• GETReads data · /1.0/user/{userId}/1.0/user/{userId}

How HumDay uses it

1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
2. The contract names it. Before anything is built, you see exactly which setlist.fm operations the program may use, and this is one of them.
3. You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.

Other setlist.fm operations

• Get a complete list of all supported countriesGET · reads data
• Search for a cityGET · reads data
• Search for venuesGET · reads data
• Search for artistsGET · reads data
• Search for setlistsGET · reads data
• Get a city by its unique geoIdGET · reads data
• Get a venue by its unique idGET · reads data

All 15 setlist.fm operations

Questions

Can HumDay get a user by userid in setlist.fm?

Yes. This operation is published in setlist.fm's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.

Does this change anything in my setlist.fm account?

No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in setlist.fm.

Do I need to write code?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your setlist.fm account.

Where this came from

Read from a published API description for setlist.fm at api.setlist.fm/docs/1.0/ui/swagger.json. The description above is the provider’s own wording, not ours. Last published 2023-03-06.