Verified OpenAPI status
No OpenAPI document is published yet. ReplyNodes will publish a versioned contract only after it is exported from the authoritative backend schema and verified against the public REST API.
Current blocker
The owning system is the private replynodes/replynodes-app backend, specifically apps/backend/src/public-api/routes/v1/public.integrations.controller.ts. It exposes the REST route prefix, but does not currently export a complete OpenAPI document with authoritative request and response schemas. A hand-authored spec would be unsafe because it could invent operations, payloads, responses, or authentication behavior.
Safe validation probe
The OpenAPI gate performs a fixed GET request to https://app.replynodes.com/api/public/v1/posts with no credentials and asserts HTTP 401. It follows no redirects and sends no mutating method or request body. This proves only that the documented route is reachable and rejects an unauthenticated read; it does not prove request/response schemas, authenticated behavior, every operation, rate limits, or a complete OpenAPI contract.
The machine-readable status is available at /openapi-status.json. See the REST API reference or ChatGPT integration guide for verified connection and authentication facts.