Home › Broker Integration Guide

Broker Integration Guide

Updated: June 2026

A technical one-pager for integrating OptionProfit's strategy engine with your trading API. The flow: your client builds a strategy → we hand you a normalized multi-leg order → you place it. You own auth, execution, funds and compliance. Prefer to talk first? See For Brokers.

Architecture

Three layers, one hand-off:

  Client
    |  builds / picks a strategy (embedded widget or our API)
    v
  OptionProfit  -->  normalized multi-leg order (JSON)
                       |  over your transport (REST / WebSocket / MQTTS / NATS / gRPC / FIX)
                       v
                     Your API  -->  routes under the client's OAuth  -->  Client account

OptionProfit is the analysis + order-building layer. Your platform receives a broker-agnostic order object and executes it. We never hold funds or long-lived credentials.

The order object

One normalized, broker-agnostic payload. Example — an iron condor on AAPL:

{
  "schema": "optionprofit.order/v1",
  "idempotency_key": "op_7f3c1a9e",
  "account_ref": "{broker-account-token}",
  "underlying": "AAPL",
  "strategy": "iron-condor",
  "order_type": "net_credit",
  "limit_price": 1.85,
  "time_in_force": "day",
  "quantity": 1,
  "legs": [
    { "action": "sell", "type": "put",  "strike": 190, "expiry": "2026-08-21", "ratio": 1 },
    { "action": "buy",  "type": "put",  "strike": 185, "expiry": "2026-08-21", "ratio": 1 },
    { "action": "sell", "type": "call", "strike": 210, "expiry": "2026-08-21", "ratio": 1 },
    { "action": "buy",  "type": "call", "strike": 215, "expiry": "2026-08-21", "ratio": 1 }
  ]
}

Field notes. action = buy|sell · type = call|put · order_type = market|limit|net_debit|net_credit · legs carry OCC/OSI-style strike + expiry and a ratio for uneven spreads. We map to your symbology (OCC, OSI, or your own option ids) during onboarding.

Delivery over any transport

The same order object, your protocol — you keep your existing order-routing structure:

REST       POST {your-base}/orders          Authorization: Bearer {client-token}
WebSocket  send { "type":"place_order", "order": { ... } }
MQTTS      publish  broker/{account}/orders  (TLS + client certificate)
NATS       publish  orders.place             (NATS JWT / nkey creds)
gRPC       rpc PlaceOrder(Order) returns (OrderAck)
FIX        New Order - Multileg (MsgType = AB), legs in the NoLegs group

We ship a small reference adapter for your transport; you keep full control of routing, risk checks and execution.

Auth

OAuth 2.0 on your side. The client authorizes order placement to their own account; we receive only the short-lived, order-scoped token you issue — never a password, never funds. Token refresh and revocation stay under your control.

Confirmation & idempotency

Every order carries a client-generated idempotency_key, so a retry never double-places.
We relay your OrderAck (accepted / rejected / filled) back to the client.
Nothing is submitted without an explicit client confirm step — we build the order; the client presses place.

What we need from you

Your order API + preferred transport + option symbology.
OAuth details (authorize/token endpoints, scopes for order placement).
Sandbox credentials to test against.

We integrate against your sandbox and hand you a reference adapter before any live order flows.

Security & scope

Analysis and order-building only. You keep execution, funds, KYC/suitability and every regulatory obligation. All traffic is encrypted in transit (TLS/HTTPS/HSTS); see our Security & Trust page. OptionProfit is an independent educational tool — not a broker and not a financial adviser.

Start the integration

Send your API docs (and sandbox access if you have it) to partnerships@options-strategies.com. We'll return a scoped integration plan and the reference adapter for your transport. General enquiries: For Brokers · contact.

About Us · Careers · For brokers · Contact · Methodology · Disclaimer · Privacy Policy · Cookie Policy (EU) · Terms & Conditions · Security · Home