> ## Documentation Index > Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt > Use this file to discover all available pages before exploring further. # Upload an OpenAPI Spec Version > Use this endpoint to publish a global OpenAPI 3.x specification version for a native service. Every tenant resolves against the published versions. Versions are immutable: uploading a version that already exists returns 409. Send the specification as multipart/form-data; the file must not exceed 8 MiB. The caller needs the create permission on the catalog resource. ## OpenAPI ````yaml en/openapi/v3-current/flowker.yaml post /v1/catalog/openapi-specs/{service}/{version} openapi: 3.1.0 info: description: >- Complete API reference for Flowker workflow orchestration services including catalog management, workflow definitions, executor configurations, provider configurations, and workflow executions. title: Flowker API version: 1.2.0 servers: - url: https://flowker.sandbox.lerian.net security: - BearerAuth: [] tags: - name: Catalog API description: >- Browse built-in providers, executors, and triggers available in the Flowker catalog. - name: Workflows API description: >- Create, update, activate, deactivate, clone, and delete workflow definitions. - name: Executions API description: Start workflow executions and track their status and results. - name: Executor Configurations API description: >- List, inspect, update, and delete the executor configuration records a deployment holds. - name: Provider Configurations API description: >- Create, update, enable, and disable the provider configurations that workflow nodes call through. - name: Dashboard API description: >- Retrieve aggregated summaries of workflows and executions for operational dashboards. - name: Webhooks API description: >- Receive webhook callbacks from external systems to trigger workflow executions. - name: Schedule API description: >- Inspect a workflow's upcoming, skipped, and parked scheduled occurrences, and run or discard the parked ones. - name: Schema Registry API description: >- Publish global OpenAPI specification versions for native services and pin the version each tenant resolves against. - name: OpenAPI Schemas API description: >- Upload, inspect, and delete the tenant's external OpenAPI schemas, and derive the contract of a single operation. - name: XSD Schemas API description: >- Upload, inspect, and delete the tenant's XSD schemas used to validate XML webhook payloads. paths: /v1/catalog/openapi-specs/{service}/{version}: post: tags: - Schema Registry API summary: Upload an OpenAPI Spec Version description: >- Use this endpoint to publish a global OpenAPI 3.x specification version for a native service. Every tenant resolves against the published versions. Versions are immutable: uploading a version that already exists returns 409. Send the specification as multipart/form-data; the file must not exceed 8 MiB. The caller needs the create permission on the catalog resource. operationId: uploadOpenAPISpec parameters: - description: >- Service identifier (the provider id / global spec key segment, e.g. ledger). in: path name: service required: true schema: description: >- Service identifier (the provider id / global spec key segment, e.g. ledger). type: string example: ledger - description: Spec version (immutable, e.g. v1.0.0). in: path name: version required: true schema: description: Spec version (immutable, e.g. v1.0.0). type: string example: v1.0.0 requestBody: content: multipart/form-data: encoding: file: contentType: application/octet-stream schema: properties: file: contentEncoding: binary contentMediaType: application/octet-stream description: OpenAPI 3.x spec file (JSON). format: binary type: string required: - file type: object responses: '201': description: >- Indicates that the resource was successfully created and the operation was completed as expected. '400': content: application/problem+json: schema: $ref: '#/components/schemas/ErrorResponse' description: >- Indicates that the request was malformed or contained invalid parameters. '409': content: application/problem+json: schema: $ref: '#/components/schemas/ErrorResponse' description: >- Indicates that the request could not be completed due to a conflict with the current state of the resource. '413': content: application/problem+json: schema: $ref: '#/components/schemas/ErrorResponse' description: Indicates that the request payload exceeds the maximum allowed size. '422': content: application/problem+json: schema: $ref: '#/components/schemas/ErrorResponse' description: >- Indicates that the request was well-formed but contains semantic errors that prevent processing. '500': content: application/problem+json: schema: $ref: '#/components/schemas/ErrorResponse' description: >- Indicates an unexpected internal error. If this persists, please contact support. '503': content: application/problem+json: schema: $ref: '#/components/schemas/ErrorResponse' description: >- Indicates that the service is temporarily unable to handle the request. components: schemas: ErrorResponse: properties: code: description: Stable, machine-readable Flowker error code. example: FLK-0001 type: string detail: description: >- Human-readable explanation of this occurrence. Responses with a status of 500 or above carry a fixed generic message. example: name is a required field type: string errors: description: Per-field entries for a request that failed validation. items: $ref: '#/components/schemas/ErrorDetail' type: array instance: description: URI reference identifying this specific occurrence. example: /v1/workflows format: uri type: string status: description: HTTP status code. example: 400 type: integer title: description: >- Standard HTTP reason phrase for the status. It does not change per error code. example: Bad Request type: string type: description: >- URI reference identifying the error. Always the error catalog base followed by the code. example: https://errors.lerian.studio/v1/FLK-0001 format: uri type: string type: object ErrorDetail: properties: location: description: Where the problem is, such as body.nodes or path.id. example: body.nodes type: string message: description: Description of the field-level problem. example: expected array length >= 1 type: string value: description: The value that caused the error, when it is safe to echo. type: object securitySchemes: BearerAuth: type: http scheme: bearer bearerFormat: JWT description: >- JWT bearer token issued by the identity provider. Send it in the Authorization header as `Bearer `. ````