songtradr_api_client_ruby 1.13.5 → 1.13.6

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (250) hide show
  1. checksums.yaml +4 -4
  2. data/Gemfile.lock +1 -1
  3. data/README.md +12 -36
  4. data/docs/FileSmallDTO.md +5 -5
  5. data/docs/MusicalFeaturesDTO.md +27 -27
  6. data/docs/PlaylistLargeDTO.md +2 -2
  7. data/docs/RecordingGenrePredictionDTO.md +3 -3
  8. data/docs/RecordingLargeDTO.md +2 -2
  9. data/docs/RecordingMediumDTO.md +2 -2
  10. data/docs/RecordingMinimalWithMusicalFeaturesDTO.md +3 -3
  11. data/docs/RecordingSmallDTO.md +3 -3
  12. data/docs/TagDTO.md +3 -3
  13. data/lib/songtradr_api_client_ruby/api/allowed_values_api.rb +1 -1
  14. data/lib/songtradr_api_client_ruby/api/party_api.rb +1 -1
  15. data/lib/songtradr_api_client_ruby/api/playlist_api.rb +1 -1
  16. data/lib/songtradr_api_client_ruby/api/recording_api.rb +1 -1
  17. data/lib/songtradr_api_client_ruby/api/user_api.rb +1 -1
  18. data/lib/songtradr_api_client_ruby/api_client.rb +1 -1
  19. data/lib/songtradr_api_client_ruby/api_error.rb +1 -1
  20. data/lib/songtradr_api_client_ruby/configuration.rb +1 -1
  21. data/lib/songtradr_api_client_ruby/models/age_range.rb +1 -1
  22. data/lib/songtradr_api_client_ruby/models/beard.rb +1 -1
  23. data/lib/songtradr_api_client_ruby/models/bounding_box.rb +1 -1
  24. data/lib/songtradr_api_client_ruby/models/category_medium_dto.rb +1 -1
  25. data/lib/songtradr_api_client_ruby/models/category_minimal_dto.rb +1 -1
  26. data/lib/songtradr_api_client_ruby/models/config_access_dto.rb +1 -1
  27. data/lib/songtradr_api_client_ruby/models/config_identifier_dto.rb +1 -1
  28. data/lib/songtradr_api_client_ruby/models/context_value.rb +1 -1
  29. data/lib/songtradr_api_client_ruby/models/contributor_type_dto.rb +1 -1
  30. data/lib/songtradr_api_client_ruby/models/curate_playlist_dto.rb +1 -1
  31. data/lib/songtradr_api_client_ruby/models/curate_playlist_response_dto.rb +1 -1
  32. data/lib/songtradr_api_client_ruby/models/dominant_color.rb +1 -1
  33. data/lib/songtradr_api_client_ruby/models/emotion.rb +1 -1
  34. data/lib/songtradr_api_client_ruby/models/error_response.rb +1 -1
  35. data/lib/songtradr_api_client_ruby/models/eye_direction.rb +1 -1
  36. data/lib/songtradr_api_client_ruby/models/eye_open.rb +1 -1
  37. data/lib/songtradr_api_client_ruby/models/eyeglasses.rb +1 -1
  38. data/lib/songtradr_api_client_ruby/models/face_detail.rb +1 -1
  39. data/lib/songtradr_api_client_ruby/models/face_detection.rb +1 -1
  40. data/lib/songtradr_api_client_ruby/models/face_occluded.rb +1 -1
  41. data/lib/songtradr_api_client_ruby/models/field_summary_dto.rb +1 -1
  42. data/lib/songtradr_api_client_ruby/models/file_dto.rb +1 -1
  43. data/lib/songtradr_api_client_ruby/models/file_list_dto.rb +1 -1
  44. data/lib/songtradr_api_client_ruby/models/file_minimal_with_url_dto.rb +1 -1
  45. data/lib/songtradr_api_client_ruby/models/file_small_dto.rb +36 -36
  46. data/lib/songtradr_api_client_ruby/models/file_upload_dto.rb +1 -1
  47. data/lib/songtradr_api_client_ruby/models/file_w_ith_url_dto.rb +1 -1
  48. data/lib/songtradr_api_client_ruby/models/files_summary_dto.rb +1 -1
  49. data/lib/songtradr_api_client_ruby/models/forgot_password_dto.rb +1 -1
  50. data/lib/songtradr_api_client_ruby/models/gender.rb +1 -1
  51. data/lib/songtradr_api_client_ruby/models/genre_dto.rb +1 -1
  52. data/lib/songtradr_api_client_ruby/models/genre_minimal_dto.rb +1 -1
  53. data/lib/songtradr_api_client_ruby/models/genres_summary_dto.rb +1 -1
  54. data/lib/songtradr_api_client_ruby/models/image_quality.rb +1 -1
  55. data/lib/songtradr_api_client_ruby/models/image_recognition_response.rb +1 -1
  56. data/lib/songtradr_api_client_ruby/models/init_put_recording_audio_dto.rb +1 -1
  57. data/lib/songtradr_api_client_ruby/models/instance.rb +1 -1
  58. data/lib/songtradr_api_client_ruby/models/jwt_token_dto.rb +1 -1
  59. data/lib/songtradr_api_client_ruby/models/label.rb +1 -1
  60. data/lib/songtradr_api_client_ruby/models/label_alias.rb +1 -1
  61. data/lib/songtradr_api_client_ruby/models/label_category.rb +1 -1
  62. data/lib/songtradr_api_client_ruby/models/label_detection.rb +1 -1
  63. data/lib/songtradr_api_client_ruby/models/landmark.rb +1 -1
  64. data/lib/songtradr_api_client_ruby/models/login_dto.rb +1 -1
  65. data/lib/songtradr_api_client_ruby/models/mouth_open.rb +1 -1
  66. data/lib/songtradr_api_client_ruby/models/musical_features_dto.rb +172 -172
  67. data/lib/songtradr_api_client_ruby/models/mustache.rb +1 -1
  68. data/lib/songtradr_api_client_ruby/models/p_line_dto.rb +1 -1
  69. data/lib/songtradr_api_client_ruby/models/parent.rb +1 -1
  70. data/lib/songtradr_api_client_ruby/models/party_large_dto.rb +1 -1
  71. data/lib/songtradr_api_client_ruby/models/party_small_dto.rb +1 -1
  72. data/lib/songtradr_api_client_ruby/models/playlist_large_dto.rb +11 -11
  73. data/lib/songtradr_api_client_ruby/models/pose.rb +1 -1
  74. data/lib/songtradr_api_client_ruby/models/product_medium_dto.rb +1 -1
  75. data/lib/songtradr_api_client_ruby/models/product_party_dto.rb +1 -1
  76. data/lib/songtradr_api_client_ruby/models/recording_for_similarity_search_dto.rb +1 -1
  77. data/lib/songtradr_api_client_ruby/models/recording_genre_prediction_dto.rb +21 -21
  78. data/lib/songtradr_api_client_ruby/models/recording_large_dto.rb +13 -13
  79. data/lib/songtradr_api_client_ruby/models/recording_list_dto.rb +1 -1
  80. data/lib/songtradr_api_client_ruby/models/recording_medium_dto.rb +13 -13
  81. data/lib/songtradr_api_client_ruby/models/recording_minimal_with_musical_features_dto.rb +16 -16
  82. data/lib/songtradr_api_client_ruby/models/recording_minimal_with_taggrams_dto.rb +1 -1
  83. data/lib/songtradr_api_client_ruby/models/recording_minimal_with_tagstrengths_dto.rb +1 -1
  84. data/lib/songtradr_api_client_ruby/models/recording_party_dto.rb +1 -1
  85. data/lib/songtradr_api_client_ruby/models/recording_playlist_dto.rb +1 -1
  86. data/lib/songtradr_api_client_ruby/models/recording_small_dto.rb +16 -16
  87. data/lib/songtradr_api_client_ruby/models/recording_tag_small_dto.rb +1 -1
  88. data/lib/songtradr_api_client_ruby/models/save_file_recording_dto.rb +1 -1
  89. data/lib/songtradr_api_client_ruby/models/save_playlist_dto.rb +1 -1
  90. data/lib/songtradr_api_client_ruby/models/save_recording_genre_dto.rb +1 -1
  91. data/lib/songtradr_api_client_ruby/models/save_recording_party_dto.rb +1 -1
  92. data/lib/songtradr_api_client_ruby/models/save_recording_playlist_dto.rb +1 -1
  93. data/lib/songtradr_api_client_ruby/models/save_recording_tag_dto.rb +1 -1
  94. data/lib/songtradr_api_client_ruby/models/save_referrer_dto.rb +1 -1
  95. data/lib/songtradr_api_client_ruby/models/save_taggrams_dto.rb +1 -1
  96. data/lib/songtradr_api_client_ruby/models/save_user_dto.rb +1 -1
  97. data/lib/songtradr_api_client_ruby/models/search_filter_values_dto.rb +1 -1
  98. data/lib/songtradr_api_client_ruby/models/search_recording_granular_abstraction_dto.rb +1 -1
  99. data/lib/songtradr_api_client_ruby/models/search_recording_granular_dto.rb +1 -1
  100. data/lib/songtradr_api_client_ruby/models/sign_up_dto.rb +1 -1
  101. data/lib/songtradr_api_client_ruby/models/smile.rb +1 -1
  102. data/lib/songtradr_api_client_ruby/models/sunglasses.rb +1 -1
  103. data/lib/songtradr_api_client_ruby/models/tag_dto.rb +16 -16
  104. data/lib/songtradr_api_client_ruby/models/tag_small_dto.rb +1 -1
  105. data/lib/songtradr_api_client_ruby/models/taggram_dto.rb +1 -1
  106. data/lib/songtradr_api_client_ruby/models/tags_summary_dto.rb +1 -1
  107. data/lib/songtradr_api_client_ruby/models/tagstrength_dto.rb +1 -1
  108. data/lib/songtradr_api_client_ruby/models/title_dto.rb +1 -1
  109. data/lib/songtradr_api_client_ruby/models/token_request.rb +1 -1
  110. data/lib/songtradr_api_client_ruby/models/track_dto.rb +1 -1
  111. data/lib/songtradr_api_client_ruby/models/track_to_medium_product_dto.rb +1 -1
  112. data/lib/songtradr_api_client_ruby/models/update_password_dto.rb +1 -1
  113. data/lib/songtradr_api_client_ruby/models/usage_dto.rb +1 -1
  114. data/lib/songtradr_api_client_ruby/models/user_dto.rb +1 -1
  115. data/lib/songtradr_api_client_ruby/models/video_recognition_response.rb +1 -1
  116. data/lib/songtradr_api_client_ruby/version.rb +2 -2
  117. data/lib/songtradr_api_client_ruby.rb +1 -10
  118. data/openapi-generator-config.yaml +1 -1
  119. data/songtradr_api_client_ruby.gemspec +1 -1
  120. data/spec/api/allowed_values_api_spec.rb +1 -1
  121. data/spec/api/party_api_spec.rb +1 -1
  122. data/spec/api/playlist_api_spec.rb +1 -1
  123. data/spec/api/recording_api_spec.rb +1 -1
  124. data/spec/api/user_api_spec.rb +1 -1
  125. data/spec/api_client_spec.rb +1 -1
  126. data/spec/configuration_spec.rb +1 -1
  127. data/spec/models/age_range_spec.rb +1 -1
  128. data/spec/models/beard_spec.rb +1 -1
  129. data/spec/models/bounding_box_spec.rb +1 -1
  130. data/spec/models/category_medium_dto_spec.rb +1 -1
  131. data/spec/models/category_minimal_dto_spec.rb +1 -1
  132. data/spec/models/config_access_dto_spec.rb +1 -1
  133. data/spec/models/config_identifier_dto_spec.rb +1 -1
  134. data/spec/models/context_value_spec.rb +1 -1
  135. data/spec/models/contributor_type_dto_spec.rb +1 -1
  136. data/spec/models/curate_playlist_dto_spec.rb +1 -1
  137. data/spec/models/curate_playlist_response_dto_spec.rb +1 -1
  138. data/spec/models/dominant_color_spec.rb +1 -1
  139. data/spec/models/emotion_spec.rb +1 -1
  140. data/spec/models/error_response_spec.rb +1 -1
  141. data/spec/models/eye_direction_spec.rb +1 -1
  142. data/spec/models/eye_open_spec.rb +1 -1
  143. data/spec/models/eyeglasses_spec.rb +1 -1
  144. data/spec/models/face_detail_spec.rb +1 -1
  145. data/spec/models/face_detection_spec.rb +1 -1
  146. data/spec/models/face_occluded_spec.rb +1 -1
  147. data/spec/models/field_summary_dto_spec.rb +1 -1
  148. data/spec/models/file_dto_spec.rb +1 -1
  149. data/spec/models/file_list_dto_spec.rb +1 -1
  150. data/spec/models/file_minimal_with_url_dto_spec.rb +1 -1
  151. data/spec/models/file_small_dto_spec.rb +17 -17
  152. data/spec/models/file_upload_dto_spec.rb +1 -1
  153. data/spec/models/file_w_ith_url_dto_spec.rb +1 -1
  154. data/spec/models/files_summary_dto_spec.rb +1 -1
  155. data/spec/models/forgot_password_dto_spec.rb +1 -1
  156. data/spec/models/gender_spec.rb +1 -1
  157. data/spec/models/genre_dto_spec.rb +1 -1
  158. data/spec/models/genre_minimal_dto_spec.rb +1 -1
  159. data/spec/models/genres_summary_dto_spec.rb +1 -1
  160. data/spec/models/image_quality_spec.rb +1 -1
  161. data/spec/models/image_recognition_response_spec.rb +1 -1
  162. data/spec/models/init_put_recording_audio_dto_spec.rb +1 -1
  163. data/spec/models/instance_spec.rb +1 -1
  164. data/spec/models/jwt_token_dto_spec.rb +1 -1
  165. data/spec/models/label_alias_spec.rb +1 -1
  166. data/spec/models/label_category_spec.rb +1 -1
  167. data/spec/models/label_detection_spec.rb +1 -1
  168. data/spec/models/label_spec.rb +1 -1
  169. data/spec/models/landmark_spec.rb +1 -1
  170. data/spec/models/login_dto_spec.rb +1 -1
  171. data/spec/models/mouth_open_spec.rb +1 -1
  172. data/spec/models/musical_features_dto_spec.rb +57 -57
  173. data/spec/models/mustache_spec.rb +1 -1
  174. data/spec/models/p_line_dto_spec.rb +1 -1
  175. data/spec/models/parent_spec.rb +1 -1
  176. data/spec/models/party_large_dto_spec.rb +1 -1
  177. data/spec/models/party_small_dto_spec.rb +1 -1
  178. data/spec/models/playlist_large_dto_spec.rb +7 -7
  179. data/spec/models/pose_spec.rb +1 -1
  180. data/spec/models/product_medium_dto_spec.rb +1 -1
  181. data/spec/models/product_party_dto_spec.rb +1 -1
  182. data/spec/models/recording_for_similarity_search_dto_spec.rb +1 -1
  183. data/spec/models/recording_genre_prediction_dto_spec.rb +4 -4
  184. data/spec/models/recording_large_dto_spec.rb +7 -7
  185. data/spec/models/recording_list_dto_spec.rb +1 -1
  186. data/spec/models/recording_medium_dto_spec.rb +7 -7
  187. data/spec/models/recording_minimal_with_musical_features_dto_spec.rb +3 -3
  188. data/spec/models/recording_minimal_with_taggrams_dto_spec.rb +1 -1
  189. data/spec/models/recording_minimal_with_tagstrengths_dto_spec.rb +1 -1
  190. data/spec/models/recording_party_dto_spec.rb +1 -1
  191. data/spec/models/recording_playlist_dto_spec.rb +1 -1
  192. data/spec/models/recording_small_dto_spec.rb +4 -4
  193. data/spec/models/recording_tag_small_dto_spec.rb +1 -1
  194. data/spec/models/save_file_recording_dto_spec.rb +1 -1
  195. data/spec/models/save_playlist_dto_spec.rb +1 -1
  196. data/spec/models/save_recording_genre_dto_spec.rb +1 -1
  197. data/spec/models/save_recording_party_dto_spec.rb +1 -1
  198. data/spec/models/save_recording_playlist_dto_spec.rb +1 -1
  199. data/spec/models/save_recording_tag_dto_spec.rb +1 -1
  200. data/spec/models/save_referrer_dto_spec.rb +1 -1
  201. data/spec/models/save_taggrams_dto_spec.rb +1 -1
  202. data/spec/models/save_user_dto_spec.rb +1 -1
  203. data/spec/models/search_filter_values_dto_spec.rb +1 -1
  204. data/spec/models/search_recording_granular_abstraction_dto_spec.rb +1 -1
  205. data/spec/models/search_recording_granular_dto_spec.rb +1 -1
  206. data/spec/models/sign_up_dto_spec.rb +1 -1
  207. data/spec/models/smile_spec.rb +1 -1
  208. data/spec/models/sunglasses_spec.rb +1 -1
  209. data/spec/models/tag_dto_spec.rb +3 -3
  210. data/spec/models/tag_small_dto_spec.rb +1 -1
  211. data/spec/models/taggram_dto_spec.rb +1 -1
  212. data/spec/models/tags_summary_dto_spec.rb +1 -1
  213. data/spec/models/tagstrength_dto_spec.rb +1 -1
  214. data/spec/models/title_dto_spec.rb +1 -1
  215. data/spec/models/token_request_spec.rb +1 -1
  216. data/spec/models/track_dto_spec.rb +1 -1
  217. data/spec/models/track_to_medium_product_dto_spec.rb +1 -1
  218. data/spec/models/update_password_dto_spec.rb +1 -1
  219. data/spec/models/usage_dto_spec.rb +1 -1
  220. data/spec/models/user_dto_spec.rb +1 -1
  221. data/spec/models/video_recognition_response_spec.rb +1 -1
  222. data/spec/spec_helper.rb +1 -1
  223. metadata +1 -37
  224. data/docs/APIKeysApi.md +0 -217
  225. data/docs/AdminApiCreateUserDTO.md +0 -76
  226. data/docs/AdminApiUpdateUserDTO.md +0 -76
  227. data/docs/AdminApiUserDTO.md +0 -70
  228. data/docs/AdminUsersControllerApi.md +0 -355
  229. data/docs/ApiKeyDTO.md +0 -24
  230. data/docs/CreateApiKeyDTO.md +0 -18
  231. data/docs/InternalApiApi.md +0 -149
  232. data/docs/SaveFileDTO.md +0 -42
  233. data/lib/songtradr_api_client_ruby/api/admin_users_controller_api.rb +0 -346
  234. data/lib/songtradr_api_client_ruby/api/api_keys_api.rb +0 -213
  235. data/lib/songtradr_api_client_ruby/api/internal_api_api.rb +0 -169
  236. data/lib/songtradr_api_client_ruby/models/admin_api_create_user_dto.rb +0 -489
  237. data/lib/songtradr_api_client_ruby/models/admin_api_update_user_dto.rb +0 -475
  238. data/lib/songtradr_api_client_ruby/models/admin_api_user_dto.rb +0 -448
  239. data/lib/songtradr_api_client_ruby/models/api_key_dto.rb +0 -262
  240. data/lib/songtradr_api_client_ruby/models/create_api_key_dto.rb +0 -214
  241. data/lib/songtradr_api_client_ruby/models/save_file_dto.rb +0 -323
  242. data/spec/api/admin_users_controller_api_spec.rb +0 -93
  243. data/spec/api/api_keys_api_spec.rb +0 -70
  244. data/spec/api/internal_api_api_spec.rb +0 -58
  245. data/spec/models/admin_api_create_user_dto_spec.rb +0 -210
  246. data/spec/models/admin_api_update_user_dto_spec.rb +0 -210
  247. data/spec/models/admin_api_user_dto_spec.rb +0 -192
  248. data/spec/models/api_key_dto_spec.rb +0 -54
  249. data/spec/models/create_api_key_dto_spec.rb +0 -36
  250. data/spec/models/save_file_dto_spec.rb +0 -108
