{"type":"model","meta":{"id":"/apps/pubhub/media/cisco-spaces-firehose-api/06dca1c4f6ca5c552beba6e1f568d97c5e54ed10/b48399e9-814a-37ff-bbd3-3e1ec68cb853","info":{"title":"Cisco Spaces Firehose Streaming API","version":"2.0.0","description":"Streaming endpoint for the Cisco Spaces Firehose. The HTTP pull channel returns a long-lived response whose body is **newline-delimited JSON (NDJSON)**: one `EventRecord` per line, separated by `\\n`. The connection remains open and events are pushed continuously.\n\nFor the WebSocket and gRPC streaming surfaces, see the companion documentation pages:\n- [WebSocket Streaming](https://developer.cisco.com/docs/cisco-spaces-firehose/websocket-streaming/)\n- gRPC: [spaces_firehose_spec_v2.0.proto](https://pubhub.devnetcloud.com/media/cisco-spaces-firehose-api/docs/v2/spaces_firehose_spec_v2.0.proto) and [gRPC Streaming](https://developer.cisco.com/docs/cisco-spaces-firehose/grpc-streaming/)\n\nThe canonical schema for `EventRecord` and every event payload is defined in the Protocol Buffer file `spaces_firehose_spec_v2.0.proto`. JSON field names on the wire are the **camelCase** equivalent of the proto `snake_case` names (e.g., `record_uid` → `recordUid`)."},"security":[{"ApiKeyAuth":[]}],"tags":[{"name":"Streaming","description":"Long-lived streaming endpoints that push EventRecord objects to subscribed clients."}],"openapi":"3.1.0","servers":[{"url":"https://partners.ciscospaces.io","description":"US region"},{"url":"https://partners.ciscospaces.eu","description":"EU region"},{"url":"https://partners.ciscospaces.sg","description":"Singapore region"}],"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"header","name":"X-API-KEY","description":"Activation-specific API key. Issued from the Cisco Spaces Partner Dashboard."}}},"spec":{"properties":{"name":{"type":"string"},"values":{"items":{"type":"string"},"type":"array"}},"additionalProperties":true,"type":"object","title":"Attribute","$$ref":"#/components/schemas/Attribute"}}