OpenAPI Spec Out of Sync with Actual API Behavior #35

Closed
opened 2026-04-05 16:18:44 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @atippin1 on 3/12/2026

Describe the bug
The OpenAPI specification is out of sync with the actual API behavior. As an example,the /monitor-custom-field/get-list endpoint accepts limit and skip query parameters (as documented at https://oneuptime.com/reference/monitor), but these parameters are not defined in the OpenAPI spec.

Steps to reproduce the behavior:

Generate an API client from the OneUptime OpenAPI specification
Attempt to use the generated client to call /monitor-custom-field/get-list with limit and skip parameters
Observe that the generated client does not support these parameters
Compare with the actual API documentation at https://oneuptime.com/reference/monitor

Expected behavior
The OpenAPI specification should include all query parameters that the API accepts, including limit and skip for pagination on the /monitor-custom-field/get-list endpoint. API clients generated from the spec should be fully functional.
Deployment Type
This affects both SaaS (at https://oneuptime.com/) and self-hosted deployments, as it's a specification issue.
Additional context
This discrepancy causes API clients generated from the OpenAPI spec to be incomplete and non-functional for pagination use cases. Other endpoints may have similar issues.

*Originally created by @atippin1 on 3/12/2026* **Describe the bug** The OpenAPI specification is out of sync with the actual API behavior. As an example,the /monitor-custom-field/get-list endpoint accepts limit and skip query parameters (as documented at https://oneuptime.com/reference/monitor), but these parameters are not defined in the OpenAPI spec. **Steps to reproduce the behavior:** Generate an API client from the OneUptime OpenAPI specification Attempt to use the generated client to call /monitor-custom-field/get-list with limit and skip parameters Observe that the generated client does not support these parameters Compare with the actual API documentation at https://oneuptime.com/reference/monitor **Expected behavior** The OpenAPI specification should include all query parameters that the API accepts, including limit and skip for pagination on the /monitor-custom-field/get-list endpoint. API clients generated from the spec should be fully functional. **Deployment Type** This affects both SaaS (at https://oneuptime.com/) and self-hosted deployments, as it's a specification issue. **Additional context** This discrepancy causes API clients generated from the OpenAPI spec to be incomplete and non-functional for pagination use cases. Other endpoints may have similar issues.
MrUnknownDE added the bugbugbugbugbugbug labels 2026-04-05 16:18:44 +02:00
Sign in to join this conversation.
No Label bug bug bug bug bug bug
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/oneuptime#35