Quanor developer documentation

Quanor's analyses of listed companies' announcements, the feed they make and company data, for your systems: read them over a REST API, have every change sent live over a WebSocket, or have it pushed to a server of yours as signed webhooks.

Addresses

Version 1. Every path of the REST API begins /v1; what changes within version 1, and how a change is announced, is in the changelog.

Authentication

Send your API key as Authorization: Bearer <key> on every call and on the feed stream's upgrade, from a server: a key is a secret, and a browser cannot send that header on a WebSocket. Quanor issues API keys to its customers, each with the access its agreement includes — the companies, how far back, and whether it may stream, receive webhooks or read each kind of detail. A call a key may not make is answered 401 or 403, in the API's one error shape.

Quickstart

A first call: find a company.

curl "https://api.quanor.com/v1/companies?q=volvo" \
  -H "Authorization: Bearer $QUANOR_API_KEY"

The feed: its newest items, as your key is shown them.

curl "https://api.quanor.com/v1/feed?limit=5" \
  -H "Authorization: Bearer $QUANOR_API_KEY"

Live: open wss://api.quanor.com/v1/stream/feed with the same header, then send:

{"type": "subscribe", "v": 1, "since": null, "lang": "en", "selections": {"feed": {}}}

The stream answers ready and then sends each change as it happens. The feed stream's reference says how to start from a page of the feed, resume after a reconnect and keep a correct copy; it ships a tested reference client.

Webhooks: create an endpoint, and Quanor sends it signed messages as the feed changes.

curl https://api.quanor.com/v1/webhook-endpoints \
  -H "Authorization: Bearer $QUANOR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://hooks.example.com/quanor", "event_types": ["announcement.*"]}'

The webhooks guide says how to verify, respond and apply.

References