I've experienced some pain as both an API consumer and provider. There are lots of consequential pains, these are the "main" ones IMO. I'm curious if anybody else resonates with these problems:
1. As a consumer and provider: Having to look at/manage different services for API docs, status, and change-logs.
2. As a consumer: Being able to subscribe to API statuses but typically not API docs (e.g. email me for a major API change).
3. As a provider: API documentation generation tools being heavy (cloning repos, running scripts, self-hosting, etc rather than having a nice hosted web UI) and inaccessible to non-engineers.
Without going too deep, as a provider, Swagger has been a godsend for help with documentation, request examples, and a nice web UI for front-end developers to test against.
I've experienced some pain as both an API consumer and provider. There are lots of consequential pains, these are the "main" ones IMO. I'm curious if anybody else resonates with these problems:
1. As a consumer and provider: Having to look at/manage different services for API docs, status, and change-logs.
2. As a consumer: Being able to subscribe to API statuses but typically not API docs (e.g. email me for a major API change).
3. As a provider: API documentation generation tools being heavy (cloning repos, running scripts, self-hosting, etc rather than having a nice hosted web UI) and inaccessible to non-engineers.