@@ -3,7 +3,7 @@
3
3
 
4
4
  #This is the Songtradr API. Use it to retrieve deep music metadata and trigger processes like auto-tagging. You can also use the API to manage your account and musicube cloud data. **Authentication** 1. Reach out to support@songtradr.com to receive a free account or use your login data if you are already signed up. 2. To authenticate, you need to login via the POST /api/v1/user/login endpoint. 3. The endpoint responds with a jwtToken which you can use in all following API requests as a bearer token. **Rate Limiting** The current limit is 120 Requests per minute. Reach out to us via support@songtradr.com if you need to request more. **Getting Started with auto-tagging** 1. If you want to get your own files auto-tagged, use the POST /api/v1/user/file/{name}/initUpload endpoint. It responds with a presigned S3 link where you can upload your file. 2. You can check the processing status of your file via the GET /api/v1/user/file/{name}/filesStatus endpoint. 3. As soon as processing is done, you can request the generated data via the GET /api/v1/user/files endpoint. **Getting Started with search** You can either search the released music via the /public/recording endpoints or your own private uploaded music via the /user/file/ endpoints. 1. If you want to search the world's released music, a good starting point is the GET /api/v1/public/recording/search endpoint. Please find the extensive list of parameters that serve as semantic search filters. 2. If you want to search your own previously uploaded music, a good starting point is the GET GET /api/v1/user/files endpoint. It has the same extensive list of parameters that serve as semantic search filters.
