songtradr_api_client_ruby 2.0.0 → 2.1.0

data/lib/songtradr_api_client_ruby/api/user_api.rb

@@ -3,10 +3,10 @@
 
 #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.
 
-The version of the OpenAPI document: 2.0.0
+The version of the OpenAPI document: 2.1.0
 Contact: info@songtradr.com
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 7.4.0-SNAPSHOT
+Generator version: 7.5.0-SNAPSHOT
 
 =end
 
@@ -781,6 +781,300 @@ module SongtradrApiClientRuby
       return data, status_code, headers
     end
 
+    # Similar recordings for a list of user recordings.
+    # @param ids [String] Comma seperated list of IDs. Can be ISRCs or proprietary IDs
+    # @param [Hash] opts the optional parameters
+    # @option opts [Boolean] :identical_only Whether a result list shall include only identical recordings. (default to false)
+    # @option opts [String] :usage Filter by recording usage.
+    # @return [Array<RecordingForSimilaritySearchDTO>]
+    def recordings_by_ids_with_similarities(ids, opts = {})
+      data, _status_code, _headers = recordings_by_ids_with_similarities_with_http_info(ids, opts)
+      data
+    end
+
+    # Similar recordings for a list of user recordings.
+    # @param ids [String] Comma seperated list of IDs. Can be ISRCs or proprietary IDs
+    # @param [Hash] opts the optional parameters
+    # @option opts [Boolean] :identical_only Whether a result list shall include only identical recordings. (default to false)
+    # @option opts [String] :usage Filter by recording usage.
+    # @return [Array<(Array<RecordingForSimilaritySearchDTO>, Integer, Hash)>] Array<RecordingForSimilaritySearchDTO> data, response status code and response headers
+    def recordings_by_ids_with_similarities_with_http_info(ids, opts = {})
+      if @api_client.config.debugging
+        @api_client.config.logger.debug 'Calling API: UserApi.recordings_by_ids_with_similarities ...'
+      end
+      # verify the required parameter 'ids' is set
+      if @api_client.config.client_side_validation && ids.nil?
+        fail ArgumentError, "Missing the required parameter 'ids' when calling UserApi.recordings_by_ids_with_similarities"
+      end
+      # resource path
+      local_var_path = '/api/v1/user/recording/{ids}/similarities'.sub('{' + 'ids' + '}', CGI.escape(ids.to_s))
+
+      # query parameters
+      query_params = opts[:query_params] || {}
+      query_params[:'identicalOnly'] = opts[:'identical_only'] if !opts[:'identical_only'].nil?
+      query_params[:'usage'] = opts[:'usage'] if !opts[:'usage'].nil?
+
+      # header parameters
+      header_params = opts[:header_params] || {}
+      # HTTP header 'Accept' (if needed)
+      header_params['Accept'] = @api_client.select_header_accept(['application/json'])
+
+      # form parameters
+      form_params = opts[:form_params] || {}
+
+      # http body (model)
+      post_body = opts[:debug_body]
+
+      # return_type
+      return_type = opts[:debug_return_type] || 'Array<RecordingForSimilaritySearchDTO>'
+
+      # auth_names
+      auth_names = opts[:debug_auth_names] || ['bearer-jwt']
+
+      new_options = opts.merge(
+        :operation => :"UserApi.recordings_by_ids_with_similarities",
+        :header_params => header_params,
+        :query_params => query_params,
+        :form_params => form_params,
+        :body => post_body,
+        :auth_names => auth_names,
+        :return_type => return_type
+      )
+
+      data, status_code, headers = @api_client.call_api(:GET, local_var_path, new_options)
+      if @api_client.config.debugging
+        @api_client.config.logger.debug "API called: UserApi#recordings_by_ids_with_similarities\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}"
+      end
+      return data, status_code, headers
+    end
+
+    # Timeseries of AI generated moods, musical features and more for a list of recordings.
+    # @param ids [String] Comma seperated list of IDs. Can be ISRCs or proprietary IDs
+    # @param [Hash] opts the optional parameters
+    # @option opts [String] :category_name Show only taggrams for one category.
+    # @option opts [String] :tag_name Show only taggrams for one tag.
+    # @option opts [String] :genre_name Show only taggrams for one genre.
+    # @option opts [Float] :from_timestamp Show only taggrams data starting from from this timestamp in seconds.
+    # @option opts [Float] :to_timestamp Show only taggrams data before this timestamp in seconds.
+    # @option opts [Boolean] :fill_with_zero If set to true, empty timeseries are filled with timeseries of 0.0 values.
+    # @return [Array<RecordingMinimalWithTaggramsDTO>]
+    def recordings_by_ids_with_taggrams(ids, opts = {})
+      data, _status_code, _headers = recordings_by_ids_with_taggrams_with_http_info(ids, opts)
+      data
+    end
+
+    # Timeseries of AI generated moods, musical features and more for a list of recordings.
+    # @param ids [String] Comma seperated list of IDs. Can be ISRCs or proprietary IDs
+    # @param [Hash] opts the optional parameters
+    # @option opts [String] :category_name Show only taggrams for one category.
+    # @option opts [String] :tag_name Show only taggrams for one tag.
+    # @option opts [String] :genre_name Show only taggrams for one genre.
+    # @option opts [Float] :from_timestamp Show only taggrams data starting from from this timestamp in seconds.
+    # @option opts [Float] :to_timestamp Show only taggrams data before this timestamp in seconds.
+    # @option opts [Boolean] :fill_with_zero If set to true, empty timeseries are filled with timeseries of 0.0 values.
+    # @return [Array<(Array<RecordingMinimalWithTaggramsDTO>, Integer, Hash)>] Array<RecordingMinimalWithTaggramsDTO> data, response status code and response headers
+    def recordings_by_ids_with_taggrams_with_http_info(ids, opts = {})
+      if @api_client.config.debugging
+        @api_client.config.logger.debug 'Calling API: UserApi.recordings_by_ids_with_taggrams ...'
+      end
+      # verify the required parameter 'ids' is set
+      if @api_client.config.client_side_validation && ids.nil?
+        fail ArgumentError, "Missing the required parameter 'ids' when calling UserApi.recordings_by_ids_with_taggrams"
+      end
+      allowable_values = ["instrument", "vocals", "energy", "soundGeneration", "rhythm", "songRating", "performanceRating", "productionRating", "moodCluster", "tonality", "arousal", "valence", "pleasantness", "engagement", "timbre", "roughness", "harmony", "texture", "groovyness", "space", "audienceAge", "audienceRegion", "audienceGender", "originRegion", "originDecade", "languageOfPerformance", "level1Genre", "level2Genre", "curateability", "useCase", "channelSuitability", "industrySuitability", "loudness"]
+      if @api_client.config.client_side_validation && opts[:'category_name'] && !allowable_values.include?(opts[:'category_name'])
+        fail ArgumentError, "invalid value for \"category_name\", must be one of #{allowable_values}"
+      end
+      # resource path
+      local_var_path = '/api/v1/user/recording/{ids}/taggrams'.sub('{' + 'ids' + '}', CGI.escape(ids.to_s))
+
+      # query parameters
+      query_params = opts[:query_params] || {}
+      query_params[:'categoryName'] = opts[:'category_name'] if !opts[:'category_name'].nil?
+      query_params[:'tagName'] = opts[:'tag_name'] if !opts[:'tag_name'].nil?
+      query_params[:'genreName'] = opts[:'genre_name'] if !opts[:'genre_name'].nil?
+      query_params[:'fromTimestamp'] = opts[:'from_timestamp'] if !opts[:'from_timestamp'].nil?
+      query_params[:'toTimestamp'] = opts[:'to_timestamp'] if !opts[:'to_timestamp'].nil?
+      query_params[:'fillWithZero'] = opts[:'fill_with_zero'] if !opts[:'fill_with_zero'].nil?
+
+      # header parameters
+      header_params = opts[:header_params] || {}
+      # HTTP header 'Accept' (if needed)
+      header_params['Accept'] = @api_client.select_header_accept(['application/json'])
+
+      # form parameters
+      form_params = opts[:form_params] || {}
+
+      # http body (model)
+      post_body = opts[:debug_body]
+
+      # return_type
+      return_type = opts[:debug_return_type] || 'Array<RecordingMinimalWithTaggramsDTO>'
+
+      # auth_names
+      auth_names = opts[:debug_auth_names] || ['bearer-jwt']
+
+      new_options = opts.merge(
+        :operation => :"UserApi.recordings_by_ids_with_taggrams",
+        :header_params => header_params,
+        :query_params => query_params,
+        :form_params => form_params,
+        :body => post_body,
+        :auth_names => auth_names,
+        :return_type => return_type
+      )
+
+      data, status_code, headers = @api_client.call_api(:GET, local_var_path, new_options)
+      if @api_client.config.debugging
+        @api_client.config.logger.debug "API called: UserApi#recordings_by_ids_with_taggrams\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}"
+      end
+      return data, status_code, headers
+    end
+
+    # Strengths as numerical representations for AI generated moods, musical features and more for recordings.
+    # @param ids [String] Comma seperated list of IDs. Can be ISRCs or proprietary IDs
+    # @param [Hash] opts the optional parameters
+    # @option opts [String] :category_name Show only taggrams for one category.
+    # @option opts [String] :tag_name Show only taggrams for one tag.
+    # @option opts [String] :genre_name Show only taggrams for one genre.
+    # @return [Array<RecordingMinimalWithTagstrengthsDTO>]
+    def recordings_by_ids_with_tagstrengths(ids, opts = {})
+      data, _status_code, _headers = recordings_by_ids_with_tagstrengths_with_http_info(ids, opts)
+      data
+    end
+
+    # Strengths as numerical representations for AI generated moods, musical features and more for recordings.
+    # @param ids [String] Comma seperated list of IDs. Can be ISRCs or proprietary IDs
+    # @param [Hash] opts the optional parameters
+    # @option opts [String] :category_name Show only taggrams for one category.
+    # @option opts [String] :tag_name Show only taggrams for one tag.
+    # @option opts [String] :genre_name Show only taggrams for one genre.
+    # @return [Array<(Array<RecordingMinimalWithTagstrengthsDTO>, Integer, Hash)>] Array<RecordingMinimalWithTagstrengthsDTO> data, response status code and response headers
+    def recordings_by_ids_with_tagstrengths_with_http_info(ids, opts = {})
+      if @api_client.config.debugging
+        @api_client.config.logger.debug 'Calling API: UserApi.recordings_by_ids_with_tagstrengths ...'
+      end
+      # verify the required parameter 'ids' is set
+      if @api_client.config.client_side_validation && ids.nil?
+        fail ArgumentError, "Missing the required parameter 'ids' when calling UserApi.recordings_by_ids_with_tagstrengths"
+      end
+      allowable_values = ["instrument", "vocals", "energy", "soundGeneration", "rhythm", "songRating", "performanceRating", "productionRating", "moodCluster", "tonality", "arousal", "valence", "pleasantness", "engagement", "timbre", "roughness", "harmony", "texture", "groovyness", "space", "audienceAge", "audienceRegion", "audienceGender", "originRegion", "originDecade", "languageOfPerformance", "level1Genre", "level2Genre", "curateability", "useCase", "channelSuitability", "industrySuitability", "loudness"]
+      if @api_client.config.client_side_validation && opts[:'category_name'] && !allowable_values.include?(opts[:'category_name'])
+        fail ArgumentError, "invalid value for \"category_name\", must be one of #{allowable_values}"
+      end
+      # resource path
+      local_var_path = '/api/v1/user/recording/{ids}/tagstrengths'.sub('{' + 'ids' + '}', CGI.escape(ids.to_s))
+
+      # query parameters
+      query_params = opts[:query_params] || {}
+      query_params[:'categoryName'] = opts[:'category_name'] if !opts[:'category_name'].nil?
+      query_params[:'tagName'] = opts[:'tag_name'] if !opts[:'tag_name'].nil?
+      query_params[:'genreName'] = opts[:'genre_name'] if !opts[:'genre_name'].nil?
+
+      # header parameters
+      header_params = opts[:header_params] || {}
+      # HTTP header 'Accept' (if needed)
+      header_params['Accept'] = @api_client.select_header_accept(['application/json'])
+
+      # form parameters
+      form_params = opts[:form_params] || {}
+
+      # http body (model)
+      post_body = opts[:debug_body]
+
+      # return_type
+      return_type = opts[:debug_return_type] || 'Array<RecordingMinimalWithTagstrengthsDTO>'
+
+      # auth_names
+      auth_names = opts[:debug_auth_names] || ['bearer-jwt']
+
+      new_options = opts.merge(
+        :operation => :"UserApi.recordings_by_ids_with_tagstrengths",
+        :header_params => header_params,
+        :query_params => query_params,
+        :form_params => form_params,
+        :body => post_body,
+        :auth_names => auth_names,
+        :return_type => return_type
+      )
+
+      data, status_code, headers = @api_client.call_api(:GET, local_var_path, new_options)
+      if @api_client.config.debugging
+        @api_client.config.logger.debug "API called: UserApi#recordings_by_ids_with_tagstrengths\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}"
+      end
+      return data, status_code, headers
+    end
+
+    # Recordings by IDs with a medium sized response.
+    # @param ids [String] Comma seperated list of IDs. Can be ISRCs or proprietary IDs
+    # @param [Hash] opts the optional parameters
+    # @option opts [Integer] :page Zero-based page index (0..N) (default to 0)
+    # @option opts [Integer] :size The size of the page to be returned (default to 20)
+    # @option opts [Array<String>] :sort Sorting criteria in the format: property,(asc|desc). Default sort order is ascending. Multiple sort criteria are supported.
+    # @return [Array<RecordingMediumDTO>]
+    def recordings_medium_by_ids(ids, opts = {})
+      data, _status_code, _headers = recordings_medium_by_ids_with_http_info(ids, opts)
+      data
+    end
+
+    # Recordings by IDs with a medium sized response.
+    # @param ids [String] Comma seperated list of IDs. Can be ISRCs or proprietary IDs
+    # @param [Hash] opts the optional parameters
+    # @option opts [Integer] :page Zero-based page index (0..N) (default to 0)
+    # @option opts [Integer] :size The size of the page to be returned (default to 20)
+    # @option opts [Array<String>] :sort Sorting criteria in the format: property,(asc|desc). Default sort order is ascending. Multiple sort criteria are supported.
+    # @return [Array<(Array<RecordingMediumDTO>, Integer, Hash)>] Array<RecordingMediumDTO> data, response status code and response headers
+    def recordings_medium_by_ids_with_http_info(ids, opts = {})
+      if @api_client.config.debugging
+        @api_client.config.logger.debug 'Calling API: UserApi.recordings_medium_by_ids ...'
+      end
+      # verify the required parameter 'ids' is set
+      if @api_client.config.client_side_validation && ids.nil?
+        fail ArgumentError, "Missing the required parameter 'ids' when calling UserApi.recordings_medium_by_ids"
+      end
+      # resource path
+      local_var_path = '/api/v1/user/recording/{ids}'.sub('{' + 'ids' + '}', CGI.escape(ids.to_s))
+
+      # query parameters
+      query_params = opts[:query_params] || {}
+      query_params[:'page'] = opts[:'page'] if !opts[:'page'].nil?
+      query_params[:'size'] = opts[:'size'] if !opts[:'size'].nil?
+      query_params[:'sort'] = @api_client.build_collection_param(opts[:'sort'], :multi) if !opts[:'sort'].nil?
+
+      # header parameters
+      header_params = opts[:header_params] || {}
+      # HTTP header 'Accept' (if needed)
+      header_params['Accept'] = @api_client.select_header_accept(['application/json'])
+
+      # form parameters
+      form_params = opts[:form_params] || {}
+
+      # http body (model)
+      post_body = opts[:debug_body]
+
+      # return_type
+      return_type = opts[:debug_return_type] || 'Array<RecordingMediumDTO>'
+
+      # auth_names
+      auth_names = opts[:debug_auth_names] || ['bearer-jwt']
+
+      new_options = opts.merge(
+        :operation => :"UserApi.recordings_medium_by_ids",
+        :header_params => header_params,
+        :query_params => query_params,
+        :form_params => form_params,
+        :body => post_body,
+        :auth_names => auth_names,
+        :return_type => return_type
+      )
+
+      data, status_code, headers = @api_client.call_api(:GET, local_var_path, new_options)
+      if @api_client.config.debugging
+        @api_client.config.logger.debug "API called: UserApi#recordings_medium_by_ids\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}"
+      end
+      return data, status_code, headers
+    end
+
     # Sign up a new user.
     # @param save_user_dto [SaveUserDTO] 
     # @param [Hash] opts the optional parameters

