Ordellum AnalyticsLaunching
Integrations
Connect Analytics to your stack through APIs, real-time streams, webhooks and client libraries.
- REST
- Request-and-response access to projects, analytics, compliance and identity resources.
- GraphQL
- Flexible queries with depth and cost limits that protect the service.
- WebSocket
- Live channels for critical alerts, high-risk events, dApp metrics and transactions.
- Webhooks
- Signed notifications pushed to your systems when something important happens.
Capabilities available through the API
- Projects
- Examples: Register a dApp, upload its contract interfaces and request verification
- Analytics
- Examples: Metrics, cohorts, segments, retention, events, tokenomics and custom queries
- Compliance
- Examples: Screen addresses, manage alerts, review and export suspicious-activity reports, check sanctions
- Identity
- Examples: Start verification, read credentials, verify presentations and check verification levels
- Alerts
- Critical and high-priority alerts, risk-threshold crossings and sanctions matches.
- Reports
- A new suspicious-activity report draft is created.
- Analytics
- Metric anomalies and significant TVL changes.
- Identity
- A verification is completed.
- Operations
- Pipeline errors and status changes.
Client libraries and their release track
Language: TypeScript
- Distribution
- npm
- Track
- Stable
Language: Python
- Distribution
- PyPI
- Track
- Stable
Language: Go
- Distribution
- Go modules
- Track
- Stable
Language: Rust
- Distribution
- crates.io
- Track
- Beta
Language: Java / Kotlin
- Distribution
- Maven
- Track
- Beta
Libraries handle authentication, retries with back-off, rate-limit awareness, pagination, WebSocket reconnection and webhook signature checks. Availability is confirmed at public launch.
- Tenant isolation
- Every request is checked against the tenant and object it belongs to.
- Field-level authorisation
- Users only see the fields they are allowed to see.
- Idempotency
- Every change carries an idempotency key, so retries never apply twice.
- Strict schemas
- Unknown fields are rejected rather than ignored.
- Rate limits
- Limits protect capacity and are never a separate revenue line.
Active
Fully supported
New features and fixes, with no end date.
12 months
Maintenance
Security fixes only.
6 months
Deprecated
Still available, with notice to migrate.
End
Retired
The version is switched off.
Adding a field, an optional parameter or a new endpoint is backwards compatible. Removing a field, changing a type or adding a required parameter only happens in a new version.