songtradr_api_client_ruby 1.13.0 → 1.13.2

Sign up to get free protection for your applications and to get access to all the features.
Files changed (173) hide show
  1. checksums.yaml +4 -4
  2. data/Gemfile.lock +1 -1
  3. data/README.md +5 -5
  4. data/docs/ApiKeyDTO.md +4 -4
  5. data/docs/CategoryMediumDTO.md +3 -3
  6. data/docs/PlaylistLargeDTO.md +11 -11
  7. data/docs/ProductMediumDTO.md +7 -7
  8. data/docs/ProductPartyDTO.md +3 -3
  9. data/docs/RecordingGenrePredictionDTO.md +3 -3
  10. data/docs/RecordingLargeDTO.md +7 -7
  11. data/docs/RecordingMediumDTO.md +5 -5
  12. data/docs/RecordingPartyDTO.md +3 -3
  13. data/docs/TrackToMediumProductDTO.md +3 -3
  14. data/getspec.rb +34 -15
  15. data/lib/songtradr_api_client_ruby/api/allowed_values_api.rb +2 -2
  16. data/lib/songtradr_api_client_ruby/api/api_keys_api.rb +2 -2
  17. data/lib/songtradr_api_client_ruby/api/party_api.rb +2 -2
  18. data/lib/songtradr_api_client_ruby/api/playlist_api.rb +2 -2
  19. data/lib/songtradr_api_client_ruby/api/recording_api.rb +2 -2
  20. data/lib/songtradr_api_client_ruby/api/user_api.rb +2 -2
  21. data/lib/songtradr_api_client_ruby/api_client.rb +2 -2
  22. data/lib/songtradr_api_client_ruby/api_error.rb +2 -2
  23. data/lib/songtradr_api_client_ruby/configuration.rb +4 -4
  24. data/lib/songtradr_api_client_ruby/models/admin_api_user_dto.rb +2 -2
  25. data/lib/songtradr_api_client_ruby/models/api_key_dto.rb +22 -22
  26. data/lib/songtradr_api_client_ruby/models/category_medium_dto.rb +17 -17
  27. data/lib/songtradr_api_client_ruby/models/category_minimal_dto.rb +2 -2
  28. data/lib/songtradr_api_client_ruby/models/config_access_dto.rb +2 -2
  29. data/lib/songtradr_api_client_ruby/models/config_identifier_dto.rb +2 -2
  30. data/lib/songtradr_api_client_ruby/models/contributor_type_dto.rb +2 -2
  31. data/lib/songtradr_api_client_ruby/models/create_api_key_dto.rb +2 -2
  32. data/lib/songtradr_api_client_ruby/models/error_response.rb +2 -2
  33. data/lib/songtradr_api_client_ruby/models/field_summary_dto.rb +2 -2
  34. data/lib/songtradr_api_client_ruby/models/file_dto.rb +2 -2
  35. data/lib/songtradr_api_client_ruby/models/file_list_dto.rb +2 -2
  36. data/lib/songtradr_api_client_ruby/models/file_minimal_with_url_dto.rb +2 -2
  37. data/lib/songtradr_api_client_ruby/models/file_small_dto.rb +2 -2
  38. data/lib/songtradr_api_client_ruby/models/file_upload_dto.rb +2 -2
  39. data/lib/songtradr_api_client_ruby/models/file_w_ith_url_dto.rb +2 -2
  40. data/lib/songtradr_api_client_ruby/models/files_summary_dto.rb +2 -2
  41. data/lib/songtradr_api_client_ruby/models/forgot_password_dto.rb +2 -2
  42. data/lib/songtradr_api_client_ruby/models/genre_dto.rb +2 -2
  43. data/lib/songtradr_api_client_ruby/models/genre_minimal_dto.rb +2 -2
  44. data/lib/songtradr_api_client_ruby/models/genres_summary_dto.rb +2 -2
  45. data/lib/songtradr_api_client_ruby/models/init_put_recording_audio_dto.rb +2 -2
  46. data/lib/songtradr_api_client_ruby/models/jwt_token_dto.rb +2 -2
  47. data/lib/songtradr_api_client_ruby/models/login_dto.rb +2 -2
  48. data/lib/songtradr_api_client_ruby/models/musical_features_dto.rb +2 -2
  49. data/lib/songtradr_api_client_ruby/models/p_line_dto.rb +2 -2
  50. data/lib/songtradr_api_client_ruby/models/party_large_dto.rb +2 -2
  51. data/lib/songtradr_api_client_ruby/models/party_small_dto.rb +2 -2
  52. data/lib/songtradr_api_client_ruby/models/playlist_large_dto.rb +50 -50
  53. data/lib/songtradr_api_client_ruby/models/product_medium_dto.rb +37 -37
  54. data/lib/songtradr_api_client_ruby/models/product_party_dto.rb +17 -17
  55. data/lib/songtradr_api_client_ruby/models/recording_for_similarity_search_dto.rb +2 -2
  56. data/lib/songtradr_api_client_ruby/models/recording_genre_prediction_dto.rb +22 -22
  57. data/lib/songtradr_api_client_ruby/models/recording_large_dto.rb +45 -45
  58. data/lib/songtradr_api_client_ruby/models/recording_list_dto.rb +2 -2
  59. data/lib/songtradr_api_client_ruby/models/recording_medium_dto.rb +36 -36
  60. data/lib/songtradr_api_client_ruby/models/recording_minimal_with_musical_features_dto.rb +2 -2
  61. data/lib/songtradr_api_client_ruby/models/recording_minimal_with_taggrams_dto.rb +2 -2
  62. data/lib/songtradr_api_client_ruby/models/recording_minimal_with_tagstrengths_dto.rb +2 -2
  63. data/lib/songtradr_api_client_ruby/models/recording_party_dto.rb +17 -17
  64. data/lib/songtradr_api_client_ruby/models/recording_playlist_dto.rb +2 -2
  65. data/lib/songtradr_api_client_ruby/models/recording_small_dto.rb +2 -2
  66. data/lib/songtradr_api_client_ruby/models/recording_tag_small_dto.rb +2 -2
  67. data/lib/songtradr_api_client_ruby/models/save_file_recording_dto.rb +14 -14
  68. data/lib/songtradr_api_client_ruby/models/save_playlist_dto.rb +2 -2
  69. data/lib/songtradr_api_client_ruby/models/save_recording_genre_dto.rb +2 -2
  70. data/lib/songtradr_api_client_ruby/models/save_recording_party_dto.rb +2 -2
  71. data/lib/songtradr_api_client_ruby/models/save_recording_playlist_dto.rb +2 -2
  72. data/lib/songtradr_api_client_ruby/models/save_recording_tag_dto.rb +2 -2
  73. data/lib/songtradr_api_client_ruby/models/save_referrer_dto.rb +2 -2
  74. data/lib/songtradr_api_client_ruby/models/save_taggrams_dto.rb +2 -2
  75. data/lib/songtradr_api_client_ruby/models/save_user_dto.rb +2 -2
  76. data/lib/songtradr_api_client_ruby/models/search_filter_values_dto.rb +2 -2
  77. data/lib/songtradr_api_client_ruby/models/search_recording_granular_abstraction_dto.rb +2 -2
  78. data/lib/songtradr_api_client_ruby/models/search_recording_granular_dto.rb +2 -2
  79. data/lib/songtradr_api_client_ruby/models/sign_up_dto.rb +2 -2
  80. data/lib/songtradr_api_client_ruby/models/tag_dto.rb +2 -2
  81. data/lib/songtradr_api_client_ruby/models/tag_small_dto.rb +2 -2
  82. data/lib/songtradr_api_client_ruby/models/taggram_dto.rb +2 -2
  83. data/lib/songtradr_api_client_ruby/models/tags_summary_dto.rb +2 -2
  84. data/lib/songtradr_api_client_ruby/models/tagstrength_dto.rb +2 -2
  85. data/lib/songtradr_api_client_ruby/models/title_dto.rb +2 -2
  86. data/lib/songtradr_api_client_ruby/models/token_request.rb +2 -2
  87. data/lib/songtradr_api_client_ruby/models/track_dto.rb +2 -2
  88. data/lib/songtradr_api_client_ruby/models/track_to_medium_product_dto.rb +22 -22
  89. data/lib/songtradr_api_client_ruby/models/update_password_dto.rb +2 -2
  90. data/lib/songtradr_api_client_ruby/models/usage_dto.rb +2 -2
  91. data/lib/songtradr_api_client_ruby/models/user_dto.rb +2 -2
  92. data/lib/songtradr_api_client_ruby/version.rb +3 -3
  93. data/lib/songtradr_api_client_ruby.rb +2 -2
  94. data/openapi-generator-config.yaml +1 -1
  95. data/songtradr_api_client_ruby.gemspec +2 -2
  96. data/spec/api/allowed_values_api_spec.rb +2 -2
  97. data/spec/api/api_keys_api_spec.rb +2 -2
  98. data/spec/api/party_api_spec.rb +2 -2
  99. data/spec/api/playlist_api_spec.rb +2 -2
  100. data/spec/api/recording_api_spec.rb +2 -2
  101. data/spec/api/user_api_spec.rb +2 -2
  102. data/spec/api_client_spec.rb +2 -2
  103. data/spec/configuration_spec.rb +2 -2
  104. data/spec/models/admin_api_user_dto_spec.rb +2 -2
  105. data/spec/models/api_key_dto_spec.rb +4 -4
  106. data/spec/models/category_medium_dto_spec.rb +4 -4
  107. data/spec/models/category_minimal_dto_spec.rb +2 -2
  108. data/spec/models/config_access_dto_spec.rb +2 -2
  109. data/spec/models/config_identifier_dto_spec.rb +2 -2
  110. data/spec/models/contributor_type_dto_spec.rb +2 -2
  111. data/spec/models/create_api_key_dto_spec.rb +2 -2
  112. data/spec/models/error_response_spec.rb +2 -2
  113. data/spec/models/field_summary_dto_spec.rb +2 -2
  114. data/spec/models/file_dto_spec.rb +2 -2
  115. data/spec/models/file_list_dto_spec.rb +2 -2
  116. data/spec/models/file_minimal_with_url_dto_spec.rb +2 -2
  117. data/spec/models/file_small_dto_spec.rb +2 -2
  118. data/spec/models/file_upload_dto_spec.rb +2 -2
  119. data/spec/models/file_w_ith_url_dto_spec.rb +2 -2
  120. data/spec/models/files_summary_dto_spec.rb +2 -2
  121. data/spec/models/forgot_password_dto_spec.rb +2 -2
  122. data/spec/models/genre_dto_spec.rb +2 -2
  123. data/spec/models/genre_minimal_dto_spec.rb +2 -2
  124. data/spec/models/genres_summary_dto_spec.rb +2 -2
  125. data/spec/models/init_put_recording_audio_dto_spec.rb +2 -2
  126. data/spec/models/jwt_token_dto_spec.rb +2 -2
  127. data/spec/models/login_dto_spec.rb +2 -2
  128. data/spec/models/musical_features_dto_spec.rb +2 -2
  129. data/spec/models/p_line_dto_spec.rb +2 -2
  130. data/spec/models/party_large_dto_spec.rb +2 -2
  131. data/spec/models/party_small_dto_spec.rb +2 -2
  132. data/spec/models/playlist_large_dto_spec.rb +11 -11
  133. data/spec/models/product_medium_dto_spec.rb +10 -10
  134. data/spec/models/product_party_dto_spec.rb +4 -4
  135. data/spec/models/recording_for_similarity_search_dto_spec.rb +2 -2
  136. data/spec/models/recording_genre_prediction_dto_spec.rb +5 -5
  137. data/spec/models/recording_large_dto_spec.rb +13 -13
  138. data/spec/models/recording_list_dto_spec.rb +2 -2
  139. data/spec/models/recording_medium_dto_spec.rb +13 -13
  140. data/spec/models/recording_minimal_with_musical_features_dto_spec.rb +2 -2
  141. data/spec/models/recording_minimal_with_taggrams_dto_spec.rb +2 -2
  142. data/spec/models/recording_minimal_with_tagstrengths_dto_spec.rb +2 -2
  143. data/spec/models/recording_party_dto_spec.rb +4 -4
  144. data/spec/models/recording_playlist_dto_spec.rb +2 -2
  145. data/spec/models/recording_small_dto_spec.rb +2 -2
  146. data/spec/models/recording_tag_small_dto_spec.rb +2 -2
  147. data/spec/models/save_file_recording_dto_spec.rb +8 -8
  148. data/spec/models/save_playlist_dto_spec.rb +2 -2
  149. data/spec/models/save_recording_genre_dto_spec.rb +2 -2
  150. data/spec/models/save_recording_party_dto_spec.rb +2 -2
  151. data/spec/models/save_recording_playlist_dto_spec.rb +2 -2
  152. data/spec/models/save_recording_tag_dto_spec.rb +2 -2
  153. data/spec/models/save_referrer_dto_spec.rb +2 -2
  154. data/spec/models/save_taggrams_dto_spec.rb +2 -2
  155. data/spec/models/save_user_dto_spec.rb +2 -2
  156. data/spec/models/search_filter_values_dto_spec.rb +2 -2
  157. data/spec/models/search_recording_granular_abstraction_dto_spec.rb +2 -2
  158. data/spec/models/search_recording_granular_dto_spec.rb +2 -2
  159. data/spec/models/sign_up_dto_spec.rb +2 -2
  160. data/spec/models/tag_dto_spec.rb +2 -2
  161. data/spec/models/tag_small_dto_spec.rb +2 -2
  162. data/spec/models/taggram_dto_spec.rb +2 -2
  163. data/spec/models/tags_summary_dto_spec.rb +2 -2
  164. data/spec/models/tagstrength_dto_spec.rb +2 -2
  165. data/spec/models/title_dto_spec.rb +2 -2
  166. data/spec/models/token_request_spec.rb +2 -2
  167. data/spec/models/track_dto_spec.rb +2 -2
  168. data/spec/models/track_to_medium_product_dto_spec.rb +5 -5
  169. data/spec/models/update_password_dto_spec.rb +2 -2
  170. data/spec/models/usage_dto_spec.rb +2 -2
  171. data/spec/models/user_dto_spec.rb +2 -2
  172. data/spec/spec_helper.rb +2 -2
  173. metadata +2 -2