5
5
 
6
- The version of the OpenAPI document: 1.13.5
6
+ The version of the OpenAPI document: 1.13.6
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 7.1.0-SNAPSHOT
@@ -3,7 +3,7 @@
3
3
 
4
4
  #This is the Songtradr API. Use it to retrieve deep music metadata and trigger processes like auto-tagging. You can also use the API to manage your account and musicube cloud data. **Authentication** 1. Reach out to support@songtradr.com to receive a free account or use your login data if you are already signed up. 2. To authenticate, you need to login via the POST /api/v1/user/login endpoint. 3. The endpoint responds with a jwtToken which you can use in all following API requests as a bearer token. **Rate Limiting** The current limit is 120 Requests per minute. Reach out to us via support@songtradr.com if you need to request more. **Getting Started with auto-tagging** 1. If you want to get your own files auto-tagged, use the POST /api/v1/user/file/{name}/initUpload endpoint. It responds with a presigned S3 link where you can upload your file. 2. You can check the processing status of your file via the GET /api/v1/user/file/{name}/filesStatus endpoint. 3. As soon as processing is done, you can request the generated data via the GET /api/v1/user/files endpoint. **Getting Started with search** You can either search the released music via the /public/recording endpoints or your own private uploaded music via the /user/file/ endpoints. 1. If you want to search the world's released music, a good starting point is the GET /api/v1/public/recording/search endpoint. Please find the extensive list of parameters that serve as semantic search filters. 2. If you want to search your own previously uploaded music, a good starting point is the GET GET /api/v1/user/files endpoint. It has the same extensive list of parameters that serve as semantic search filters.
5
5
 
6
- The version of the OpenAPI document: 1.13.5
6
+ The version of the OpenAPI document: 1.13.6
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 7.1.0-SNAPSHOT
@@ -3,7 +3,7 @@
3
3
 
4
4
  #This is the Songtradr API. Use it to retrieve deep music metadata and trigger processes like auto-tagging. You can also use the API to manage your account and musicube cloud data. **Authentication** 1. Reach out to support@songtradr.com to receive a free account or use your login data if you are already signed up. 2. To authenticate, you need to login via the POST /api/v1/user/login endpoint. 3. The endpoint responds with a jwtToken which you can use in all following API requests as a bearer token. **Rate Limiting** The current limit is 120 Requests per minute. Reach out to us via support@songtradr.com if you need to request more. **Getting Started with auto-tagging** 1. If you want to get your own files auto-tagged, use the POST /api/v1/user/file/{name}/initUpload endpoint. It responds with a presigned S3 link where you can upload your file. 2. You can check the processing status of your file via the GET /api/v1/user/file/{name}/filesStatus endpoint. 3. As soon as processing is done, you can request the generated data via the GET /api/v1/user/files endpoint. **Getting Started with search** You can either search the released music via the /public/recording endpoints or your own private uploaded music via the /user/file/ endpoints. 1. If you want to search the world's released music, a good starting point is the GET /api/v1/public/recording/search endpoint. Please find the extensive list of parameters that serve as semantic search filters. 2. If you want to search your own previously uploaded music, a good starting point is the GET GET /api/v1/user/files endpoint. It has the same extensive list of parameters that serve as semantic search filters.
5
5
 
6
- The version of the OpenAPI document: 1.13.5
6
+ The version of the OpenAPI document: 1.13.6
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 7.1.0-SNAPSHOT
@@ -3,7 +3,7 @@
3
3
 
4
4
  #This is the Songtradr API. Use it to retrieve deep music metadata and trigger processes like auto-tagging. You can also use the API to manage your account and musicube cloud data. **Authentication** 1. Reach out to support@songtradr.com to receive a free account or use your login data if you are already signed up. 2. To authenticate, you need to login via the POST /api/v1/user/login endpoint. 3. The endpoint responds with a jwtToken which you can use in all following API requests as a bearer token. **Rate Limiting** The current limit is 120 Requests per minute. Reach out to us via support@songtradr.com if you need to request more. **Getting Started with auto-tagging** 1. If you want to get your own files auto-tagged, use the POST /api/v1/user/file/{name}/initUpload endpoint. It responds with a presigned S3 link where you can upload your file. 2. You can check the processing status of your file via the GET /api/v1/user/file/{name}/filesStatus endpoint. 3. As soon as processing is done, you can request the generated data via the GET /api/v1/user/files endpoint. **Getting Started with search** You can either search the released music via the /public/recording endpoints or your own private uploaded music via the /user/file/ endpoints. 1. If you want to search the world's released music, a good starting point is the GET /api/v1/public/recording/search endpoint. Please find the extensive list of parameters that serve as semantic search filters. 2. If you want to search your own previously uploaded music, a good starting point is the GET GET /api/v1/user/files endpoint. It has the same extensive list of parameters that serve as semantic search filters.
5
5
 
6
- The version of the OpenAPI document: 1.13.5
6
+ The version of the OpenAPI document: 1.13.6
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 7.1.0-SNAPSHOT
@@ -3,7 +3,7 @@
3
3
 
