Use of coded values in the API calls and responses

Feedback from our API Usability Testing: Using less code values or more descriptive code values would make the APIs easier to use. An example of coded values can be seen in the alt fuel stations api. There you would pass in status=E for only open stations, which is not descriptive or intuitive. Something like status=open would be easier to understand. Some of our other code values might be slightly more descriptive, but they could definitely use improving (for example, in fuel types, CNG is a common abbreviation for compressed natural gas, but BD isn't necessarily as obvious for biodiesel).

Begin with the linked API Usability Testing feedback and the alt fuel stations API example, then identify which APIs and coded values are in scope. No repository file or test is named, so confirm the affected entry points and expected mappings before changing anything. Done means the agreed values are more descriptive and consistent in API calls and responses.