Solusfinance Fantasy Trading API integration & OpenData services

Account & session module

Mirrors the in-app login flow. Supports email/social sign-in, KYC tier read, device-binding tokens, and session refresh. Pairs with consent records so every downstream call can be audited.

Concrete use: single sign-on bridge between Solus and your customer portal so users see their tournament entries inside your dashboard.

Contest & tournament module

List active and upcoming tournaments with entry fee, prize pool, asset universe (BTC, ETH, EUR/USD, NASDAQ100, etc.), and rule-set. Submit entries, fetch confirmations, and stream live state changes via webhook.

Concrete use: a community manager dashboard showing every tournament a creator's audience is currently entered in, with auto-pinned rankings.

Leaderboard & ranking module

Pull global, tournament-scoped, and friend-scoped leaderboards with paging, ranking deltas, and consistency scores. Returns timestamps so historical climbs can be replayed.

Concrete use: publish a weekly "top strategies" digest on a partner's website without scraping the in-app UI.

Prediction history module

Per-user list of UP/DOWN calls — asset, direction, stake, expiry, outcome, AI suggestion (if used). Exportable as JSON/CSV; supports incremental sync with cursor pagination.

Concrete use: performance attribution across asset classes, e.g. "this user beats the market on BTC but underperforms on FX".

Wallet, staking & reward module

Reads SOLUS token balance, staked amount, 12% APY accrued, blue-chip airdrop receipts, and contest credit balance. Flags transactions with type, source tournament, and chain reference where applicable.

Concrete use: tax-year ledger generation for users in jurisdictions that treat tokens as taxable income.

Referral & creator payouts module

Surfaces the referral graph (inviter → invitee) with bonus amounts, the 20% referral cut, and creator-tournament fee splits. Supports CSV exports for finance and KYC review.

Concrete use: influencer revenue dashboard showing earnings per tournament and per cohort.

Deliverables checklist

• Protocol & auth flow report (OAuth/token, refresh, device binding).
• OpenAPI / Swagger specification for all endpoints we wrap.
• Runnable source for login, contest, leaderboard, prediction history, wallet, and referral APIs (Python or Node.js).
• Webhook handlers for live tournament state and reward events.
• Automated tests, sample payloads, and Postman collection.
• Compliance brief: KYC tier handling, GDPR retention, MiCA-aligned crypto disclosures.

Technical implementation — login

POST /api/v1/solus/auth/login
Content-Type: application/json

{
  "email": "user@example.com",
  "password": "***",
  "device_id": "ios-9F2A...",
  "consent_scopes": ["contest.read","leaderboard.read","wallet.read"]
}

200 OK
{
  "access_token": "eyJhbGc...",
  "refresh_token": "rft_...",
  "expires_in": 3600,
  "kyc_tier": "tier-2",
  "user_id": "usr_8h2k"
}

Technical implementation — leaderboard

GET /api/v1/solus/leaderboard?
  tournament_id=trn_20251108_btc&
  scope=global&limit=50&cursor=eyJv...
Authorization: Bearer <ACCESS_TOKEN>

200 OK
{
  "tournament_id": "trn_20251108_btc",
  "entries": [
    {"rank":1,"user_id":"usr_a1","return_pct":18.4,"consistency":0.81,"delta":+2},
    {"rank":2,"user_id":"usr_b2","return_pct":15.7,"consistency":0.74,"delta":-1}
  ],
  "next_cursor": "eyJvZmZ..."
}

Technical implementation — wallet & staking

GET /api/v1/solus/wallet/ledger?
  from=2025-01-01&to=2025-12-31&
  types=stake_accrual,airdrop,referral_payout
Authorization: Bearer <ACCESS_TOKEN>

200 OK
{
  "balance_solus": 4218.55,
  "staked_solus": 3000.00,
  "apy_accrued_ytd": 312.41,
  "movements": [
    {"ts":"2025-04-07T10:12:00Z","type":"airdrop","asset":"BTC","amount":0.00041},
    {"ts":"2025-04-08T08:00:00Z","type":"stake_accrual","asset":"SOLUS","amount":1.62},
    {"ts":"2025-04-12T19:55:00Z","type":"referral_payout","asset":"SOLUS","amount":21.00}
  ]
}

// Error envelope used across endpoints
{ "error": { "code":"rate_limited", "retry_after_ms": 1500 } }

Compliance & privacy

Solus operates a token economy and processes both fiat-side flows (entry fees, payouts) and on-chain assets (SOLUS token, blue-chip airdrops). Integrations should align with several frameworks at once:

• GDPR for any user residing in the EU/EEA — explicit consent scopes per data category, right-to-erasure handling, and 30-day data minimisation defaults.
• MiCA (EU's crypto-asset regulation, applicable from 2024) — disclosures for token reward mechanics, staking yield, and any service that touches custody of SOLUS.
• FCA / SEC / SEBI guidance on skill-based contests vs. regulated trading — our integration brief flags which endpoints can be exposed to consumer apps and which require a regulated counterparty.
• KYC tier propagation — only endpoints whose KYC requirement is satisfied are returned to the partner; lower-tier users see scoped subsets.

We work strictly under explicit user authorization or documented public/authorized APIs. Audit logs, consent records, and data-retention policies are part of every delivery.

Data flow / architecture

A typical pipeline:

• Client App (Solus iOS/Android) — user authenticates, enters contests, makes UP/DOWN calls.
• Ingestion / API gateway — our wrapper handles login, scope checks, rate-limit shaping, and request signing.
• Storage layer — Postgres for relational records (entries, leaderboards), object store for raw exports, time-series store for prediction streams.
• Analytics / API output — REST/GraphQL for partners, webhooks for live events, scheduled exports (CSV/Parquet) for finance teams.

The architecture mirrors OpenBanking's three-layer model — Account Information Service, Transaction Information Service, and Consent Service — adapted to a fantasy-trading context.

About our studio

We are an independent technical studio specializing in App interface integration and authorized API integration. Our team has hands-on experience in mobile applications, fintech, crypto wallets, and protocol analysis, and we have shipped integrations against contest platforms, banks, payment rails, and OTT services across multiple regions.

• Experience with fintech, crypto, contest, and prediction-market platforms.
• Deep knowledge of OAuth, mobile token flows, certificate pinning, and webhook delivery.
• Multi-language SDKs (Python, Node.js, Go) with full test harnesses.
• End-to-end pipeline: protocol analysis → API design → implementation → validation → compliance brief.
• Source code delivery from $300 — runnable API source code and full documentation; pay after delivery upon satisfaction.
• Pay-per-call API billing — hosted endpoints, pay only per call, no upfront cost; suited to teams that want usage-based pricing.

Contact

For quotes, sandbox access, or to submit your target app and requirements, open our contact page:

Contact page

We respond within one business day. NDAs available on request.

Engagement workflow

1. Scope confirmation — which Solus features matter (contests, leaderboards, wallet, referrals) and what scopes you need.
2. Protocol analysis & API design (2–5 business days, complexity-dependent).
3. Build, internal validation, and webhook plumbing (3–8 business days).
4. Documentation, sample collection, and test cases (1–2 business days).
5. Typical first delivery: 5–15 business days; third-party approvals or KYC partner sign-off may extend this.

FAQ

What do you need from me?

How long does delivery take?

How do you handle compliance for a token-based app?

Can I extend integration to similar apps later?