4
4
  #This is the Songtradr API. Use it to retrieve deep music metadata and trigger processes like auto-tagging. You can also use the API to manage your account and musicube cloud data. **Authentication** 1. Reach out to support@songtradr.com to receive a free account or use your login data if you are already signed up. 2. To authenticate, you need to login via the POST /api/v1/user/login endpoint. 3. The endpoint responds with a jwtToken which you can use in all following API requests as a bearer token. **Rate Limiting** The current limit is 120 Requests per minute. Reach out to us via support@songtradr.com if you need to request more. **Getting Started with auto-tagging** 1. If you want to get your own files auto-tagged, use the POST /api/v1/user/file/{name}/initUpload endpoint. It responds with a presigned S3 link where you can upload your file. 2. You can check the processing status of your file via the GET /api/v1/user/file/{name}/filesStatus endpoint. 3. As soon as processing is done, you can request the generated data via the GET /api/v1/user/files endpoint. **Getting Started with search** You can either search the released music via the /public/recording endpoints or your own private uploaded music via the /user/file/ endpoints. 1. If you want to search the world's released music, a good starting point is the GET /api/v1/public/recording/search endpoint. Please find the extensive list of parameters that serve as semantic search filters. 2. If you want to search your own previously uploaded music, a good starting point is the GET GET /api/v1/user/files endpoint. It has the same extensive list of parameters that serve as semantic search filters.
5
5
 
6
- The version of the OpenAPI document: 1.13.5
6
+ The version of the OpenAPI document: 1.13.6
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 7.1.0-SNAPSHOT
@@ -3,7 +3,7 @@
3
3
 
4
4
  #This is the Songtradr API. Use it to retrieve deep music metadata and trigger processes like auto-tagging. You can also use the API to manage your account and musicube cloud data. **Authentication** 1. Reach out to support@songtradr.com to receive a free account or use your login data if you are already signed up. 2. To authenticate, you need to login via the POST /api/v1/user/login endpoint. 3. The endpoint responds with a jwtToken which you can use in all following API requests as a bearer token. **Rate Limiting** The current limit is 120 Requests per minute. Reach out to us via support@songtradr.com if you need to request more. **Getting Started with auto-tagging** 1. If you want to get your own files auto-tagged, use the POST /api/v1/user/file/{name}/initUpload endpoint. It responds with a presigned S3 link where you can upload your file. 2. You can check the processing status of your file via the GET /api/v1/user/file/{name}/filesStatus endpoint. 3. As soon as processing is done, you can request the generated data via the GET /api/v1/user/files endpoint. **Getting Started with search** You can either search the released music via the /public/recording endpoints or your own private uploaded music via the /user/file/ endpoints. 1. If you want to search the world's released music, a good starting point is the GET /api/v1/public/recording/search endpoint. Please find the extensive list of parameters that serve as semantic search filters. 2. If you want to search your own previously uploaded music, a good starting point is the GET GET /api/v1/user/files endpoint. It has the same extensive list of parameters that serve as semantic search filters.
5
5
 
6
- The version of the OpenAPI document: 1.13.5
6
+ The version of the OpenAPI document: 1.13.6
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 7.1.0-SNAPSHOT
@@ -3,7 +3,7 @@
3
3
 
4
4
  #This is the Songtradr API. Use it to retrieve deep music metadata and trigger processes like auto-tagging. You can also use the API to manage your account and musicube cloud data. **Authentication** 1. Reach out to support@songtradr.com to receive a free account or use your login data if you are already signed up. 2. To authenticate, you need to login via the POST /api/v1/user/login endpoint. 3. The endpoint responds with a jwtToken which you can use in all following API requests as a bearer token. **Rate Limiting** The current limit is 120 Requests per minute. Reach out to us via support@songtradr.com if you need to request more. **Getting Started with auto-tagging** 1. If you want to get your own files auto-tagged, use the POST /api/v1/user/file/{name}/initUpload endpoint. It responds with a presigned S3 link where you can upload your file. 2. You can check the processing status of your file via the GET /api/v1/user/file/{name}/filesStatus endpoint. 3. As soon as processing is done, you can request the generated data via the GET /api/v1/user/files endpoint. **Getting Started with search** You can either search the released music via the /public/recording endpoints or your own private uploaded music via the /user/file/ endpoints. 1. If you want to search the world's released music, a good starting point is the GET /api/v1/public/recording/search endpoint. Please find the extensive list of parameters that serve as semantic search filters. 2. If you want to search your own previously uploaded music, a good starting point is the GET GET /api/v1/user/files endpoint. It has the same extensive list of parameters that serve as semantic search filters.
5
5
 
6
- The version of the OpenAPI document: 1.13.5
6
+ The version of the OpenAPI document: 1.13.6
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 7.1.0-SNAPSHOT
@@ -3,7 +3,7 @@
3
3
 
4
4
  #This is the Songtradr API. Use it to retrieve deep music metadata and trigger processes like auto-tagging. You can also use the API to manage your account and musicube cloud data. **Authentication** 1. Reach out to support@songtradr.com to receive a free account or use your login data if you are already signed up. 2. To authenticate, you need to login via the POST /api/v1/user/login endpoint. 3. The endpoint responds with a jwtToken which you can use in all following API requests as a bearer token. **Rate Limiting** The current limit is 120 Requests per minute. Reach out to us via support@songtradr.com if you need to request more. **Getting Started with auto-tagging** 1. If you want to get your own files auto-tagged, use the POST /api/v1/user/file/{name}/initUpload endpoint. It responds with a presigned S3 link where you can upload your file. 2. You can check the processing status of your file via the GET /api/v1/user/file/{name}/filesStatus endpoint. 3. As soon as processing is done, you can request the generated data via the GET /api/v1/user/files endpoint. **Getting Started with search** You can either search the released music via the /public/recording endpoints or your own private uploaded music via the /user/file/ endpoints. 1. If you want to search the world's released music, a good starting point is the GET /api/v1/public/recording/search endpoint. Please find the extensive list of parameters that serve as semantic search filters. 2. If you want to search your own previously uploaded music, a good starting point is the GET GET /api/v1/user/files endpoint. It has the same extensive list of parameters that serve as semantic search filters.
5
5
 
6
- The version of the OpenAPI document: 1.13.5
6
+ The version of the OpenAPI document: 1.13.6
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 7.1.0-SNAPSHOT
@@ -3,7 +3,7 @@
3
3
 
4
4
  #This is the Songtradr API. Use it to retrieve deep music metadata and trigger processes like auto-tagging. You can also use the API to manage your account and musicube cloud data. **Authentication** 1. Reach out to support@songtradr.com to receive a free account or use your login data if you are already signed up. 2. To authenticate, you need to login via the POST /api/v1/user/login endpoint. 3. The endpoint responds with a jwtToken which you can use in all following API requests as a bearer token. **Rate Limiting** The current limit is 120 Requests per minute. Reach out to us via support@songtradr.com if you need to request more. **Getting Started with auto-tagging** 1. If you want to get your own files auto-tagged, use the POST /api/v1/user/file/{name}/initUpload endpoint. It responds with a presigned S3 link where you can upload your file. 2. You can check the processing status of your file via the GET /api/v1/user/file/{name}/filesStatus endpoint. 3. As soon as processing is done, you can request the generated data via the GET /api/v1/user/files endpoint. **Getting Started with search** You can either search the released music via the /public/recording endpoints or your own private uploaded music via the /user/file/ endpoints. 1. If you want to search the world's released music, a good starting point is the GET /api/v1/public/recording/search endpoint. Please find the extensive list of parameters that serve as semantic search filters. 2. If you want to search your own previously uploaded music, a good starting point is the GET GET /api/v1/user/files endpoint. It has the same extensive list of parameters that serve as semantic search filters.
5
5
 
6
- The version of the OpenAPI document: 1.13.5
6
+ The version of the OpenAPI document: 1.13.6
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 7.1.0-SNAPSHOT
@@ -3,7 +3,7 @@
3
3
 
4
4
  #This is the Songtradr API. Use it to retrieve deep music metadata and trigger processes like auto-tagging. You can also use the API to manage your account and musicube cloud data. **Authentication** 1. Reach out to support@songtradr.com to receive a free account or use your login data if you are already signed up. 2. To authenticate, you need to login via the POST /api/v1/user/login endpoint. 3. The endpoint responds with a jwtToken which you can use in all following API requests as a bearer token. **Rate Limiting** The current limit is 120 Requests per minute. Reach out to us via support@songtradr.com if you need to request more. **Getting Started with auto-tagging** 1. If you want to get your own files auto-tagged, use the POST /api/v1/user/file/{name}/initUpload endpoint. It responds with a presigned S3 link where you can upload your file. 2. You can check the processing status of your file via the GET /api/v1/user/file/{name}/filesStatus endpoint. 3. As soon as processing is done, you can request the generated data via the GET /api/v1/user/files endpoint. **Getting Started with search** You can either search the released music via the /public/recording endpoints or your own private uploaded music via the /user/file/ endpoints. 1. If you want to search the world's released music, a good starting point is the GET /api/v1/public/recording/search endpoint. Please find the extensive list of parameters that serve as semantic search filters. 2. If you want to search your own previously uploaded music, a good starting point is the GET GET /api/v1/user/files endpoint. It has the same extensive list of parameters that serve as semantic search filters.
