You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Documentation error: Request Body shows [undefined] in multiple endpoints #474
This issue is not limited to the export endpoint — it also occurs in other endpoints across the documentation, making it unclear what parameters are required.
When testing the endpoints, if required fields (such as "query") are not provided, the API responds with errors like:
Invalid payload. "query" is required
This indicates that the documentation is not showing the actual required body structure.
Expected behavior
Documentation should display the correct request body schema for each endpoint.
Required fields (e.g., "query") should be clearly indicated with their format.
Current behavior
Request Body sections show [undefined].
The API rejects requests when mandatory fields are missing.
To Reproduce
Steps to Reproduce
Open Postman.
Make a request to the affected endpoint (e.g., export) using valid credentials.
Check the official documentation for the endpoint.
Observe that the Request Body is displayed as [undefined].
Send the request without "query" and see the error response.
Activity
linear commentedon Oct 3, 2025
CMS-1380
linear commentedon Oct 3, 2025
EDU-491
joselcvarela commentedon Oct 24, 2025
For the case of
POST /utils/export/{collection}(Export Data to a File) it looks like the body requiresqueryandformatfix(api): declare object schema on utility request bodies