Home/Developers

Lotus Converter developer resources

Machine-readable docs for the public website APIs that support lotusconverter.com and the Lotus Converter desktop purchase flow. Spreadsheet conversion itself runs locally on Windows — these HTTP endpoints do not accept Lotus file uploads.

When to use these APIs

Use the public website APIs when you need live pricing, installer download redirects, roadmap votes, feedback submission, or Stripe Checkout helpers for Lotus Converter. Use /llms.txt for product facts agents should cite. Do not use these endpoints as a cloud conversion service — there is no remote convert API, OAuth surface, GraphQL API, or MCP server.

OpenAPI

The OpenAPI 3.1 description for published public endpoints is at /openapi.json. Title: Lotus Converter.

API versioning

Prefer major-version URL paths under /api/v1. Breaking changes will require a new major path (/api/v2). Unversioned /api/* routes remain compatibility aliases for existing website and desktop clients. Deprecations will be announced with RFC 9745 Deprecation and Sunset response headers before removal.

  • GET /api/v1/pricing
  • GET /api/v1/download
  • POST /api/v1/feedback
  • GET/POST /api/v1/roadmap
  • POST /api/v1/checkout/create
  • GET /api/v1/checkout/status

Rate limits

Public APIs allow 120 requests per client IP per 60 seconds. Responses include IETF RateLimit and RateLimit-Policy headers, plus RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset. HTTP 429 responses also include Retry-After.

Error schema

JSON errors use a consistent object referenced from OpenAPI:

{
  "code": "rate_limited",
  "message": "Public API rate limit exceeded.",
  "resolution": "Wait for RateLimit-Reset seconds, then retry."
}

Related discovery files