Choose a source
Upload JSON, enter a supported definition URL or select a GitHub file.
// OpenAPI Import
Bring a supported OpenAPI or Swagger definition into a shared model for Documentation, API Designer, Request Builder and SDK Generation.
Creates a payment for an existing order.
Import the complete JSON example from the guide. The normalized POST /payments model provides documentation inputs, a Request Builder starting point and schemas for generated integration source. Use an actual API URL when sending requests; example.com is illustrative.
openapi.json -> Preview -> Save API Source
POST /payments
Request: amount (integer), currency (string)
Responses: 201 Created, 422 Unprocessable Content
Continue: Documentation / API Designer / Request Builder / SDK GenerationFollow the practical guideCapabilities
Workflow
Upload JSON, enter a supported definition URL or select a GitHub file.
Review the detected operations and resolve import errors.
Save the source to make the normalized contract available in the workspace.
Browse Documentation, open a request or generate integration source code.
Start from a maintained specification instead of re-entering every operation.
Inspect POST /payments inputs and expected responses before integrating.
Choose manual API creation as a separate starting option when no definition exists and editing is permitted.
Design and refine your API visually, then export its saved definition as a portable OpenAPI JSON specification.
Explore GitHub SynchronizationConnect a repository specification, detect incoming updates and review them alongside local API changes.
Explore API DocumentationTurn OpenAPI 3.x and Swagger 2.0 JSON definitions into structured, searchable reference material for your workspace.
Explore// FAQ
// GET STARTED
Start with an OpenAPI or Swagger JSON definition and keep the workflow together.