Skip to Content
SignalWise

Introduction

How to access SignalWise data, and how to authenticate.

Introduction

SignalWise data is available in two ways:

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.com

Authentication

The REST API and the widgets use a Bearer token.

  1. Get your application client ID and secret from Bridgewise.
  2. Exchange them for a token on POST /users/authenticate.
  3. Send the token in the Authorization header of each request, or as accessToken in widget URLs.
POST/users/authenticate

Parameters

application_client_idstringRequired
Your application client ID.
secretstringRequired
Your 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 – alertsscope
Latest alerts. Also enables the Market Signals widget.
SignalWise – alerts reasonsscope
Latest 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>