{"note":"OpenAPI conversion -- returning structured metadata","name":"ebay-com-developer-analytics","description":"Analytics API","version":"v1_beta.0.1","base_url":"https://api.ebay.com/developer/analytics/v1_beta","endpoints":2,"raw":"@lap v0.3\n# Machine-readable API spec. Each @endpoint block is one API call.\n@api Analytics API\n@base https://api.ebay.com/developer/analytics/v1_beta\n@version v1_beta.0.1\n@auth OAuth2\n@endpoints 2\n@toc rate_limit(1), user_rate_limit(1)\n\n@group rate_limit\n@endpoint GET /rate_limit/\n@desc This method retrieves the call limit and utilization data for an application. The data is retrieved for all RESTful APIs and the legacy Trading API.  The response from getRateLimits includes a list of the applicable resources and the \"call limit\", or quota, that is set for each resource. In addition to quota information, the response also includes the number of remaining calls available before the limit is reached, the time remaining before the quota resets, the number of calls made to the specific resource, and the length of the \"time window\" to which the quota applies.  By default, this method returns utilization data for all RESTful API and the legacy Trading API resources. Use the api_name and api_context query parameters to filter the response to only the desired APIs.  For more on call limits, see Application Growth Check.\n@optional {api_context: str # This optional query parameter filters the result to include only the specified API context. Valid values: buysell commercedevelopertradingapi, api_name: str # This optional query parameter filters the result to include only the APIs specified. Example values:  browse for the Buy APIs inventory for the Sell APIs  taxonomy for the Commerce APIs  tradingapi for the Trading APIs}\n@returns(200) {rateLimits: [map]} # OK\n@returns(204) No Content\n@errors {500: Internal Server Error}\n\n@endgroup\n\n@group user_rate_limit\n@endpoint GET /user_rate_limit/\n@desc This method retrieves the call limit and utilization data for an application user. The call-limit data is returned for all RESTful APIs and the legacy Trading API that limit calls on a per-user basis.  The response from getUserRateLimits includes a list of the applicable resources and the \"call limit\", or quota, that is set for each resource. In addition to quota information, the response also includes the number of remaining calls available before the limit is reached, the time remaining before the quota resets, the number of calls made to the specific resource, and the length of the \"time window\" to which the quota applies.  By default, this method returns utilization data for all RESTful APIs resources and the legacy Trading API calls that limit request access by user. Use the api_name and api_context query parameters to filter the response to only the desired APIs.  For more on call limits, see Application Growth Check.\n@optional {api_context: str # This optional query parameter filters the result to include only the specified API context. Valid values: buy sell commerce developer tradingapi, api_name: str # This optional query parameter filters the result to include only the APIs specified. Example values: browse for the Buy APIs inventory for the Sell APIs  taxonomy for the Commerce APIs  tradingapi for the Trading APIs}\n@returns(200) {rateLimits: [map]} # OK\n@returns(204) No Content\n@errors {500: Internal Server Error}\n\n@endgroup\n\n@end\n"}