data/lib/songtradr_api_client_ruby/api_client.rb

@@ -3,10 +3,10 @@
 
 #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.
 
-The version of the OpenAPI document: 2.0.0
+The version of the OpenAPI document: 2.1.0
 Contact: info@songtradr.com
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 7.4.0-SNAPSHOT
+Generator version: 7.5.0-SNAPSHOT
 
 =end
 
@@ -17,7 +17,7 @@ require 'tempfile'
 require 'time'
 require 'faraday'
 require 'faraday/multipart' if Gem::Version.new(Faraday::VERSION) >= Gem::Version.new('2.0')
-require 'filemagic'
+require 'marcel'
 
 
 module SongtradrApiClientRuby
@@ -141,8 +141,7 @@ module SongtradrApiClientRuby
         form_params.each do |key, value|
           case value
           when ::File, ::Tempfile
-            filemagic = FileMagic.new(FileMagic::MAGIC_MIME)
-            data[key] = Faraday::FilePart.new(value.path, filemagic.file(value.path, true))
+            data[key] = Faraday::FilePart.new(value.path, Marcel::MimeType.for(Pathname.new(value.path)))
           when ::Array, nil
             # let Faraday handle Array and nil parameters
             data[key] = value

data/lib/songtradr_api_client_ruby/api_error.rb

