openapi: 3.0.1 info: title: Quix Cloud HTTP APIs Definitions Event Data API description: 'OpenAPI 3.0 description of the HTTP (REST) surfaces of Quix Cloud: the Streaming Writer API for publishing time-series parameter data, events, and definitions into Quix topics, and the account-wide Portal API for managing workspaces, topics, and deployments. The Streaming Reader API is delivered exclusively over a Microsoft SignalR hub (WebSockets / Long Polling) and is therefore modeled separately in the companion AsyncAPI document at asyncapi/quix-asyncapi.yml, not here. All endpoints authenticate with a Quix Personal Access Token (PAT) supplied as an `Authorization: Bearer ` header. The Streaming Writer API base host is environment-specific (`writer-{environmentId}.cloud.quix.io`); the Portal API is account-wide (`portal-api.platform.quix.io`). Endpoint paths are documented by Quix; per-environment Swagger/OpenAPI references are available from the Quix portal under Settings > APIs and tokens.' termsOfService: https://quix.io/terms/ contact: name: Quix Support url: https://quix.io/contact/ license: name: API documentation - Quix Terms url: https://quix.io/terms/ version: '1.0' servers: - url: https://writer-{environmentId}.cloud.quix.io description: Streaming Writer API. Environment-specific host; `{environmentId}` is the URL-friendly combination of organization, project, and environment names (e.g. `myorg-myproject-production`). variables: environmentId: default: myorg-myproject-production description: Quix environment (workspace) identifier. - url: https://portal-api.platform.quix.io description: Portal API. Account-wide management host. The subdomain segment may differ per Quix deployment; copy the exact Portal API base from the Quix portal (Settings > APIs and tokens). tags: - name: Event Data description: Publish discrete events into a stream (Streaming Writer API). paths: /topics/{topicName}/streams/{streamId}/events/data: post: operationId: sendEventData tags: - Event Data summary: Send event data description: Publishes one or more discrete events to a stream. Each event carries a nanosecond `timestamp`, an `id`, an optional `value`, and optional `tags`. servers: - url: https://writer-{environmentId}.cloud.quix.io variables: environmentId: default: myorg-myproject-production parameters: - $ref: '#/components/parameters/TopicName' - $ref: '#/components/parameters/StreamId' requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/EventDataRequest' responses: '200': description: Events accepted. '401': $ref: '#/components/responses/Unauthorized' security: - bearerAuth: [] components: responses: Unauthorized: description: Authentication failed - the bearer token is missing, malformed, or expired. content: application/json: schema: $ref: '#/components/schemas/Error' parameters: TopicName: name: topicName in: path required: true description: The name of the topic the stream belongs to. schema: type: string StreamId: name: streamId in: path required: true description: The unique identifier of the stream. Publishing to an id that does not exist creates the stream implicitly. schema: type: string schemas: Error: type: object properties: status: type: integer title: type: string detail: type: string EventDataRequest: type: array description: An array of discrete events to publish. items: type: object required: - id - timestamp properties: id: type: string description: The event definition id. timestamp: type: integer format: int64 description: Nanosecond epoch timestamp of the event. value: type: string description: Optional event payload value. tags: type: object additionalProperties: type: string description: Optional tags for the event. securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: PAT description: 'Quix Personal Access Token (PAT) presented as `Authorization: Bearer `. Generate from the Quix portal under your profile > Personal Access Tokens, or Settings > APIs and tokens.'