[ Integration overview ]

One API between your product and the market maker.

Receive executable prices, request firm quotes, send orders and consume execution reports without maintaining a separate integration for every venue.

Illustrative RFQ lifecycle Connected
  1. 01
    REQUESTInstrument · side · quantity
  2. 02
    QUOTEFirm price · quote ID · validity
  3. 03
    ACCEPTQuote ID · client order ID
  4. 04
    REPORTStatus · price · filled quantity

Conceptual flow. Client schemas and supported fields are supplied during integration.

[ What you can build ]

Executable workflows, not another indicative data feed.

01

FIX 4.4

Connect automated and institutional order workflows through an established trading protocol.

02

REST

Bring quote and execution workflows into broker, exchange, wallet and application backends.

03

Streaming prices

Consume executable two-way prices for the instruments enabled for your relationship.

04

Firm RFQ

Request a price for a defined instrument, direction and quantity, with explicit validity.

05

Order entry

Submit supported IOC and FOK orders with client identifiers and deterministic responses.

06

Execution reports

Carry acknowledgement, fill and status information into your customer and operational records.

[ Sandbox access ]

See the workflow before you plan the integration.

Explore the Stelaxis trading environment and see how pricing, orders, controls and post-trade activity fit together. When you are ready to connect systems, we will scope API access around your actual flow.

[ Available now ]

Open the Stelaxis sandbox.

Use the web environment for an initial product review. API credentials and configured instruments are provided separately for qualified integrations.

[ Request to record ]

The trading lifecycle stays connected.

Use one integration for the pricing and execution path, then retain the same trade context as the transaction moves into controls, settlement and reconciliation.

  1. 01

    Authenticate and subscribe

    Connect to the agreed environment and request the instruments and pricing modes enabled for your account.

  2. 02

    Receive or request a price

    Consume an executable stream or send an RFQ with the instrument, side and quantity.

  3. 03

    Execute with a clear state

    Submit the order or accept the quote and receive a defined acknowledgement, fill or rejection.

  4. 04

    Carry the result downstream

    Use execution identifiers and reports to support customer records, settlement and reconciliation.

[ Path to production ]

Integrate around the flow you actually intend to launch.

We start with your customer journey, markets, expected sizes, geography and settlement model. That defines the appropriate commercial relationship and a focused technical certification plan.

  1. QualifyAgree the use case, instruments, expected flow, jurisdiction and target launch.
  2. ConfigureSet the pricing mode, credentials, limits and sandbox environment for your workflow.
  3. CertifyTest order states, failure paths, identifiers and operational hand-offs—not only the happy path.
  4. LaunchMove to production after technical, commercial, legal and operational readiness are confirmed.

[ Defined before production ]

No ambiguity about what the connection covers.

01

Markets

Enabled instruments, pricing modes and supported order types.

02

Flow

Expected volumes, typical order sizes and applicable limits.

03

Settlement

Supported assets, currencies, wallets and operational cut-offs.

04

Counterparty

Contracting entity, eligibility, jurisdiction and relevant service terms.

Availability depends on instrument, jurisdiction, client eligibility, onboarding and the agreed contracting entity.

[ Start with your use case ]

Tell us what you are building and the flow you expect.