5
5
 
6
- The version of the OpenAPI document: 1.13.5
6
+ The version of the OpenAPI document: 1.13.6
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 7.1.0-SNAPSHOT
@@ -3,7 +3,7 @@
3
3
 
4
4
  #This is the Songtradr API. Use it to retrieve deep music metadata and trigger processes like auto-tagging. You can also use the API to manage your account and musicube cloud data. **Authentication** 1. Reach out to support@songtradr.com to receive a free account or use your login data if you are already signed up. 2. To authenticate, you need to login via the POST /api/v1/user/login endpoint. 3. The endpoint responds with a jwtToken which you can use in all following API requests as a bearer token. **Rate Limiting** The current limit is 120 Requests per minute. Reach out to us via support@songtradr.com if you need to request more. **Getting Started with auto-tagging** 1. If you want to get your own files auto-tagged, use the POST /api/v1/user/file/{name}/initUpload endpoint. It responds with a presigned S3 link where you can upload your file. 2. You can check the processing status of your file via the GET /api/v1/user/file/{name}/filesStatus endpoint. 3. As soon as processing is done, you can request the generated data via the GET /api/v1/user/files endpoint. **Getting Started with search** You can either search the released music via the /public/recording endpoints or your own private uploaded music via the /user/file/ endpoints. 1. If you want to search the world's released music, a good starting point is the GET /api/v1/public/recording/search endpoint. Please find the extensive list of parameters that serve as semantic search filters. 2. If you want to search your own previously uploaded music, a good starting point is the GET GET /api/v1/user/files endpoint. It has the same extensive list of parameters that serve as semantic search filters.
5
5
 
6
- The version of the OpenAPI document: 1.13.5
6
+ The version of the OpenAPI document: 1.13.6
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 7.1.0-SNAPSHOT
@@ -3,7 +3,7 @@
3
3
 
4
4
  #This is the Songtradr API. Use it to retrieve deep music metadata and trigger processes like auto-tagging. You can also use the API to manage your account and musicube cloud data. **Authentication** 1. Reach out to support@songtradr.com to receive a free account or use your login data if you are already signed up. 2. To authenticate, you need to login via the POST /api/v1/user/login endpoint. 3. The endpoint responds with a jwtToken which you can use in all following API requests as a bearer token. **Rate Limiting** The current limit is 120 Requests per minute. Reach out to us via support@songtradr.com if you need to request more. **Getting Started with auto-tagging** 1. If you want to get your own files auto-tagged, use the POST /api/v1/user/file/{name}/initUpload endpoint. It responds with a presigned S3 link where you can upload your file. 2. You can check the processing status of your file via the GET /api/v1/user/file/{name}/filesStatus endpoint. 3. As soon as processing is done, you can request the generated data via the GET /api/v1/user/files endpoint. **Getting Started with search** You can either search the released music via the /public/recording endpoints or your own private uploaded music via the /user/file/ endpoints. 1. If you want to search the world's released music, a good starting point is the GET /api/v1/public/recording/search endpoint. Please find the extensive list of parameters that serve as semantic search filters. 2. If you want to search your own previously uploaded music, a good starting point is the GET GET /api/v1/user/files endpoint. It has the same extensive list of parameters that serve as semantic search filters.
5
5
 
6
- The version of the OpenAPI document: 1.13.5
6
+ The version of the OpenAPI document: 1.13.6
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 7.1.0-SNAPSHOT
@@ -3,7 +3,7 @@
3
3
 
4
4
  #This is the Songtradr API. Use it to retrieve deep music metadata and trigger processes like auto-tagging. You can also use the API to manage your account and musicube cloud data. **Authentication** 1. Reach out to support@songtradr.com to receive a free account or use your login data if you are already signed up. 2. To authenticate, you need to login via the POST /api/v1/user/login endpoint. 3. The endpoint responds with a jwtToken which you can use in all following API requests as a bearer token. **Rate Limiting** The current limit is 120 Requests per minute. Reach out to us via support@songtradr.com if you need to request more. **Getting Started with auto-tagging** 1. If you want to get your own files auto-tagged, use the POST /api/v1/user/file/{name}/initUpload endpoint. It responds with a presigned S3 link where you can upload your file. 2. You can check the processing status of your file via the GET /api/v1/user/file/{name}/filesStatus endpoint. 3. As soon as processing is done, you can request the generated data via the GET /api/v1/user/files endpoint. **Getting Started with search** You can either search the released music via the /public/recording endpoints or your own private uploaded music via the /user/file/ endpoints. 1. If you want to search the world's released music, a good starting point is the GET /api/v1/public/recording/search endpoint. Please find the extensive list of parameters that serve as semantic search filters. 2. If you want to search your own previously uploaded music, a good starting point is the GET GET /api/v1/user/files endpoint. It has the same extensive list of parameters that serve as semantic search filters.
5
5
 
6
- The version of the OpenAPI document: 1.13.5
6
+ The version of the OpenAPI document: 1.13.6
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 7.1.0-SNAPSHOT
@@ -3,7 +3,7 @@
3
3
 
4
4
  #This is the Songtradr API. Use it to retrieve deep music metadata and trigger processes like auto-tagging. You can also use the API to manage your account and musicube cloud data. **Authentication** 1. Reach out to support@songtradr.com to receive a free account or use your login data if you are already signed up. 2. To authenticate, you need to login via the POST /api/v1/user/login endpoint. 3. The endpoint responds with a jwtToken which you can use in all following API requests as a bearer token. **Rate Limiting** The current limit is 120 Requests per minute. Reach out to us via support@songtradr.com if you need to request more. **Getting Started with auto-tagging** 1. If you want to get your own files auto-tagged, use the POST /api/v1/user/file/{name}/initUpload endpoint. It responds with a presigned S3 link where you can upload your file. 2. You can check the processing status of your file via the GET /api/v1/user/file/{name}/filesStatus endpoint. 3. As soon as processing is done, you can request the generated data via the GET /api/v1/user/files endpoint. **Getting Started with search** You can either search the released music via the /public/recording endpoints or your own private uploaded music via the /user/file/ endpoints. 1. If you want to search the world's released music, a good starting point is the GET /api/v1/public/recording/search endpoint. Please find the extensive list of parameters that serve as semantic search filters. 2. If you want to search your own previously uploaded music, a good starting point is the GET GET /api/v1/user/files endpoint. It has the same extensive list of parameters that serve as semantic search filters.
5
5
 
6
- The version of the OpenAPI document: 1.13.5
6
+ The version of the OpenAPI document: 1.13.6
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 7.1.0-SNAPSHOT
@@ -3,7 +3,7 @@
3
3
 
4
4
  #This is the Songtradr API. Use it to retrieve deep music metadata and trigger processes like auto-tagging. You can also use the API to manage your account and musicube cloud data. **Authentication** 1. Reach out to support@songtradr.com to receive a free account or use your login data if you are already signed up. 2. To authenticate, you need to login via the POST /api/v1/user/login endpoint. 3. The endpoint responds with a jwtToken which you can use in all following API requests as a bearer token. **Rate Limiting** The current limit is 120 Requests per minute. Reach out to us via support@songtradr.com if you need to request more. **Getting Started with auto-tagging** 1. If you want to get your own files auto-tagged, use the POST /api/v1/user/file/{name}/initUpload endpoint. It responds with a presigned S3 link where you can upload your file. 2. You can check the processing status of your file via the GET /api/v1/user/file/{name}/filesStatus endpoint. 3. As soon as processing is done, you can request the generated data via the GET /api/v1/user/files endpoint. **Getting Started with search** You can either search the released music via the /public/recording endpoints or your own private uploaded music via the /user/file/ endpoints. 1. If you want to search the world's released music, a good starting point is the GET /api/v1/public/recording/search endpoint. Please find the extensive list of parameters that serve as semantic search filters. 2. If you want to search your own previously uploaded music, a good starting point is the GET GET /api/v1/user/files endpoint. It has the same extensive list of parameters that serve as semantic search filters.
5
5
 
6
- The version of the OpenAPI document: 1.13.5
6
+ The version of the OpenAPI document: 1.13.6
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 7.1.0-SNAPSHOT
@@ -3,7 +3,7 @@
3
3
 
4
4
  #This is the Songtradr API. Use it to retrieve deep music metadata and trigger processes like auto-tagging. You can also use the API to manage your account and musicube cloud data. **Authentication** 1. Reach out to support@songtradr.com to receive a free account or use your login data if you are already signed up. 2. To authenticate, you need to login via the POST /api/v1/user/login endpoint. 3. The endpoint responds with a jwtToken which you can use in all following API requests as a bearer token. **Rate Limiting** The current limit is 120 Requests per minute. Reach out to us via support@songtradr.com if you need to request more. **Getting Started with auto-tagging** 1. If you want to get your own files auto-tagged, use the POST /api/v1/user/file/{name}/initUpload endpoint. It responds with a presigned S3 link where you can upload your file. 2. You can check the processing status of your file via the GET /api/v1/user/file/{name}/filesStatus endpoint. 3. As soon as processing is done, you can request the generated data via the GET /api/v1/user/files endpoint. **Getting Started with search** You can either search the released music via the /public/recording endpoints or your own private uploaded music via the /user/file/ endpoints. 1. If you want to search the world's released music, a good starting point is the GET /api/v1/public/recording/search endpoint. Please find the extensive list of parameters that serve as semantic search filters. 2. If you want to search your own previously uploaded music, a good starting point is the GET GET /api/v1/user/files endpoint. It has the same extensive list of parameters that serve as semantic search filters.
