How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Symphony Signals API

The Signals API from Symphony — 8 operation(s) for signals.

Symphony Signals API is one of 20 APIs that Symphony publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Signals. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 8 operations across 8 paths, and defines 9 schemas. It is described by OpenAPI 3.2.0, at version 22.9.1.

Requests are made against a single base URL, /.

8 operations 8 paths 9 schemas 3 GET5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
22.9.1
Base URL
https://acme.symphony.com
Resource Areas
1

Paths & Operations 8

Across 8 paths, the API surfaces 8 operations — 3 GET, 5 POST. Each is listed below with its method, path, parameters, and response codes.

Signals 8
GET
/v1/signals/list
Symphony List signals for the requesting user. This includes signals that the user has created and public signals to which they subscribed.
4 params → 200400401403500
GET
/v1/signals/{id}/get
Symphony Get Details of the Requested Signal
3 params → 200400401403500
POST
/v1/signals/create
Symphony Create a Signal
2 params body → 200400401403451500
POST
/v1/signals/{id}/update
Symphony Update a Signal
3 params body → 200400401403451500
POST
/v1/signals/{id}/delete
Symphony Delete a Signal
3 params → 200400401403500
POST
/v1/signals/{id}/subscribe
Symphony Subscribe to a Signal
4 params body → 200400401403500
POST
/v1/signals/{id}/unsubscribe
Symphony Unsubscribe to a Signal
3 params body → 200400401403500
GET
/v1/signals/{id}/subscribers
Symphony Get the Subscribers of a Signal
5 params → 200400401403500

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are ChannelSubscriber (6 properties), BaseSignal (4 properties), ChannelSubscriberResponse (4 properties), ChannelSubscriptionResponse (4 properties). Each schema is shown below with its type and property counts.

V2Error
object
3 properties 2 required
SignalList
array
Signal
ChannelSubscriptionError
object
3 properties
SuccessResponse
object
2 properties
ChannelSubscriber
object
6 properties
ChannelSubscriptionResponse
object
4 properties
ChannelSubscriberResponse
object
4 properties
BaseSignal
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

symphony-signals-api-openapi.yml Raw ↑

Other APIs Symphony publishes across the network.

Symphony All API
Symphony App API
Symphony Audittrail API
Symphony Authenticate API
Symphony Channelco API
Symphony Datafeeds API
Symphony Dlp API
Symphony Events API
Symphony Groups API
Symphony Health API
Symphony Idm API
Symphony Info API
Where this information came from

This is an independent, third-party profile of Symphony Signals API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.