@@ -3,10 +3,10 @@
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.0
6
+ The version of the OpenAPI document: 1.13.2
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 7.0.0-SNAPSHOT
9
+ OpenAPI Generator version: 7.0.1-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -3,10 +3,10 @@
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.0
6
+ The version of the OpenAPI document: 1.13.2
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 7.0.0-SNAPSHOT
9
+ OpenAPI Generator version: 7.0.1-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -3,10 +3,10 @@
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.0
6
+ The version of the OpenAPI document: 1.13.2
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 7.0.0-SNAPSHOT
9
+ OpenAPI Generator version: 7.0.1-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -3,10 +3,10 @@
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.0
6
+ The version of the OpenAPI document: 1.13.2
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 7.0.0-SNAPSHOT
9
+ OpenAPI Generator version: 7.0.1-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -3,10 +3,10 @@
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.0
6
+ The version of the OpenAPI document: 1.13.2
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 7.0.0-SNAPSHOT
9
+ OpenAPI Generator version: 7.0.1-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -3,10 +3,10 @@
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.0
6
+ The version of the OpenAPI document: 1.13.2
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 7.0.0-SNAPSHOT
9
+ OpenAPI Generator version: 7.0.1-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -3,10 +3,10 @@
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.0
6
+ The version of the OpenAPI document: 1.13.2
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 7.0.0-SNAPSHOT
9
+ OpenAPI Generator version: 7.0.1-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -3,10 +3,10 @@
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.0
6
+ The version of the OpenAPI document: 1.13.2
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 7.0.0-SNAPSHOT
9
+ OpenAPI Generator version: 7.0.1-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -3,10 +3,10 @@
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.0
6
+ The version of the OpenAPI document: 1.13.2
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 7.0.0-SNAPSHOT
9
+ OpenAPI Generator version: 7.0.1-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -3,10 +3,10 @@
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.0
6
+ The version of the OpenAPI document: 1.13.2
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 7.0.0-SNAPSHOT
9
+ OpenAPI Generator version: 7.0.1-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -3,10 +3,10 @@
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.0
6
+ The version of the OpenAPI document: 1.13.2
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 7.0.0-SNAPSHOT
9
+ OpenAPI Generator version: 7.0.1-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -3,10 +3,10 @@
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.0
6
+ The version of the OpenAPI document: 1.13.2
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 7.0.0-SNAPSHOT
9
+ OpenAPI Generator version: 7.0.1-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -3,10 +3,10 @@
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.0
6
+ The version of the OpenAPI document: 1.13.2
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 7.0.0-SNAPSHOT
9
+ OpenAPI Generator version: 7.0.1-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -3,10 +3,10 @@
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.0
6
+ The version of the OpenAPI document: 1.13.2
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 7.0.0-SNAPSHOT
9
+ OpenAPI Generator version: 7.0.1-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -3,10 +3,10 @@
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.0
6
+ The version of the OpenAPI document: 1.13.2
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 7.0.0-SNAPSHOT
9
+ OpenAPI Generator version: 7.0.1-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -3,10 +3,10 @@
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.0
6
+ The version of the OpenAPI document: 1.13.2
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 7.0.0-SNAPSHOT
9
+ OpenAPI Generator version: 7.0.1-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -3,10 +3,10 @@
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.0
6
+ The version of the OpenAPI document: 1.13.2
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 7.0.0-SNAPSHOT
9
+ OpenAPI Generator version: 7.0.1-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -41,55 +41,55 @@ describe SongtradrApiClientRuby::PlaylistLargeDTO do
41
41
  end
