waldur-api

To retrieve Waldur OpenAPI endpoints and schemas, use this skill to parse the waldur-openapi.json spec, resolving JSON references to deliver formatted endpoint overviews and detailed operation docs for integration tasks.

Waldur API endpoint lookup covers domains including customers, projects, marketplace, invoices, authentication, and compute providers, extracting operation IDs and schemas from the OpenAPI specification for development reference.

Yes, you need the waldur-openapi.json file placed in the repository root. It must exist and be up-to-date, serving as the source of truth for resolving JSON references and formatting consistent API endpoint documentation.

The best way to document Waldur API operation details is parsing the OpenAPI specification to extract operation IDs, schemas, and endpoints, then formatting them into an organized, developer-friendly API reference document.

Waldur API schema lookup fails or returns inconsistent data if the waldur-openapi.json file is outdated because this skill uses that file as the single source of truth to resolve JSON references and generate endpoint documentation.

Yes, you can generate a developer-friendly API reference for Waldur marketplace and invoice endpoints by parsing the OpenAPI spec to fetch operation details, schemas, and endpoint overviews across those specific domains.