@@ -3,10 +3,10 @@
 
 #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.
 
-The version of the OpenAPI document: 2.0.0
+The version of the OpenAPI document: 2.1.0
 Contact: info@songtradr.com
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 7.4.0-SNAPSHOT
+Generator version: 7.5.0-SNAPSHOT
 
 =end
 

data/lib/songtradr_api_client_ruby/configuration.rb

@@ -3,10 +3,10 @@
 
 #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.
 
-The version of the OpenAPI document: 2.0.0
+The version of the OpenAPI document: 2.1.0
 Contact: info@songtradr.com
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 7.4.0-SNAPSHOT
+Generator version: 7.5.0-SNAPSHOT
 
 =end
 

data/lib/songtradr_api_client_ruby/models/category_medium_dto.rb

@@ -3,10 +3,10 @@
 
 #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.
 
-The version of the OpenAPI document: 2.0.0
+The version of the OpenAPI document: 2.1.0
 Contact: info@songtradr.com
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 7.4.0-SNAPSHOT
+Generator version: 7.5.0-SNAPSHOT
 
 =end
 

data/lib/songtradr_api_client_ruby/models/category_minimal_dto.rb

@@ -3,10 +3,10 @@
 
 #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.
 
-The version of the OpenAPI document: 2.0.0
+The version of the OpenAPI document: 2.1.0
 Contact: info@songtradr.com
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 7.4.0-SNAPSHOT
+Generator version: 7.5.0-SNAPSHOT
 
 =end
 

