I've been testing the API responses from arab, and I've noticed some inexcusable inconsistencies that are driving me crazy. For some endpoints, the response structure changes randomly based on the input parameters, which makes it nearly impossible to build a reliable client around it. Why can't we have a standardized response structure?
For example, I expected the same fields in the response for various related endpoints, but sometimes they include additional metadata, and other times they don't. This is beyond frustrating. Can we please sort this out?
Additionally, I've found no clear way to handle errors effectively because responses don't reliably include status codes or error messages. It's a complete mess. I shouldn't have to check every response for changes in structure. This is not how API design should work! If we could standardize the response format, it would save us all a lot of headaches.
Can anyone else confirm this behavior? When is this going to be addressed?
I've been testing the API responses from arab, and I've noticed some inexcusable inconsistencies that are driving me crazy. For some endpoints, the response structure changes randomly based on the input parameters, which makes it nearly impossible to build a reliable client around it. Why can't we have a standardized response structure?
For example, I expected the same fields in the response for various related endpoints, but sometimes they include additional metadata, and other times they don't. This is beyond frustrating. Can we please sort this out?
Additionally, I've found no clear way to handle errors effectively because responses don't reliably include status codes or error messages. It's a complete mess. I shouldn't have to check every response for changes in structure. This is not how API design should work! If we could standardize the response format, it would save us all a lot of headaches.
Can anyone else confirm this behavior? When is this going to be addressed?