Gateways

Import from OpenAPI

If your upstream API has an OpenAPI (Swagger) specification, you can import it to automatically create Gateway endpoints. PayWeave reads the spec, extracts paths and methods, and generates endpoints with a default price you can adjust.

Supported formats

PayWeave accepts OpenAPI 3.0 and 3.1 specifications in JSON or YAML format. Swagger 2.0 specs are automatically converted during import.

How to import

From your Gateway detail page, click Import from OpenAPI. You can provide the spec in two ways:

URL - Paste a link to your spec file (e.g. https://api.example.com/openapi.json). PayWeave fetches and parses it automatically.

File upload - Upload a .json or .yaml file directly from your machine.

What gets imported

For each path and method combination in the spec, PayWeave creates an endpoint:

Plain Text

OpenAPI spec:
  /users:
    get: List users
    post: Create user
  /users/{id}:
    get: Get user by ID

Generated endpoints:
  GET  /users       → $0.001 (default price)
  POST /users       → $0.001 (default price)
  GET  /users/{id}  → $0.001 (default price, wildcard mode)

Paths with parameters like {id} are automatically set to wildcard mode. Static paths default to exact mode.

Adjusting after import

After import, all endpoints appear in the endpoint list with a default price. You can then individually adjust pricing, change path modes, add or remove methods, or delete endpoints you don't want to expose.

Import is additive - it does not remove existing endpoints. You can import multiple specs or re-import after updating your API to add new endpoints without affecting existing ones.

Descriptions and metadata

PayWeave pulls the summary and description fields from each operation in the spec and uses them as the endpoint description. This metadata is displayed in the Bazaar catalog and in 402 responses, helping callers understand what each endpoint does before paying.

Upstream Auth Refunds