Developer Overview

Pariflow developer documentation is for partners and approved integrations that need market data or platform access.

API access is not documented here as an open self-serve surface. Access can require approval, credential issuance, usage limits, and additional controls depending on the integration.

Access model

API access may be restricted by use case, account status, rate limit, jurisdiction, and compliance review. Do not assume every product feature is available through public API.

Approved integrations should use the smallest permission scope needed for the product experience. Read-only market data, user-authorized account data, and trading permissions should be treated as separate access levels.

Integration areas

Area	Description
Market data	Read market metadata, price snapshots, order book context, and activity where available.
User data	Access account-specific data only through authenticated user flows or approved credentials.
Trading	Programmatic trading, where available, is subject to additional controls and explicit permission.
Webhooks	Event-driven integrations may be available for settlement, account, or operational workflows.

Safe public example

Use environment variables or a managed secret store. Do not hard-code credentials in client-side code, public repositories, support tickets, screenshots, or documentation.


PARIFLOW_API_KEY=your_key_here
PARIFLOW_ENV=production

The example above is a safe sample value. It is not a real credential.

Reliability expectations

Integrations should handle:

Rate limits.
Stale or delayed market data.
Closed or suspended markets.
Partial or unavailable liquidity.
Temporary market data interruptions.
Backward-compatible schema additions.

State-aware integrations

Before using a price or submitting any trade-related request, integrations should confirm: