Build on the Rail

Direct API access to liquidity, pricing, and AIDANN intelligence.
Integrate the IDBX rail directly into your OMS/EMS.

DeveloperAPI · Integration

One venue. One API.Everything the desk can see.

The venue exposes what it knows through one interface: the consolidated book, your own obligations and settlement state, the netting set AIDANN computes, and the answers it gives. The same surface a trader sees on screen, addressable from your own systems.

The interface is specified and exercisable in a sandbox. Production access follows authorisation and institutional onboarding, and is granted per participant.

Sample requestSandbox · illustrative

      
Response200 OK

      

    

  


  

    
 Scroll

    

      
      London --:--
      New York --:--
      Singapore --:--
    

  





Developer & API
Protocols
FIX 5.0 SP2, REST, WebSocket’s 
AIDANN via API
Pipe AI-driven liquidity analysis directly 
into internal dashboards
Sandbox
Test integration against live 
market data





  

    
Live · rendered in your browser

    
Four calls, and what comes back.

    
The surface is small on purpose. Read the book, read your
      own position, read what nets, and ask AIDANN a question. Pick one and the
      request and its response are written out as they would arrive.


    

      

      

        
RequestSandbox · illustrative

        

        

          Response200 OK
        

        

        

      

    

  


  

    
The contract

    
What an integration can rely on.

    
These are design commitments rather than a service level.
      What they describe is how the interface behaves, not how fast it runs: no
      throughput or latency figure is published here, because none has been measured
      in production.


    

      

        
Authenticated per participant

        
Credentials are issued to an institution, not to an application, and every
          call is attributable to the participant that made it.

      

      

        
Versioned in the path

        
The version sits in the URL. A breaking change is a new version, not a
          silent change to the one you already build against.

      

      

        
Idempotent writes

        
Anything that changes state takes a client key, so a retry after a timeout
          cannot produce a second instruction.

      

      

        
Limits published, not discovered

        
Rate limits are stated in the documentation and returned in the response
          headers, so a client can back off before it is refused.

      

    


    
The interface is specified and exercisable in a sandbox.
      Production access follows authorisation and institutional onboarding. IDBX
      Markets Ltd is not currently authorised by the Financial Conduct Authority,
      and nothing here constitutes an offer of regulated services.

  






System Limits
Capacity agreed at onboarding.
Performance and capacity are set out in the rules of engagement and agreed with each participant during onboarding. Rate limits are 
negotiable for Market Makers.