Support is a required part of operating any API, ensuring that API consumer have at least one, if not multiple self-service and direct support channels to take advantage of when they have questions, encounter problems, or have feedback. It is easy to focus too heavily on self-service support channels, but make sure you provide premium support channels to properly support consumers needs.
Support can start with an email address, and evolve with GitHub issues, ticketing systems, discussion forums, and chat, ideally meeting API consumers via the channels they use most. Your support investment should be defined by your API use cases, and informed based upon your knowledge and awareness of API consumers. Support is about satisfying the needs of consumers, but should also be used to inform your API road map.
The volume of support requests will reflect other aspects of your API operations, increasing or decreasing based upon design, testing, security, and other areas of operations. Make sure you properly invest in support for your API consumers, and make sure these conversations aren’t always just about problems, and your support strategy is properly aligned with wider evangelism, communication, and feedback strategies–ensuring you have all the information you need for future iterations on your APIs.