42
42
  end
43
43
 
44
- describe 'test attribute "description"' do
44
+ describe 'test attribute "songtradr_playlist_guid"' do
45
45
  it 'should work' do
46
46
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
47
47
  end
48
48
  end
49
49
 
50
- describe 'test attribute "created"' do
50
+ describe 'test attribute "pretzel_tier"' do
51
51
  it 'should work' do
52
52
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
53
53
  end
54
54
  end
55
55
 
56
- describe 'test attribute "updated"' do
56
+ describe 'test attribute "asset_url"' do
57
57
  it 'should work' do
58
58
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
59
59
  end
60
60
  end
61
61
 
62
- describe 'test attribute "usages"' do
62
+ describe 'test attribute "usage"' do
63
63
  it 'should work' do
64
64
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
65
65
  end
66
66
  end
67
67
 
68
- describe 'test attribute "songtradr_playlist_guid"' do
68
+ describe 'test attribute "usages"' do
69
69
  it 'should work' do
70
70
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
71
71
  end
72
72
  end
73
73
 
74
- describe 'test attribute "asset_url"' do
74
+ describe 'test attribute "tracks"' do
75
75
  it 'should work' do
76
76
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
77
77
  end
78
78
  end
79
79
 
80
- describe 'test attribute "pretzel_tier"' do
80
+ describe 'test attribute "created"' do
81
81
  it 'should work' do