data/lib/songtradr_api_client_ruby/models/config_access_dto.rb

@@ -3,10 +3,10 @@
 
 #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.
 
-The version of the OpenAPI document: 2.0.0
+The version of the OpenAPI document: 2.1.0
 Contact: info@songtradr.com
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 7.4.0-SNAPSHOT
+Generator version: 7.5.0-SNAPSHOT
 
 =end
 

data/lib/songtradr_api_client_ruby/models/config_identifier_dto.rb

@@ -3,10 +3,10 @@
 
 #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.
 
-The version of the OpenAPI document: 2.0.0
+The version of the OpenAPI document: 2.1.0
 Contact: info@songtradr.com
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 7.4.0-SNAPSHOT
+Generator version: 7.5.0-SNAPSHOT
 
 =end
 

data/lib/songtradr_api_client_ruby/models/contributor_type_dto.rb

@@ -3,10 +3,10 @@
 
 #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.
 
-The version of the OpenAPI document: 2.0.0
+The version of the OpenAPI document: 2.1.0
 Contact: info@songtradr.com
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 7.4.0-SNAPSHOT
+Generator version: 7.5.0-SNAPSHOT
 
 =end
 

data/lib/songtradr_api_client_ruby/models/error_response.rb

@@ -3,10 +3,10 @@
 
 #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.
 
