Order flow, positions and quotes behind a BlackArrow session

Every BlackArrow session authenticates a trader and then carries two live channels: a market-data stream and an order-routing link to the broker the account sits at. That is where the value is. The chart, the indicator stack and the watchlist columns are a front end; underneath, the app holds a trader's open positions, working and historical orders, and a continuous quote feed across B3 and global instruments. An integration that respects the account holder's consent can read all of it.

The route we would take is authorized protocol analysis of the BlackArrow client's own authenticated traffic, operated against a consenting account. It does not depend on anything Nelogica publishes, it covers the per-account data a trader actually sees, and where the linked broker participates in Open Finance Brasil we can add the regulated investment-data path for normalized holdings. The rest of this brief sets out the surfaces, the wire shapes, and what we hand over.

What sits behind a BlackArrow login

Getting at that data under authorization

Three routes genuinely apply here; one is the spine.

Authorized protocol analysis of the session

We analyse the BlackArrow client's authenticated traffic — the login and token handshake, the order-routing channel, the account and position queries, the quote subscription — and rebuild the parts a third party needs as clean endpoints. Reach is wide: everything the trader can see in the app. Effort is moderate; durability is good once the decode is pinned and a verification suite guards against client drift. Access is arranged with you during onboarding and the build runs against a consenting account. This is the route we would recommend, because it covers per-account data directly and does not wait on anyone else's roadmap.

User-consented credential access

The account holder consents, and the integration operates inside their own session for positions, fills and watchlists. Lower engineering cost, narrower than full protocol work, and a good fit when one trader or a small desk needs their own data exported on a schedule.

Open Finance Brasil investment-data sharing

Where the broker the account is linked to participates in Open Finance Brasil, consented investment-data sharing gives a regulated, normalized view of holdings. It does not reach BlackArrow-specific surfaces like indicator setups or the tick feed, so we treat it as a complement to the session work, not a replacement.

What the authenticated traffic looks like

Illustrative shapes, confirmed against an authorized BlackArrow session during a build — not copied from any published document. Names are normalized for the brief.

# 1. Authenticate the trader; obtain a short-lived session token.
POST  /auth/login        { user, secret, device_id }
      -> { session_token, ttl_seconds }

# 2. Open the routing context for the linked broker.
OPEN  routing(session_token, broker_id)
      -> { account_ref }

# 3. Pull open positions and order history for that account.
GET   positions(account_ref)
      -> [ { symbol, qty, avg_price, side, open_pnl } ]
GET   orders(account_ref, from_ts, to_ts)
      -> [ { order_id, symbol, side, qty, price, status, ts } ]
      # status walks: NEW -> PARTIAL -> FILLED | CANCELLED | REJECTED

# 4. Subscribe market data on a separate, binary-framed channel.
SUB   quotes(session_token, [ symbols ])
      -> stream{ symbol, last, bid, ask, aggression, ts }

on session_drop:  re-auth, replay from last order_id cursor, resubscribe symbols
on token_expiry:  refresh before ttl; do not stall the quote stream on the refresh
      

The two channels behave differently. Order routing is state-sensitive and must be reconstructed from status transitions so a partial fill is never double-counted. The quote channel is high-volume and needs a resync-on-drop consumer, not a naive poller.

What lands at the end of the build

For BlackArrow the package is concrete and tied to the surfaces above:

• An OpenAPI specification covering authentication, positions, order history and the quote subscription as normalized endpoints.
• A protocol and auth-flow report: the login and token handshake, refresh timing, the routing-context open, and the binary framing of the market-data channel.
• Runnable source for the key endpoints in Python and Node.js, including the resync-on-drop consumer and the order-state reconstruction.
• Automated tests against recorded session fixtures, plus the verification suite that flags client drift.
• Interface documentation and data-retention guidance written for the Brazilian rulebook the account falls under.

A build of this size lands in roughly one to two weeks.

Where integrators put this

• A risk desk syncing every trader's BlackArrow positions into one consolidated exposure dashboard.
• An automated trade journal that reconstructs fills and computes a tax-ready P&L from the order history.
• Position aggregation across several brokers where traders use BlackArrow on top of different linked accounts.
• A market-data pipeline feeding a backtester from the tick-with-aggression stream.
• A compliance archive that retains a signed, timestamped record of orders for the period CVM expects.

Consent and the Brazilian rulebook for this data

The account behind BlackArrow is a brokerage account: it is governed by CVM, by Banco Central do Brasil, and by B3's market procedures, while the personal data inside it falls under the LGPD with the ANPD as supervisory authority. Nelogica's own product page frames the company as a technology facilitator that does not give investment recommendations, which means the regulated account relationship belongs to the trader and their broker — and so does the consent. We work only on explicit account-holder authorization, keep consent records and access logs, minimize the fields we pull to what the integration needs, and sign an NDA where the engagement calls for one. Where the linked broker is an Open Finance Brasil participant, consented investment-data sharing is the regulated path and we use it for normalized holdings rather than reconstructing them.