82
82
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
83
83
  end
84
84
  end
85
85
 
86
- describe 'test attribute "usage"' do
86
+ describe 'test attribute "updated"' do
87
87
  it 'should work' do
88
88
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
89
89
  end
90
90
  end
91
91
 
92
- describe 'test attribute "tracks"' do
92
+ describe 'test attribute "description"' do
93
93
  it 'should work' do
94
94
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
95
95
  end
@@ -3,10 +3,10 @@
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.0
6
+ The version of the OpenAPI document: 1.13.2
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 7.0.0-SNAPSHOT
9
+ OpenAPI Generator version: 7.0.1-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -31,49 +31,49 @@ describe SongtradrApiClientRuby::ProductMediumDTO do
31
31
  end
32
32
  end
33
33
 
34
- describe 'test attribute "takedown_date"' do
34
+ describe 'test attribute "release_date"' do
35
35
  it 'should work' do
36
36
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
37
37
  end
38
38
  end
39
39
 
40
- describe 'test attribute "parties"' do
40
+ describe 'test attribute "takedown_date"' do
41
41
  it 'should work' do
42
42
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
43
43
  end
44
44
  end
45
45
 
46
- describe 'test attribute "gtin"' do
46
+ describe 'test attribute "parties"' do
47
47
  it 'should work' do