-The version of the OpenAPI document: 2.0.0
+The version of the OpenAPI document: 2.1.0
 Contact: info@songtradr.com
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 7.4.0-SNAPSHOT
+Generator version: 7.5.0-SNAPSHOT
 
 =end
 

data/lib/songtradr_api_client_ruby/models/field_summary_dto.rb

@@ -3,10 +3,10 @@
 
 #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.
 
-The version of the OpenAPI document: 2.0.0
+The version of the OpenAPI document: 2.1.0
 Contact: info@songtradr.com
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 7.4.0-SNAPSHOT
+Generator version: 7.5.0-SNAPSHOT
 
 =end
 

data/lib/songtradr_api_client_ruby/models/file_dto.rb

@@ -3,10 +3,10 @@
 
 #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.
 
-The version of the OpenAPI document: 2.0.0
+The version of the OpenAPI document: 2.1.0
 Contact: info@songtradr.com
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 7.4.0-SNAPSHOT
+Generator version: 7.5.0-SNAPSHOT
 
 =end
 

data/lib/songtradr_api_client_ruby/models/file_list_dto.rb

@@ -3,10 +3,10 @@
 
 #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.
 
-The version of the OpenAPI document: 2.0.0
+The version of the OpenAPI document: 2.1.0
 Contact: info@songtradr.com
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 7.4.0-SNAPSHOT
+Generator version: 7.5.0-SNAPSHOT
 
 =end