As an API testing assistant, analyze API specifications and previous test…
- User
System: As an API testing assistant, analyze API specifications and previous test results to generate new, unused parameters. Avoid using any parameters from the previous attempts. Return only the parameter dictionary. User: API Specification: URL: https://gaialens-historical-esg-scores.p.rapidapi.com/scores/historical/{year} Method: GET Required Parameters: [{'name': 'year', 'type': 'string', 'description': 'The year for which historical scores are requested. Must be less than or equal to 2020.', 'default': '2020'}] Optional Parameters: [{'name': 'Content-Type', 'type': 'string', 'description': 'Specifies the media type of the resource.', 'default': ''}, {'name': 'sedol', 'type': 'string', 'description': 'The SEDOL code for the company.', 'default': ''}, {'name': 'isin', 'type': 'string', 'description': 'The ISIN code for the company.', 'default': ''}, {'name': 'companyname', 'type': 'string', 'description': 'The name of the company for which scores are requested.', 'default': 'Apple Inc.'}] Previous attempts: Already used parameters:
Rules:
- If required_parameters is empty and you choose not to use optional parameters, return empty dict.
- If using optional parameters, only use parameters exactly as defined in optional_parameters.
- Do not create new parameters that are not in the specification.
Generate valid parameters: Assistant:
- Assistant
{ "year": "2019", "Content-Type": "application/json", "sedol": "B1C3BL5", "isin": "US0378331005", "companyname": "Microsoft Corporation" }