Skip to content
Partner API Docs

Market-data redistribution rights

Govern display, derived use, storage, attribution, entitlements, audits, vendors, and exchange-specific restrictions for delayed market data.

Technical access does not equal redistribution permission. Before exposing an exchange's data to end users, confirm that the upstream licence permits the intended audience, device, geography, latency, storage, and commercial use.

Classify the use before launch

UseTypical classificationRequired decision
Price shown to one authenticated investorDisplayIs end-user display permitted and attributable?
Public website, widget, or social postPublic redistributionIs a public-display licence required?
Download, API, spreadsheet, or bulk exportNon-display / redistributionUsually requires explicit rights
Portfolio valuation or P&LDerived internal useDefine whether values can be stored or exposed
Index, signal, model, or AI trainingDerived/computational useSeparate permission may apply
Data shared with affiliates or vendorsThird-party useSub-licence, processor, or vendor approval

No implied exchange licence

MyStocks API credentials do not grant a direct exchange licence or permission to resell a feed. Your executed data schedule controls. Where it conflicts with a general guide, the executed schedule wins.

Entitlement record

Maintain a machine-readable register for every market:

FieldExample
Exchange / datasetNSE delayed top-of-book
Audienceauthenticated retail customers
GeographyKenya and approved diaspora markets
Usein-app display and portfolio valuation
Delayapproximately 15 minutes
Attributionrequired text and logo treatment
Storagequote cache TTL and historical retention
Exportdisabled unless separately approved
Effective / renewal datecontract-controlled
Evidence ownerdata licensing lead

Gate the product by this register. A commercial team should not be able to turn on a new public widget, country, or download feature without a recorded rights decision.

Display standard

  • Show the exchange, instrument currency, and market status.
  • Present asOf, ageSeconds, stale, and delayMode where relevant to the decision.
  • Use “delayed” rather than “live” or “real time” for price endpoints.
  • Apply required MyStocks and exchange attribution without obscuring it.
  • Stop or degrade display when entitlement expires, data becomes stale, or the provider withdraws rights.
  • Keep state-change webhooks/SSE distinct from price streaming; event delivery is not a tick feed.

Storage and downstream controls

  1. Limit cache and historical retention to the executed licence.
  2. Prevent bulk extraction with authentication, rate limits, export limits, and anomaly detection.
  3. Flow restrictions to analytics, observability, support tools, subprocessors, and backups.
  4. Maintain lineage from provider and exchange through transformed fields to customer display.
  5. Delete or quarantine data when rights end, subject to lawful record-retention requirements.
  6. Preserve usage logs needed for exchange/vendor audits without collecting unnecessary personal data.

Change workflow

Product request
market · audience · use
Rights review
contract + exchange policy
Technical controls
entitlement · cache · attribution
Approval
legal + data owner
Monitor
usage + expiry + audit

Production evidence

  • Executed market-data schedule and exchange/provider rights matrix.
  • Screenshots or design evidence showing delay and attribution treatment.
  • Cache, export, download, and API-access controls.
  • Vendor/subprocessor list and contractual flow-downs.
  • Usage reporting, audit response, expiry, and takedown procedure.

See Data licensing and Market-data quotes for the current API behaviour.

Was this page useful?

Your signal helps us tighten partner onboarding docs.

Last updated on

On this page