Onboarding checklist
The steps to go live with SignalWise.
Agree on the scope
With your account manager, choose:
- Plan: Standard (alerts), Advanced (alerts + reasoning) or Personalized (alerts per user).
- Universe: the asset classes, markets or exact list of assets you want covered.
- Alert types: all 13, or only some of them. See Alert types.
- Languages: the languages of your users. See Languages.
- Delivery method: Kafka, a cloud connector, REST API or widgets. See Integration options.
- A technical contact on your side.
Receive your credentials
Bridgewise sends your credentials through a secure, one-time link:
- Kafka: bootstrap server, API key and secret, Schema Registry URL and credentials, and your topic name(s). Access is read-only.
- REST API and widgets: an application client ID and secret.
- Personalized plan: your
tenantId.
Share your instruments (optional)
If you want to use your own instrument IDs, send us a mapping file. See Instrument identifiers.
Connect and test on staging
Start on the staging environment: rest.stage-bridgewise.com for the API, and topics prefixed with stage- on Kafka. A separate test topic can be created for you.
Personalized plan: send your users' holdings
Publish your users' portfolios or watchlists to the input topic every day, or whenever they change. See Personalization.
Go live
Switch to production credentials and topics, and start notifying your users.
Need historical data?
Historical alerts and reasoning can be delivered on request, as a JSON Lines file over SFTP. Useful for back-testing or to fill your feed on day one. Ask your account manager.