5
5
 
6
- The version of the OpenAPI document: 1.13.5
6
+ The version of the OpenAPI document: 1.13.6
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 7.1.0-SNAPSHOT
@@ -3,7 +3,7 @@
3
3
 
4
4
  #This is the Songtradr API. Use it to retrieve deep music metadata and trigger processes like auto-tagging. You can also use the API to manage your account and musicube cloud data. **Authentication** 1. Reach out to support@songtradr.com to receive a free account or use your login data if you are already signed up. 2. To authenticate, you need to login via the POST /api/v1/user/login endpoint. 3. The endpoint responds with a jwtToken which you can use in all following API requests as a bearer token. **Rate Limiting** The current limit is 120 Requests per minute. Reach out to us via support@songtradr.com if you need to request more. **Getting Started with auto-tagging** 1. If you want to get your own files auto-tagged, use the POST /api/v1/user/file/{name}/initUpload endpoint. It responds with a presigned S3 link where you can upload your file. 2. You can check the processing status of your file via the GET /api/v1/user/file/{name}/filesStatus endpoint. 3. As soon as processing is done, you can request the generated data via the GET /api/v1/user/files endpoint. **Getting Started with search** You can either search the released music via the /public/recording endpoints or your own private uploaded music via the /user/file/ endpoints. 1. If you want to search the world's released music, a good starting point is the GET /api/v1/public/recording/search endpoint. Please find the extensive list of parameters that serve as semantic search filters. 2. If you want to search your own previously uploaded music, a good starting point is the GET GET /api/v1/user/files endpoint. It has the same extensive list of parameters that serve as semantic search filters.
5
5
 
6
- The version of the OpenAPI document: 1.13.5
6
+ The version of the OpenAPI document: 1.13.6
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 7.1.0-SNAPSHOT
@@ -147,42 +147,12 @@ describe SongtradrApiClientRuby::MusicalFeaturesDTO do
147
147
  end
148
148
  end
149
149
 
150
- describe 'test attribute "roughness"' do
151
- it 'should work' do
152
- # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
153
- # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["very clear", "clear", "moderate roughness", "distorted", "very distorted"])
154
- # validator.allowable_values.each do |value|
155
- # expect { instance.roughness = value }.not_to raise_error
156
- # end
157
- end
158
- end
159
-
160
- describe 'test attribute "scale"' do
161
- it 'should work' do
162
- # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
163
- # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["major key", "minor key", "neutral key"])
164
- # validator.allowable_values.each do |value|
165
- # expect { instance.scale = value }.not_to raise_error
166
- # end
167
- end
168
- end
169
-
170
- describe 'test attribute "sound_generation"' do
171
- it 'should work' do
172
- # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
173
- # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["acoustic", "electric", "electronic", "mixed sound generation"])
174
- # validator.allowable_values.each do |value|
175
- # expect { instance.sound_generation = value }.not_to raise_error
176
- # end
177
- end
178
- end
179
-
180
- describe 'test attribute "tempo"' do
150
+ describe 'test attribute "audience_region"' do
181
151
  it 'should work' do
182
152
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
183
- # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["very slow", "slow", "mid-tempo", "fast", "very fast", "varying tempo"])
153
+ # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["Australia and New Zealand", "Central America and the Carribean", "Central and Southern Asia", "Eastern Asia", "Eastern Europe", "Northern Africa and Western Asia", "Northern America", "Oceania", "South America", "South-Eastern Asia", "Southern Europe", "Sub-Saharan Africa", "Western and Northern Europe"])
184
154
  # validator.allowable_values.each do |value|
185
- # expect { instance.tempo = value }.not_to raise_error
155
+ # expect { instance.audience_region = value }.not_to raise_error
186
156
  # end
187
157
  end
188
158
  end
@@ -505,12 +475,42 @@ describe SongtradrApiClientRuby::MusicalFeaturesDTO do
505
475
  end
506
476
  end
507
477
 
508
- describe 'test attribute "audience_region"' do
478
+ describe 'test attribute "roughness"' do
509
479
  it 'should work' do
510
480
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
511
- # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["Australia and New Zealand", "Central America and the Carribean", "Central and Southern Asia", "Eastern Asia", "Eastern Europe", "Northern Africa and Western Asia", "Northern America", "Oceania", "South America", "South-Eastern Asia", "Southern Europe", "Sub-Saharan Africa", "Western and Northern Europe"])
481
+ # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["very clear", "clear", "moderate roughness", "distorted", "very distorted"])
512
482
  # validator.allowable_values.each do |value|
513
- # expect { instance.audience_region = value }.not_to raise_error
483
+ # expect { instance.roughness = value }.not_to raise_error
484
+ # end
485
+ end
486
+ end
487
+
488
+ describe 'test attribute "scale"' do
489
+ it 'should work' do
490
+ # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
491
+ # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["major key", "minor key", "neutral key"])
492
+ # validator.allowable_values.each do |value|
493
+ # expect { instance.scale = value }.not_to raise_error
494
+ # end
495
+ end
496
+ end
497
+
498
+ describe 'test attribute "sound_generation"' do
499
+ it 'should work' do
500
+ # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
501
+ # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["acoustic", "electric", "electronic", "mixed sound generation"])
502
+ # validator.allowable_values.each do |value|
503
+ # expect { instance.sound_generation = value }.not_to raise_error
504
+ # end
505
+ end
506
+ end
507
+
508
+ describe 'test attribute "tempo"' do
509
+ it 'should work' do
510
+ # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
511
+ # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["very slow", "slow", "mid-tempo", "fast", "very fast", "varying tempo"])
512
+ # validator.allowable_values.each do |value|
513
+ # expect { instance.tempo = value }.not_to raise_error
514
514
  # end
515
515
  end
516
516
  end
@@ -605,103 +605,103 @@ describe SongtradrApiClientRuby::MusicalFeaturesDTO do
605
605
  end
606
606
  end
607
607
 
608
- describe 'test attribute "valence_affinity"' do
608
+ describe 'test attribute "roughness_affinity"' do
609
609
  it 'should work' do
610
610
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
611
611
  end
612
612
  end
613
613
 
614
- describe 'test attribute "arousal_affinity"' do
614
+ describe 'test attribute "harmony_affinity"' do
615
615
  it 'should work' do
616
616
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
617
617
  end
618
618
  end
619
619
 
620
- describe 'test attribute "pleasantness_affinity"' do
620
+ describe 'test attribute "texture_affinity"' do
621
621
  it 'should work' do
622
622
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
623
623
  end
624
624
  end
625
625
 
626
- describe 'test attribute "engagement_affinity"' do
626
+ describe 'test attribute "groovyness_affinity"' do
627
627
  it 'should work' do
628
628
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
629
629
  end
630
630
  end
631
631
 
632
- describe 'test attribute "energy_affinity"' do
632
+ describe 'test attribute "space_affinity"' do
633
633
  it 'should work' do
634
634
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
635
635
  end
636
636
  end
637
637
 
638
- describe 'test attribute "tempo_affinity"' do
638
+ describe 'test attribute "key_affinity"' do
639
639
  it 'should work' do
640
640
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
641
641
  end
642
642
  end
643
643
 
644
- describe 'test attribute "scale_affinity"' do
644
+ describe 'test attribute "channel_suitability_affinity"' do
645
645
  it 'should work' do
646
646
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
647
647
  end
648
648
  end
649
649
 
650
- describe 'test attribute "timbre_affinity"' do
650
+ describe 'test attribute "key"' do
651
651
  it 'should work' do
652
652
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
653
+ # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["C", "C#", "D", "D#", "E", "F", "F#", "G", "G#", "A", "A#", "B", "unclear"])
654
+ # validator.allowable_values.each do |value|
655
+ # expect { instance.key = value }.not_to raise_error
656
+ # end
653
657
  end
654
658
  end
655
659
 
656
- describe 'test attribute "roughness_affinity"' do
660
+ describe 'test attribute "valence_affinity"' do
657
661
  it 'should work' do
658
662
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
659
663
  end
660
664
  end
661
665
 
662
- describe 'test attribute "harmony_affinity"' do
666
+ describe 'test attribute "arousal_affinity"' do
663
667
  it 'should work' do
664
668
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
665
669
  end
666
670
  end
667
671
 
668
- describe 'test attribute "texture_affinity"' do
672
+ describe 'test attribute "pleasantness_affinity"' do
669
673
  it 'should work' do
670
674
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
671
675
  end
672
676
  end