Engineering realities we plan around

Two things about BlackArrow shape how the build is designed, and we handle both inside the engagement.

First, BlackArrow is a thin client over a broker-routed session, so positions and fills reflect whichever institution the trader linked. The routing context and account identifiers differ by broker. We map the integration per linked broker and run it against a consenting account arranged with you at onboarding, so the work is correct for the specific institution rather than a generic guess.

Second, the market-data channel is binary-framed and carries B3 and global symbols in the same stream. We decode the frame format, reconcile every symbol against an exchange-tagged instrument master so a B3 ticker is never confused with a same-named foreign listing, and design the consumer to resync on a session drop rather than silently leave a gap. Client releases occasionally reshape how fields are framed; the maintenance plan budgets for a decode refresh and ships an updated build inside the normal cycle.

Keeping a BlackArrow feed honest over time

Two failure modes matter for a long-running integration. Session tokens are short-lived, so the consumer refreshes ahead of expiry and never blocks the quote stream while it does. And the app exposes only a bounded window of intraday and recent history on demand, so the integration backfills within that window and persists everything beyond it on our side — a later request for last quarter's fills reads our store, not a window the app no longer serves.

Screens from the app

Comparable software in the same space

An aggregation layer rarely sees BlackArrow alone, so it helps to know what sits next to it. These are named for ecosystem context only, not ranked.

• Profit — Nelogica's flagship Brazilian client, strong on order-flow and tape reading, with a similar broker-routed account model.
• Vector — Nelogica's other trading platform, sharing much of the same backend and instrument coverage.
• Tryd — a Brazilian platform built for fast scalping in mini contracts, holding the same kind of per-account order state.
• MetaTrader 5 — global multi-asset platform reaching B3 through some brokers, with positions and order history per linked account.
• TradingView — browser-first charting and a social network; holds watchlists, alerts and saved studies per user.
• Tradezone — a Brazilian trading front end with broker connectivity and order routing comparable to BlackArrow.
• Bookmap — order-book visualization (Nelogica holds a majority stake per its corporate announcement); depth-of-market data per session.
• cTrader — depth-of-market and algo-oriented platform with per-account positions and an order API surface.
• ProRealTime — charting and automated execution with broker links, holding strategy and order data per user.

Questions integrators ask about BlackArrow

Does BlackArrow's position and order data come from Nelogica or from the broker the account is linked to?

Both, at different layers. Nelogica's backend authenticates the BlackArrow session and carries the quote feed, but balances, open positions and fills belong to the brokerage account the trader linked. An integration reads account state through the routed session against that specific broker, so the work is scoped to the institution the account sits at.

Can you separate the B3-listed instruments from the global assets BlackArrow shows in one feed?

Yes. BlackArrow exposes a mixed symbol catalogue spanning B3 equities, futures and indices alongside global stocks, ETFs and currency pairs. We reconcile the app's symbols against an exchange-tagged instrument master so a downstream system never conflates a B3 ticker with a same-named foreign listing.

How does Brazilian regulation shape pulling a trader's BlackArrow order history?

The account is governed by CVM rules and B3 market procedures, and the personal data inside it falls under the LGPD. Access runs on the account holder's explicit consent or written authorization, with consent records and access logs kept. Where the underlying broker participates in Open Finance Brasil, consented investment-data sharing is the regulated path for normalized holdings.

If Nelogica reshapes the BlackArrow client between releases, does the integration stop working?

Client releases can change how fields are framed on the wire. The build pins the decoded shapes and ships with a verification suite that flags a drift fast; a decode refresh and an updated build fit inside the normal one-to-two-week cycle rather than a rewrite.

What was checked, and when

For this brief I read BlackArrow's Google Play listing for the package identifier and the feature copy (Chart Trading, Market Monitor, the 100+ indicators including Moving Averages, IFR and VWAP), Nelogica's BlackArrow product page for the product framing and its technology-facilitator disclaimer, B3's non-resident market-rules material and the CVM framework it describes for the Brazilian account context, and Nelogica's corporate announcement for the company's scope. Checked May 2026.

• BlackArrow on Google Play
• Nelogica — BlackArrow product page
• B3 — operational procedures and regulation
• Nelogica corporate announcement (Bookmap stake)

Mapped by the OpenBanking Studio integration desk · 2026-05-18.

Source for the BlackArrow endpoints is delivered from $300, and you pay after delivery once it runs and you are satisfied; if you would rather host nothing, the same integration is available as a metered endpoint you call and pay per request, with nothing upfront. Either way the cycle is one to two weeks, you give us the app name and what you need from its data, and access and compliance are arranged with you. Start at /contact.html and we will scope it.