48
48
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
49
49
  end
50
50
  end
51
51
 
52
- describe 'test attribute "grid"' do
52
+ describe 'test attribute "genres"' do
53
53
  it 'should work' do
54
54
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
55
55
  end
56
56
  end
57
57
 
58
- describe 'test attribute "release_date"' do
58
+ describe 'test attribute "titles"' do
59
59
  it 'should work' do
60
60
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
61
61
  end
62
62
  end
63
63
 
64
- describe 'test attribute "pline"' do
64
+ describe 'test attribute "gtin"' do
65
65
  it 'should work' do
66
66
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
67
67
  end
68
68
  end
69
69
 
70
- describe 'test attribute "genres"' do
70
+ describe 'test attribute "grid"' do
71
71
  it 'should work' do
72
72
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
73
73
  end
74
74
  end
75
75
 
76
- describe 'test attribute "titles"' do
76
+ describe 'test attribute "pline"' do
77
77
  it 'should work' do
78
78
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
79
79
  end
@@ -3,10 +3,10 @@
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.0
6
+ The version of the OpenAPI document: 1.13.2
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 7.0.0-SNAPSHOT
9
+ OpenAPI Generator version: 7.0.1-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -25,13 +25,13 @@ describe SongtradrApiClientRuby::ProductPartyDTO do
25
25
  expect(instance).to be_instance_of(SongtradrApiClientRuby::ProductPartyDTO)
