/api/*
Live production routes used across the platform and public integrations today.
Policy
Versioning Policy
Reyzen currently exposes public data routes under /api/*. The long-term stable
convention targets explicit versioning such as /v1/*. Until then, this changelog is the
authoritative place to monitor interface drift, field additions, and deprecation intent.
/v1/*
Explicit version names are the target once route families are stabilized long-term.
Planned breaking removals should ship with migration notes and advance notice.
Standards
Release Principles
- Field additions may occur without breaking consumers if the response remains backwards compatible.
- Consumers should tolerate
null,N/A, or omitted fields where live upstream data is unavailable. - Cache and freshness behavior can change if required to protect origin stability or correctness.
- UI wording may evolve, but public response field names and semantics should be documented here when they materially change.
Integration Guidance
Build against documented fields, not inferred display labels. Where freshness matters, always inspect timestamp or status fields rather than assuming every response is real-time.
Latest
Latest Release Notes
The current milestone formalized the public documentation surface, standardized core response guidance, and improved route discoverability for builders consuming Reyzen analytics.
Builder-Ready Documentation Expansion
The developer portal expanded into a structured endpoint catalog with request/response guidance, implementation notes, and operational conventions for external teams.
- Published full endpoint catalog at
/docs/with grouped product sections. - Added request examples and response structure guidance for live trade, profile, trader, and share-card APIs.
- Documented reliability conventions including cache control, freshness, rate limiting, and nullability expectations.
- Added builder-facing integration examples for curl, JavaScript, and Python clients.
Rate Limit and Cache Header Standardization
Core routes were brought under a more explicit rate-limit and caching policy so integrators can reason about traffic patterns and refresh behavior more safely.
- Enforced per-IP rate limiting with
X-RateLimit-*response headers. - Applied route-specific
Cache-Controlpolicies for live, funding, and ticker paths. - Documented retry guidance for
429responses and freshness-sensitive consumers.
Wallet Share Route Stability Improvements
Share-card generation behavior and route conventions were normalized for more stable social-card automation and external preview generation.
- Standardized share-card response behavior on
/api/share-card. - Normalized wallet-specific share URL patterns such as
/share/wallet/{address}. - Improved metadata consistency for preview cards used on X/Twitter and other Open Graph surfaces.
Archive
Release Archive Notes
This changelog is still young. Additional dated entries should be appended here as production-facing contracts evolve. Keep major route changes, field-level contract shifts, and builder-impacting fixes in this page even if the UI itself changes elsewhere.
| Change Type | Should Be Logged Here | Builder Impact |
|---|---|---|
| New endpoint | Yes | Discovery and adoption path for new integrations |
| Field added | Yes if meaningful | Consumer parsing, feature expansion, optional UI support |
| Cache policy changed | Yes | Polling cadence and freshness assumptions may need adjustment |
| Pure visual redesign | No unless API contract changed | Usually none for external consumers |
| Planned deprecation | Always | Migration planning and rollout coordination |
No changelog sections match this search.