673
677
 
674
- describe 'test attribute "groovyness_affinity"' do
678
+ describe 'test attribute "engagement_affinity"' do
675
679
  it 'should work' do
676
680
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
677
681
  end
678
682
  end
679
683
 
680
- describe 'test attribute "space_affinity"' do
684
+ describe 'test attribute "energy_affinity"' do
681
685
  it 'should work' do
682
686
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
683
687
  end
684
688
  end
685
689
 
686
- describe 'test attribute "key_affinity"' do
690
+ describe 'test attribute "tempo_affinity"' do
687
691
  it 'should work' do
688
692
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
689
693
  end
690
694
  end
691
695
 
692
- describe 'test attribute "channel_suitability_affinity"' do
696
+ describe 'test attribute "scale_affinity"' do
693
697
  it 'should work' do
694
698
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
695
699
  end
696
700
  end
697
701
 
698
- describe 'test attribute "key"' do
702
+ describe 'test attribute "timbre_affinity"' do
699
703
  it 'should work' do
700
704
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
701
- # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["C", "C#", "D", "D#", "E", "F", "F#", "G", "G#", "A", "A#", "B", "unclear"])
702
- # validator.allowable_values.each do |value|
703
- # expect { instance.key = value }.not_to raise_error
704
- # end
705
705
  end
706
706
  end
707
707
 
@@ -3,7 +3,7 @@
3
3
 
4
4
  #This is the Songtradr API. Use it to retrieve deep music metadata and trigger processes like auto-tagging. You can also use the API to manage your account and musicube cloud data. **Authentication** 1. Reach out to support@songtradr.com to receive a free account or use your login data if you are already signed up. 2. To authenticate, you need to login via the POST /api/v1/user/login endpoint. 3. The endpoint responds with a jwtToken which you can use in all following API requests as a bearer token. **Rate Limiting** The current limit is 120 Requests per minute. Reach out to us via support@songtradr.com if you need to request more. **Getting Started with auto-tagging** 1. If you want to get your own files auto-tagged, use the POST /api/v1/user/file/{name}/initUpload endpoint. It responds with a presigned S3 link where you can upload your file. 2. You can check the processing status of your file via the GET /api/v1/user/file/{name}/filesStatus endpoint. 3. As soon as processing is done, you can request the generated data via the GET /api/v1/user/files endpoint. **Getting Started with search** You can either search the released music via the /public/recording endpoints or your own private uploaded music via the /user/file/ endpoints. 1. If you want to search the world's released music, a good starting point is the GET /api/v1/public/recording/search endpoint. Please find the extensive list of parameters that serve as semantic search filters. 2. If you want to search your own previously uploaded music, a good starting point is the GET GET /api/v1/user/files endpoint. It has the same extensive list of parameters that serve as semantic search filters.
5
5
 
6
- The version of the OpenAPI document: 1.13.5
6
+ The version of the OpenAPI document: 1.13.6
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 7.1.0-SNAPSHOT
@@ -3,7 +3,7 @@
3
3
 
4
4
  #This is the Songtradr API. Use it to retrieve deep music metadata and trigger processes like auto-tagging. You can also use the API to manage your account and musicube cloud data. **Authentication** 1. Reach out to support@songtradr.com to receive a free account or use your login data if you are already signed up. 2. To authenticate, you need to login via the POST /api/v1/user/login endpoint. 3. The endpoint responds with a jwtToken which you can use in all following API requests as a bearer token. **Rate Limiting** The current limit is 120 Requests per minute. Reach out to us via support@songtradr.com if you need to request more. **Getting Started with auto-tagging** 1. If you want to get your own files auto-tagged, use the POST /api/v1/user/file/{name}/initUpload endpoint. It responds with a presigned S3 link where you can upload your file. 2. You can check the processing status of your file via the GET /api/v1/user/file/{name}/filesStatus endpoint. 3. As soon as processing is done, you can request the generated data via the GET /api/v1/user/files endpoint. **Getting Started with search** You can either search the released music via the /public/recording endpoints or your own private uploaded music via the /user/file/ endpoints. 1. If you want to search the world's released music, a good starting point is the GET /api/v1/public/recording/search endpoint. Please find the extensive list of parameters that serve as semantic search filters. 2. If you want to search your own previously uploaded music, a good starting point is the GET GET /api/v1/user/files endpoint. It has the same extensive list of parameters that serve as semantic search filters.
5
5
 
6
- The version of the OpenAPI document: 1.13.5
6
+ The version of the OpenAPI document: 1.13.6
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 7.1.0-SNAPSHOT
@@ -3,7 +3,7 @@
3
3
 
4
4
  #This is the Songtradr API. Use it to retrieve deep music metadata and trigger processes like auto-tagging. You can also use the API to manage your account and musicube cloud data. **Authentication** 1. Reach out to support@songtradr.com to receive a free account or use your login data if you are already signed up. 2. To authenticate, you need to login via the POST /api/v1/user/login endpoint. 3. The endpoint responds with a jwtToken which you can use in all following API requests as a bearer token. **Rate Limiting** The current limit is 120 Requests per minute. Reach out to us via support@songtradr.com if you need to request more. **Getting Started with auto-tagging** 1. If you want to get your own files auto-tagged, use the POST /api/v1/user/file/{name}/initUpload endpoint. It responds with a presigned S3 link where you can upload your file. 2. You can check the processing status of your file via the GET /api/v1/user/file/{name}/filesStatus endpoint. 3. As soon as processing is done, you can request the generated data via the GET /api/v1/user/files endpoint. **Getting Started with search** You can either search the released music via the /public/recording endpoints or your own private uploaded music via the /user/file/ endpoints. 1. If you want to search the world's released music, a good starting point is the GET /api/v1/public/recording/search endpoint. Please find the extensive list of parameters that serve as semantic search filters. 2. If you want to search your own previously uploaded music, a good starting point is the GET GET /api/v1/user/files endpoint. It has the same extensive list of parameters that serve as semantic search filters.
5
5
 
6
- The version of the OpenAPI document: 1.13.5
6
+ The version of the OpenAPI document: 1.13.6
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 7.1.0-SNAPSHOT
@@ -3,7 +3,7 @@
3
3
 
4
4
  #This is the Songtradr API. Use it to retrieve deep music metadata and trigger processes like auto-tagging. You can also use the API to manage your account and musicube cloud data. **Authentication** 1. Reach out to support@songtradr.com to receive a free account or use your login data if you are already signed up. 2. To authenticate, you need to login via the POST /api/v1/user/login endpoint. 3. The endpoint responds with a jwtToken which you can use in all following API requests as a bearer token. **Rate Limiting** The current limit is 120 Requests per minute. Reach out to us via support@songtradr.com if you need to request more. **Getting Started with auto-tagging** 1. If you want to get your own files auto-tagged, use the POST /api/v1/user/file/{name}/initUpload endpoint. It responds with a presigned S3 link where you can upload your file. 2. You can check the processing status of your file via the GET /api/v1/user/file/{name}/filesStatus endpoint. 3. As soon as processing is done, you can request the generated data via the GET /api/v1/user/files endpoint. **Getting Started with search** You can either search the released music via the /public/recording endpoints or your own private uploaded music via the /user/file/ endpoints. 1. If you want to search the world's released music, a good starting point is the GET /api/v1/public/recording/search endpoint. Please find the extensive list of parameters that serve as semantic search filters. 2. If you want to search your own previously uploaded music, a good starting point is the GET GET /api/v1/user/files endpoint. It has the same extensive list of parameters that serve as semantic search filters.
5
5
 
6
- The version of the OpenAPI document: 1.13.5
6
+ The version of the OpenAPI document: 1.13.6
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 7.1.0-SNAPSHOT
@@ -3,7 +3,7 @@
3
3
 
4
4
  #This is the Songtradr API. Use it to retrieve deep music metadata and trigger processes like auto-tagging. You can also use the API to manage your account and musicube cloud data. **Authentication** 1. Reach out to support@songtradr.com to receive a free account or use your login data if you are already signed up. 2. To authenticate, you need to login via the POST /api/v1/user/login endpoint. 3. The endpoint responds with a jwtToken which you can use in all following API requests as a bearer token. **Rate Limiting** The current limit is 120 Requests per minute. Reach out to us via support@songtradr.com if you need to request more. **Getting Started with auto-tagging** 1. If you want to get your own files auto-tagged, use the POST /api/v1/user/file/{name}/initUpload endpoint. It responds with a presigned S3 link where you can upload your file. 2. You can check the processing status of your file via the GET /api/v1/user/file/{name}/filesStatus endpoint. 3. As soon as processing is done, you can request the generated data via the GET /api/v1/user/files endpoint. **Getting Started with search** You can either search the released music via the /public/recording endpoints or your own private uploaded music via the /user/file/ endpoints. 1. If you want to search the world's released music, a good starting point is the GET /api/v1/public/recording/search endpoint. Please find the extensive list of parameters that serve as semantic search filters. 2. If you want to search your own previously uploaded music, a good starting point is the GET GET /api/v1/user/files endpoint. It has the same extensive list of parameters that serve as semantic search filters.
