openapi: 3.0.1 info: title: Symphony Agent Add Subscribers API description: 'This document refers to Symphony API calls to send and receive messages and content. They need the on-premise Agent installed to perform decryption/encryption of content. - sessionToken and keyManagerToken can be obtained by calling the authenticationAPI on the symphony back end and the key manager respectively. Refer to the methods described in authenticatorAPI.yaml. - Actions are defined to be atomic, ie will succeed in their entirety or fail and have changed nothing. - If it returns a 40X status then it will have sent no message to any stream even if a request to some subset of the requested streams would have succeeded. - If this contract cannot be met for any reason then this is an error and the response code will be 50X. - MessageML is a markup language for messages. See reference here: https://rest-api.symphony.com/docs/messagemlv2 - **Real Time Events**: The following events are returned when reading from a real time messages and events stream ("datafeed"). These events will be returned for datafeeds created with the v5 endpoints. To know more about the endpoints, refer to Create Messages/Events Stream and Read Messages/Events Stream. Unless otherwise specified, all events were added in 1.46. ' version: 22.9.1 servers: - url: / tags: - name: Subscribers paths: /v1/signals/{id}/subscribers: get: tags: - Subscribers summary: Get the Subscribers of a Signal parameters: - name: sessionToken in: header description: Session authentication token. required: true schema: type: string - name: keyManagerToken in: header description: Key Manager authentication token. schema: type: string - name: id in: path description: The id of the signal. required: true schema: type: string - name: skip in: query description: No. of results to skip. schema: type: integer default: 0 - name: limit in: query description: Max No. of subscribers to return. If no value is provided, 100 is the default. schema: type: integer default: 100 responses: '200': description: Signal Subscribers. content: application/json: schema: $ref: '#/components/schemas/ChannelSubscriberResponse' '400': description: Client error, see response body for further details. content: application/json: schema: $ref: '#/components/schemas/V2Error' '401': description: 'Unauthorized: Session tokens invalid.' content: application/json: schema: $ref: '#/components/schemas/V2Error' '403': description: 'Forbidden: Caller lacks necessary entitlement.' content: application/json: schema: $ref: '#/components/schemas/V2Error' '500': description: Server error, see response body for further details. content: application/json: schema: $ref: '#/components/schemas/V2Error' components: schemas: V2Error: required: - code - message type: object properties: code: type: integer format: int32 message: type: string details: type: object ChannelSubscriber: type: object properties: subscriptionId: type: string pushed: type: boolean description: True if the subscriber is allowed to unsubscribe default: false owner: type: boolean description: True if the subscriber is the creator default: false subscriberName: type: string description: User display name userId: type: integer description: The user ID of the subscriber format: int64 timestamp: type: integer description: Timestamp when the signal was subscribed, in milliseconds since Jan 1 1970 format: int64 ChannelSubscriberResponse: type: object properties: offset: type: integer description: The number of subscribers skipped format: int64 hasMore: type: boolean description: True if there are more subscribers total: type: integer description: The total number of subscribers data: type: array items: $ref: '#/components/schemas/ChannelSubscriber'