Introduction
How to access SignalWise data, and how to authenticate.
Introduction
SignalWise data is available in two ways:
- Kafka topics: alerts are pushed to you in near real time. See Alert message, Personalized alert message and Portfolio positions.
- REST API: you pull alerts on demand. JSON over HTTPS. See Alerts.
Every alert has the same building blocks: event metadata, text per language, price evidence, asset details and, if your plan includes it, reasoning.
The interactive REST reference is available at rest.bridgewise.com/docs.
BASE URLS
# Production
https://rest.bridgewise.com
# Staging
https://rest.stage-bridgewise.comAuthentication
The REST API and the widgets use a Bearer token.
- Get your application client ID and secret from Bridgewise.
- Exchange them for a token on
POST /users/authenticate. - Send the token in the
Authorizationheader of each request, or asaccessTokenin widget URLs.
POST/users/authenticate
Parameters
application_client_idstringRequiredYour application client ID.
secretstringRequiredYour application secret.
Tokens last 24 hours
Request a token at most once every 24 hours and store it on your backend. Repeated requests are rejected. Never call this endpoint from a browser or a mobile app.
POST /users/authenticate
curl -X POST https://rest.bridgewise.com/users/authenticate \
-H "Content-Type: application/json" \
-d '{
"application_client_id": "<client-id>",
"secret": "<secret>"
}'AUTHENTICATED REQUEST
curl https://rest.bridgewise.com/alerts \
-H "Authorization: Bearer <token>"Scopes
Each token only gives access to the products in your plan.
SignalWise scopes
SignalWise – alertsscopeLatest alerts. Also enables the Market Signals widget.
SignalWise – alerts reasonsscopeLatest alerts with reasons. Also enables the Latest Market Events widget.
KAFKA ACCESS
# Kafka uses separate, read-only credentials
security.protocol=SASL_SSL
sasl.mechanisms=PLAIN
sasl.username=<api-key>
sasl.password=<api-secret>