26
26
  end
27
27
  end
28
- describe 'test attribute "contributor_types"' do
28
+ describe 'test attribute "party"' do
29
29
  it 'should work' do
30
30
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
31
31
  end
32
32
  end
33
33
 
34
- describe 'test attribute "party"' do
34
+ describe 'test attribute "contributor_types"' do
35
35
  it 'should work' do
36
36
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
37
37
  end
@@ -3,10 +3,10 @@
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.0
6
+ The version of the OpenAPI document: 1.13.2
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 7.0.0-SNAPSHOT
9
+ OpenAPI Generator version: 7.0.1-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -3,10 +3,10 @@
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.0
6
+ The version of the OpenAPI document: 1.13.2
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 7.0.0-SNAPSHOT
9
+ OpenAPI Generator version: 7.0.1-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -25,19 +25,19 @@ describe SongtradrApiClientRuby::RecordingGenrePredictionDTO do
25
25
  expect(instance).to be_instance_of(SongtradrApiClientRuby::RecordingGenrePredictionDTO)
26
26
  end
27
27
  end
28
- describe 'test attribute "genre"' do
28
+ describe 'test attribute "genre_type"' do
29
29
  it 'should work' do
30
30
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
31
31
  end
32
32
  end
33
33
 
34
- describe 'test attribute "probability"' do
34
+ describe 'test attribute "genre"' do
35
35
  it 'should work' do
36
36
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
37
37
  end
38
38
  end
39
39
 
40
- describe 'test attribute "genre_type"' do
40
+ describe 'test attribute "probability"' do
41
41
  it 'should work' do
42
42
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
43
43
  end
@@ -3,10 +3,10 @@
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.0
6
+ The version of the OpenAPI document: 1.13.2
7
7
  Contact: info@songtradr.com
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 7.0.0-SNAPSHOT
9
+ OpenAPI Generator version: 7.0.1-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -31,67 +31,67 @@ describe SongtradrApiClientRuby::RecordingLargeDTO do
31
31
  end
32
32
  end
33
33
 
34
- describe 'test attribute "spotify_id"' do
34
+ describe 'test attribute "isrc"' do
35
35
  it 'should work' do
36
36
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
37
37
  end
38
38
  end
39
39
 
40
- describe 'test attribute "pline"' do
40
+ describe 'test attribute "parties"' do
41
41
  it 'should work' do
42
42
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
43
43
  end
44
44
  end
45
45
 
46
- describe 'test attribute "genre_predictions"' do
46
+ describe 'test attribute "genres"' do
47
47
  it 'should work' do
48
48
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
49
49
  end
50
50
  end
51
51
 
52
- describe 'test attribute "isrc"' do
52
+ describe 'test attribute "language_of_performance"' do
53
53
  it 'should work' do
54
54
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
55
55
  end
56
56
  end
57
57
 
58
- describe 'test attribute "parties"' do
58
+ describe 'test attribute "titles"' do
59
59
  it 'should work' do
60
60
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
61
61
  end
62
62
  end
63
63
 
64
- describe 'test attribute "genres"' do
64
+ describe 'test attribute "tracks"' do
65
65
  it 'should work' do
66
66
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
67
67
  end
68
68
  end
69
69
 
70
- describe 'test attribute "language_of_performance"' do
70
+ describe 'test attribute "musical_features"' do
71
71
  it 'should work' do
72
72
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
73
73
  end
74
74
  end
75
75
 
76
- describe 'test attribute "titles"' do
76
+ describe 'test attribute "tags"' do
77
77
  it 'should work' do
78
78
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
79
79
  end
80
80
  end
81
81
 
82
- describe 'test attribute "tracks"' do
82
+ describe 'test attribute "spotify_id"' do
83
83
  it 'should work' do
84
84
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
85
85
  end
86
86
  end
87
87
 
88
- describe 'test attribute "musical_features"' do
88
+ describe 'test attribute "pline"' do
89
89
  it 'should work' do
90
90
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
91
91
  end
92
92
  end
93
93
 
94
- describe 'test attribute "tags"' do
94
+ describe 'test attribute "genre_predictions"' do
95
95
  it 'should work' do
96
96
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
97
97
  end