Automate VocaDbWeb
HumDay reads VocaDbWeb’s own published API description and derives 127 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What HumDay can do in VocaDbWeb
53 documented operations change something in VocaDbWeb. The 49 most useful are listed here.
- DELETEDelete messages
/api/users/{id}/messages - POSTUpdate messages
/api/users/{id}/messages - POSTUpdate tags
/api/tags - POSTUpdate entryType comments
/api/comments/{entryType}-comments - POSTUpdate songLists
/api/songLists - POSTUpdate refreshEntryEdit
/api/users/current/refreshEntryEdit - POSTUpdate reports
/api/users/{id}/reports - POSTUpdate comments
/api/songs/{id}/comments - POSTUpdate comments
/api/albums/{id}/comments - POSTUpdate comments
/api/artists/{id}/comments - POSTUpdate comments
/api/tags/{tagId}/comments - DELETEDelete commentId
/api/tags/comments/{commentId} - POSTUpdate commentId
/api/tags/comments/{commentId} - DELETEDelete commentId
/api/songs/comments/{commentId} - POSTUpdate commentId
/api/songs/comments/{commentId} - POSTUpdate profileComments
/api/users/{id}/profileComments - DELETEDelete commentId
/api/albums/comments/{commentId} - POSTUpdate commentId
/api/albums/comments/{commentId} - POSTUpdate comments
/api/songLists/{listId}/comments - DELETEDelete commentId
/api/artists/comments/{commentId} - POSTUpdate commentId
/api/artists/comments/{commentId} - DELETEDelete commentId
/api/songLists/comments/{commentId} - POSTUpdate commentId
/api/songLists/comments/{commentId} - DELETEDelete commentId
/api/discussions/comments/{commentId} - POSTUpdate commentId
/api/discussions/comments/{commentId} - DELETEDelete commentId
/api/users/profileComments/{commentId} - POSTUpdate commentId
/api/users/profileComments/{commentId} - POSTUpdate folders
/api/discussions/folders - DELETEDelete id
/api/tags/{id} - DELETEDelete id
/api/songs/{id} - POSTUpdate albumId
/api/users/current/albums/{albumId} - DELETEDelete id
/api/albums/{id} - POSTUpdate songId
/api/users/current/songTags/{songId} - DELETEDelete id
/api/venues/{id} - DELETEDelete id
/api/artists/{id} - DELETEDelete id
/api/songLists/{id} - DELETEDelete tagId
/api/users/current/followedTags/{tagId} - POSTUpdate tagId
/api/users/current/followedTags/{tagId} - DELETEDelete commentId
/api/comments/{entryType}-comments/{commentId} - POSTUpdate commentId
/api/comments/{entryType}-comments/{commentId} - POSTUpdate comments
/api/discussions/topics/{topicId}/comments - DELETEDelete id
/api/releaseEvents/{id} - DELETEDelete id
/api/releaseEventSeries/{id} - POSTUpdate settingName
/api/users/{id}/settings/{settingName} - POSTUpdate ratings
/api/songs/{id}/ratings - POSTUpdate reviews
/api/albums/{id}/reviews - POSTUpdate reports
/api/venues/{id}/reports - POSTUpdate reports
/api/tags/{tagId}/reports - DELETEDelete topicId
/api/discussions/topics/{topicId}
What HumDay can read from VocaDbWeb
These are the operations a schedule or a trigger can watch.
- GETRead users
/api/users - GETRead comments
/api/comments - GETRead events
/api/users/{id}/events - GETRead messages
/api/users/{id}/messages - GETRead messageId
/api/users/messages/{messageId} - GETRead new
/api/albums/new - GETRead names
/api/users/names - GETRead current
/api/users/current - GETRead id
/api/users/{id} - GETRead tags
/api/tags - GETRead entryType comments
/api/comments/{entryType}-comments - GETRead songs
/api/songs - GETRead albums
/api/albums - GETRead venues
/api/venues - GETRead artists
/api/artists - GETRead entries
/api/entries - GETRead albums
/api/users/{id}/albums - GETRead releaseEvents
/api/releaseEvents - GETRead comments
/api/songs/{id}/comments - GETRead activityEntries
/api/activityEntries - GETRead comments
/api/albums/{id}/comments - GETRead songLists
/api/users/{id}/songLists - GETRead comments
/api/artists/{id}/comments - GETRead comments
/api/tags/{tagId}/comments - GETRead ratedSongs
/api/users/{id}/ratedSongs - GETRead releaseEventSeries
/api/releaseEventSeries - GETRead followedArtists
/api/users/{id}/followedArtists - GETRead profileComments
/api/users/{id}/profileComments - GETRead comments
/api/songLists/{listId}/comments - GETRead user collections
/api/albums/{id}/user-collections - GETRead top
/api/tags/top - GETRead top
/api/albums/top - GETRead byPv
/api/songs/byPv - GETRead names
/api/tags/names - GETRead names
/api/songs/names - GETRead names
/api/albums/names - GETRead names
/api/artists/names - GETRead names
/api/entries/names - GETRead for songs
/api/pvs/for-songs - GETRead top rated
/api/songs/top-rated - GETRead highlighted
/api/songs/highlighted - GETRead topics
/api/discussions/topics - GETRead featured
/api/songLists/featured - GETRead categoryNames
/api/tags/categoryNames - GETRead folders
/api/discussions/folders - GETRead names
/api/releaseEvents/names - GETRead id
/api/tags/{id} - GETRead id
/api/songs/{id} - GETRead id
/api/albums/{id} - GETRead id
/api/artists/{id} - GETRead songId
/api/users/current/ratedSongs/{songId}
How automating VocaDbWeb works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
- See it proven. The program runs and shows you the result before it is allowed near your live VocaDbWeb account.
- Grant access, then go live. You approve the specific VocaDbWeb operations it may use — and only those.
Automate VocaDbWeb with these
- Google Compute Engine694 operations
- Jellyfin379 operations
- OpenAI273 operations
- Evetech EVE Swagger Interface206 operations
- Google Campaign Manager 360205 operations
- Google Content for Shopping175 operations
- Google Display & Video 360151 operations
- Bungie.Net134 operations
- Google Admin SDK122 operations
- Google Apigee109 operations
- Shutterstock Explorer109 operations
- Wowza Streaming Cloud Reference Documentation100 operations
Categories
Questions about VocaDbWeb automation
- Can HumDay connect to VocaDbWeb?
- Yes. HumDay reads VocaDbWeb's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 127 operations are documented.
- Do I need to write code to automate VocaDbWeb?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your VocaDbWeb account.
- What can HumDay do in VocaDbWeb?
- 53 of the 127 documented operations change something in VocaDbWeb, and 74 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my VocaDbWeb account safe?
- Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to VocaDbWeb is held behind that approval.
Where this came from
The operations above are read from a published API description for VocaDbWeb at vocadb.net/swagger/v1/swagger.json. Descriptions are the provider’s own words, not ours. Last published 2023-03-08.