Import an OpenAPI spec as a draft
Imports a new OpenAPI 3 spec into a version. The result is always a draft: nothing changes in the help center until you publish it. Auto-publish never applies here.
Body
Send exactly one of:
url: an https URL of the raw JSON or YAML file. Featurebase fetches it once (the version keeps its source; use the dashboard to set a URL that is checked every 6 hours).content: the JSON or YAML text. Up to 50 MB; for a big fileurlis easier.
Swagger 2.0 is rejected: convert it to OpenAPI 3 first. The same limits as the dashboard apply (50 MB, 1,000 tags, 5,000 endpoints).
Result
202 with a syncId. The spec is processed in the background: poll GET /v2/help_center/api_specs/{specId}/syncs/{syncId} until the status is draft, noop or failed, then read the draft (GET …/draft) and publish it.
Send an Idempotency-Key header to make retries safe (24 hours).
Limits
60 imports and syncs per hour per version, 120 per hour per API key. Every call is in the audit log.
Body
The OpenAPI 3 document as JSON or YAML text. Up to 50 MB; a big file is easier to import with url or the sync endpoint.
1openapi: 3.1.0
info:
title: Acme API
version: 1.0.0
paths: {}
Response
Success
help_center_api_spec_synchelp_center_api_spec_sync