Marketly Assistant by Binomo — API integration & OpenFinance services

Deliverables checklist

• OpenAPI 3.1 specification for every endpoint we expose.
• Protocol analysis report covering the auth handshake, token lifecycle, and WebSocket frames observed.
• Runnable Python and Node.js source for login, candle pull, and trade-history pull.
• Postman collection plus pytest / vitest suites against a sandbox.
• Compliance notes: data minimization, retention, KYC pass-through, and IFC-aligned dispute handling.

Engagement models

• Source code delivery from $300 — you receive the runnable API source and docs; you pay after delivery and acceptance.
• Pay-per-call hosted endpoints — call our managed Marketly / Binomo gateway and pay only per request; no upfront fee, ideal for usage-based teams.
• Custom retainer — protocol drift monitoring, schema regression tests, and on-call patches when the upstream app updates.

1. Trade-history reconciliation for affiliates

An IB or affiliate network needs nightly trade tickets across thousands of referred users. We expose /v1/marketly/trade-history with cursor pagination, signed by a per-affiliate token. The job lands deltas into BigQuery, where the affiliate calculates payout splits — replacing weekly CSV exports with a reliable, idempotent pull.

2. OHLC export for back-testing

A quant team wants 90 days of 1-minute candles for the top 30 instruments. We map asset symbols, normalise UTC timestamps, and serve a streaming response so they can backfill without rate-limit retries. This mirrors the get_candles(asset, start, end) shape already familiar from community Python clients.

3. KYC-aware account binding

A neo-broker partner wants to embed Marketly Assistant accounts inside its own app. We wrap the email / Google / Facebook login behind /v1/marketly/login, validate the 2FA challenge, and return a scoped session — the partner stores only an opaque handle, not raw credentials. KYC tier is exposed as a claim so downstream features unlock cleanly.

4. Demo-account telemetry for training providers

A trading-school operator runs cohorts on the no-registration demo mode. We push per-cohort win-rate, drawdown, and lesson-completion events into their LMS so instructors can grade students on real chart behaviour rather than quiz scores — turning the in-app demo into measurable curriculum output.

5. Compliance audit trail for IFC disputes

If a client must file with the International Financial Commission, the audit pack needs every order, payout, and authentication event. Our /v1/marketly/audit endpoint returns a Merkle-anchored event log so the operator can hand a regulator a tamper-evident timeline rather than a raw database dump.

1) Account login + 2FA

POST /v1/marketly/login
Content-Type: application/json

{
  "email": "trader@example.com",
  "password": "<hashed>",
  "totp": "123456",
  "device_id": "ios-9c8f"
}

200 OK
{
  "session_id": "sess_01HX...",
  "access_token": "eyJhbGciOi...",
  "refresh_token": "rt_01HX...",
  "kyc_tier": "verified",
  "expires_in": 3600
}

2) Pull OHLC candles

GET /v1/marketly/candles
  ?asset=EURUSD
  &timeframe=1m
  &from=2026-04-01T00:00:00Z
  &to=2026-04-02T00:00:00Z
Authorization: Bearer <ACCESS_TOKEN>

200 OK
{
  "asset": "EURUSD",
  "timeframe": "1m",
  "candles": [
    {"t":"2026-04-01T00:00:00Z","o":1.0832,"h":1.0834,"l":1.0830,"c":1.0833,"v":215},
    {"t":"2026-04-01T00:01:00Z","o":1.0833,"h":1.0836,"l":1.0832,"c":1.0835,"v":188}
  ],
  "next_cursor": "c_01HX..."
}

3) Trade-event webhook

POST https://your-app.example.com/hooks/marketly
X-Marketly-Signature: sha256=ab12...

{
  "event": "trade.closed",
  "occurred_at": "2026-05-02T08:14:11Z",
  "trade": {
    "id": "trd_01HX...",
    "asset": "BTCUSD",
    "direction": "call",
    "stake": 25.00,
    "payout": 47.50,
    "status": "won",
    "opened_at": "2026-05-02T08:13:11Z",
    "closed_at": "2026-05-02T08:14:11Z"
  },
  "account": {"id":"acc_01HX...","mode":"real","kyc_tier":"verified"}
}

Compliance & privacy

Marketly Assistant is operated on the Binomo platform by Dolphin Corp LLC, registered in Saint Vincent and the Grenadines. The platform is a Category A member of the International Financial Commission, which provides a dispute framework with compensation up to €20,000 per claim. We design every integration to respect that envelope: written client authorization, KYC pass-through, AML logging, and data-minimisation at the edge. Where users are based in the EU we additionally honour GDPR rights (access, rectification, erasure) through a documented data-subject-request endpoint.

What we will not do

• Bypass platform rate limits, anti-abuse controls, or device attestation.
• Persist raw user passwords or 2FA seeds anywhere in our infrastructure.
• Operate in jurisdictions where the underlying broker is restricted (e.g. US, UK, EU regulated retail) without your written legal sign-off.
• Mix real-money and demo data streams without explicit channel separation.

About OpenFinance Lab

We are an independent studio focused on mobile-app protocol analysis and OpenData / OpenFinance / OpenBanking integrations. Our engineers come from FX brokers, payment gateways, and reverse-engineering teams, and have shipped production APIs against trading apps, retail wallets, and bank super-apps in IN, ID, BR, TR, ZA, and MENA. We act under client authorization and ship runnable code, not slide decks.

• Trading and binary-option platforms (login, candles, trade history, payouts).
• Open Banking style account aggregation and statement export.
• Custom Python / Node.js / Go SDKs with regression tests and protocol drift alerts.
• Two engagement models: source-code delivery from $300, or pay-per-call hosted endpoints.

Contact

To request a quote or scope a Marketly Assistant by Binomo integration, send us your target endpoints (login / candles / trade history / webhook) and any sandbox credentials.

Contact page

Engagement workflow

1. Scope confirmation: which endpoints (login, candles, trade history, webhook) and which markets.
2. Protocol analysis on a sandbox account (2–5 business days).
3. API build, normalisation layer, and internal validation (3–8 business days).
4. Docs, OpenAPI spec, Postman collection and test cases (1–2 business days).
5. Acceptance, then either source-code handover or activation of the hosted gateway.

FAQ

What do you need from us to start a Marketly Assistant by Binomo integration?

How long does delivery take for a Binomo-style trading app integration?

How do you handle compliance for a non-EU regulated trading app?