The name of each API should be simple, intuitive, and speak to what is possible with an API, not the technology behind the API. Naming is hard, so take a moment to consider what some one wasn’t involved in producing the API will think when they read the name. Is it something you could say to someone and it will make sense?
The name of your API should speak to the business use cases it covers, and is what will show up in your API catalog, directory, and search results. Think about how you can align the naming of your APIs across domain, line of business, or team, as part of a wider API product strategy.
The name of an API should be a collaborative effort between product and engineering stakeholders, with the consumers of the API in mind. The name of an API is likely not to change, so take the time to consider what the right name is as part of the design stage along with other naming, paths, and tagging.