5
5
 
6
- The version of the OpenAPI document: 1.13.5
6
+ The version of the OpenAPI document: 1.13.6
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 7.1.0-SNAPSHOT
@@ -3,7 +3,7 @@
3
3
 
4
4
  #This is the Songtradr API. Use it to retrieve deep music metadata and trigger processes like auto-tagging. You can also use the API to manage your account and musicube cloud data. **Authentication** 1. Reach out to support@songtradr.com to receive a free account or use your login data if you are already signed up. 2. To authenticate, you need to login via the POST /api/v1/user/login endpoint. 3. The endpoint responds with a jwtToken which you can use in all following API requests as a bearer token. **Rate Limiting** The current limit is 120 Requests per minute. Reach out to us via support@songtradr.com if you need to request more. **Getting Started with auto-tagging** 1. If you want to get your own files auto-tagged, use the POST /api/v1/user/file/{name}/initUpload endpoint. It responds with a presigned S3 link where you can upload your file. 2. You can check the processing status of your file via the GET /api/v1/user/file/{name}/filesStatus endpoint. 3. As soon as processing is done, you can request the generated data via the GET /api/v1/user/files endpoint. **Getting Started with search** You can either search the released music via the /public/recording endpoints or your own private uploaded music via the /user/file/ endpoints. 1. If you want to search the world's released music, a good starting point is the GET /api/v1/public/recording/search endpoint. Please find the extensive list of parameters that serve as semantic search filters. 2. If you want to search your own previously uploaded music, a good starting point is the GET GET /api/v1/user/files endpoint. It has the same extensive list of parameters that serve as semantic search filters.
5
5
 
6
- The version of the OpenAPI document: 1.13.5
6
+ The version of the OpenAPI document: 1.13.6
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 7.1.0-SNAPSHOT
@@ -49,12 +49,6 @@ describe SongtradrApiClientRuby::PlaylistLargeDTO do
49
49
  end
50
50
  end
51
51
 
52
- describe 'test attribute "songtradr_playlist_guid"' do
53
- it 'should work' do
54
- # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
55
- end
56
- end
57
-
58
52
  describe 'test attribute "usages"' do
59
53
  it 'should work' do
60
54
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
@@ -85,6 +79,12 @@ describe SongtradrApiClientRuby::PlaylistLargeDTO do
85
79
  end
86
80
  end
87
81
 
82
+ describe 'test attribute "songtradr_playlist_guid"' do
83
+ it 'should work' do
84
+ # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
85
+ end
86
+ end
87
+
88
88
  describe 'test attribute "created"' do
89
89
  it 'should work' do
90
90
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
@@ -3,7 +3,7 @@
3
3
 
4
4
  #This is the Songtradr API. Use it to retrieve deep music metadata and trigger processes like auto-tagging. You can also use the API to manage your account and musicube cloud data. **Authentication** 1. Reach out to support@songtradr.com to receive a free account or use your login data if you are already signed up. 2. To authenticate, you need to login via the POST /api/v1/user/login endpoint. 3. The endpoint responds with a jwtToken which you can use in all following API requests as a bearer token. **Rate Limiting** The current limit is 120 Requests per minute. Reach out to us via support@songtradr.com if you need to request more. **Getting Started with auto-tagging** 1. If you want to get your own files auto-tagged, use the POST /api/v1/user/file/{name}/initUpload endpoint. It responds with a presigned S3 link where you can upload your file. 2. You can check the processing status of your file via the GET /api/v1/user/file/{name}/filesStatus endpoint. 3. As soon as processing is done, you can request the generated data via the GET /api/v1/user/files endpoint. **Getting Started with search** You can either search the released music via the /public/recording endpoints or your own private uploaded music via the /user/file/ endpoints. 1. If you want to search the world's released music, a good starting point is the GET /api/v1/public/recording/search endpoint. Please find the extensive list of parameters that serve as semantic search filters. 2. If you want to search your own previously uploaded music, a good starting point is the GET GET /api/v1/user/files endpoint. It has the same extensive list of parameters that serve as semantic search filters.
5
5
 
6
- The version of the OpenAPI document: 1.13.5
6
+ The version of the OpenAPI document: 1.13.6
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 7.1.0-SNAPSHOT
@@ -3,7 +3,7 @@
3
3
 
4
4
  #This is the Songtradr API. Use it to retrieve deep music metadata and trigger processes like auto-tagging. You can also use the API to manage your account and musicube cloud data. **Authentication** 1. Reach out to support@songtradr.com to receive a free account or use your login data if you are already signed up. 2. To authenticate, you need to login via the POST /api/v1/user/login endpoint. 3. The endpoint responds with a jwtToken which you can use in all following API requests as a bearer token. **Rate Limiting** The current limit is 120 Requests per minute. Reach out to us via support@songtradr.com if you need to request more. **Getting Started with auto-tagging** 1. If you want to get your own files auto-tagged, use the POST /api/v1/user/file/{name}/initUpload endpoint. It responds with a presigned S3 link where you can upload your file. 2. You can check the processing status of your file via the GET /api/v1/user/file/{name}/filesStatus endpoint. 3. As soon as processing is done, you can request the generated data via the GET /api/v1/user/files endpoint. **Getting Started with search** You can either search the released music via the /public/recording endpoints or your own private uploaded music via the /user/file/ endpoints. 1. If you want to search the world's released music, a good starting point is the GET /api/v1/public/recording/search endpoint. Please find the extensive list of parameters that serve as semantic search filters. 2. If you want to search your own previously uploaded music, a good starting point is the GET GET /api/v1/user/files endpoint. It has the same extensive list of parameters that serve as semantic search filters.
5
5
 
6
- The version of the OpenAPI document: 1.13.5
6
+ The version of the OpenAPI document: 1.13.6
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 7.1.0-SNAPSHOT
@@ -3,7 +3,7 @@
3
3
 
4
4
  #This is the Songtradr API. Use it to retrieve deep music metadata and trigger processes like auto-tagging. You can also use the API to manage your account and musicube cloud data. **Authentication** 1. Reach out to support@songtradr.com to receive a free account or use your login data if you are already signed up. 2. To authenticate, you need to login via the POST /api/v1/user/login endpoint. 3. The endpoint responds with a jwtToken which you can use in all following API requests as a bearer token. **Rate Limiting** The current limit is 120 Requests per minute. Reach out to us via support@songtradr.com if you need to request more. **Getting Started with auto-tagging** 1. If you want to get your own files auto-tagged, use the POST /api/v1/user/file/{name}/initUpload endpoint. It responds with a presigned S3 link where you can upload your file. 2. You can check the processing status of your file via the GET /api/v1/user/file/{name}/filesStatus endpoint. 3. As soon as processing is done, you can request the generated data via the GET /api/v1/user/files endpoint. **Getting Started with search** You can either search the released music via the /public/recording endpoints or your own private uploaded music via the /user/file/ endpoints. 1. If you want to search the world's released music, a good starting point is the GET /api/v1/public/recording/search endpoint. Please find the extensive list of parameters that serve as semantic search filters. 2. If you want to search your own previously uploaded music, a good starting point is the GET GET /api/v1/user/files endpoint. It has the same extensive list of parameters that serve as semantic search filters.
5
5
 
6
- The version of the OpenAPI document: 1.13.5
6
+ The version of the OpenAPI document: 1.13.6
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 7.1.0-SNAPSHOT
@@ -3,7 +3,7 @@
3
3
 
4
4
  #This is the Songtradr API. Use it to retrieve deep music metadata and trigger processes like auto-tagging. You can also use the API to manage your account and musicube cloud data. **Authentication** 1. Reach out to support@songtradr.com to receive a free account or use your login data if you are already signed up. 2. To authenticate, you need to login via the POST /api/v1/user/login endpoint. 3. The endpoint responds with a jwtToken which you can use in all following API requests as a bearer token. **Rate Limiting** The current limit is 120 Requests per minute. Reach out to us via support@songtradr.com if you need to request more. **Getting Started with auto-tagging** 1. If you want to get your own files auto-tagged, use the POST /api/v1/user/file/{name}/initUpload endpoint. It responds with a presigned S3 link where you can upload your file. 2. You can check the processing status of your file via the GET /api/v1/user/file/{name}/filesStatus endpoint. 3. As soon as processing is done, you can request the generated data via the GET /api/v1/user/files endpoint. **Getting Started with search** You can either search the released music via the /public/recording endpoints or your own private uploaded music via the /user/file/ endpoints. 1. If you want to search the world's released music, a good starting point is the GET /api/v1/public/recording/search endpoint. Please find the extensive list of parameters that serve as semantic search filters. 2. If you want to search your own previously uploaded music, a good starting point is the GET GET /api/v1/user/files endpoint. It has the same extensive list of parameters that serve as semantic search filters.
5
5
 
6
- The version of the OpenAPI document: 1.13.5
6
+ The version of the OpenAPI document: 1.13.6
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 7.1.0-SNAPSHOT