The CLI often surfaces generic errors instead of clear, actionable messages. This has come up from both customer feedback and internal usage.
Example: Running apimatic portal serve while logged out returns:
"An unexpected error occurred, please try again later. If the problem persists, please reach out to our team at support@apimatic.io"
The same endpoint called via Postman without an auth header returns a much clearer response:
{ "message": "Authorization has been denied for this request." }What we want: Surface the specific underlying error and pair it with a suggested fix (e.g., prompt the user to log in) so troubleshooting is faster.
Context: Reported multiple times and flagged as a recurring pain point. Source: apimatic/apimatic-customer-support#331
The CLI often surfaces generic errors instead of clear, actionable messages. This has come up from both customer feedback and internal usage.
Example: Running
apimatic portal servewhile logged out returns:The same endpoint called via Postman without an auth header returns a much clearer response:
{ "message": "Authorization has been denied for this request." }What we want: Surface the specific underlying error and pair it with a suggested fix (e.g., prompt the user to log in) so troubleshooting is faster.
Context: Reported multiple times and flagged as a recurring pain point. Source: apimatic/apimatic-customer-support#331