{"_id":"56b25f012d96461700599281","user":"563cc6fa8894d20d00014ea3","__v":6,"category":{"_id":"56b25e4794ab060d00067421","pages":["56b25f012d96461700599281"],"project":"569407ac73f48f0d0075c9c9","version":"569407ad73f48f0d0075c9cc","__v":1,"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2016-02-03T20:08:39.073Z","from_sync":false,"order":9999,"slug":"connectivity","title":"Connectivity"},"githubsync":"","project":"569407ac73f48f0d0075c9c9","version":{"_id":"569407ad73f48f0d0075c9cc","project":"569407ac73f48f0d0075c9c9","__v":4,"createdAt":"2016-01-11T19:51:09.439Z","releaseDate":"2016-01-11T19:51:09.439Z","categories":["569407ae73f48f0d0075c9cd","56b25e4794ab060d00067421","56b2615b147e900d00d64995","56b3788d78a1212100900709"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1"},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2016-02-03T20:11:45.133Z","link_external":false,"link_url":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":0,"body":"Separate connections are used for market data and order management related messages, allowing different settings to be applied based on the different characteristics of the traffic.  Partners requesting access to the FIX API must register their source IP Addresses with DriveWealth.  Subsequently, DriveWealth will issue FIX CompIDs and provision our systems for access.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Connecting to UAT\"\n}\n[/block]\nEstablishing connectivity to the UAT environment is straight forward and done via an internet connection once provisioned by DriveWealth.\n[block:callout]\n{\n  \"type\": \"success\",\n  \"title\": \"FIX Order Management Endpoints\",\n  \"body\": \"fixapi01.drivewealth.io:6950\\nfixapi02.drivewealth.io:6950\"\n}\n[/block]\n\n[block:callout]\n{\n  \"type\": \"success\",\n  \"title\": \"FIX Market Data Endpoints\",\n  \"body\": \"fixmds01.drivewealth.io:6940\\nfixmds02.drivewealth.io:6940\"\n}\n[/block]\n\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Connecting to PROD\"\n}\n[/block]\nClients are responsible for initiating connections to the DriveWealth server using SSL. Once the connection is established, the client should verify the identity of the server using the SSL certificate and then initiate the normal FIX logon process.  Partners typically utilize stunnel to created the secure connection.\n[block:callout]\n{\n  \"type\": \"info\",\n  \"title\": \"stunnel Connections\",\n  \"body\": \"stunnel acts as a proxy between the client's FIX application and DriveWealth.  The FIX application will target the stunnel IP and port and stunnel will pass the traffic to DriveWealth in a secure tunnel.\"\n}\n[/block]\n\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Market Data Connection\"\n}\n[/block]\nThe market data connection is intended to keep the FIX session management overhead to the minimum, allowing for low latency delivery of market data. The messages sent on this connection are not persisted and will not be available to be resend on recovery. Further the sequence number will be explicitly reset on a reconnection and logon.\n[block:callout]\n{\n  \"type\": \"info\",\n  \"body\": \"Connectivity to market data is available from Friday 18:00 ET to Friday 17:30 ET.\",\n  \"title\": \"Market Data Availability\"\n}\n[/block]\n\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Order Management Connection\"\n}\n[/block]\nThe order management connection persists all messages sent. The sequence is reset at the end of each trading week (Friday 5:30 pm NY time).\n[block:callout]\n{\n  \"type\": \"info\",\n  \"body\": \"Connectivity to Order management is available from Friday 18:00 ET to Friday 17:30 ET.\",\n  \"title\": \"Order Management Availability\"\n}\n[/block]\nMultiple servers are available for fail-over and it is recommended that client systems make use of this high availability.","excerpt":"","slug":"connectivity-overview","type":"basic","title":"Connectivity Overview"}

Connectivity Overview


Separate connections are used for market data and order management related messages, allowing different settings to be applied based on the different characteristics of the traffic. Partners requesting access to the FIX API must register their source IP Addresses with DriveWealth. Subsequently, DriveWealth will issue FIX CompIDs and provision our systems for access. [block:api-header] { "type": "basic", "title": "Connecting to UAT" } [/block] Establishing connectivity to the UAT environment is straight forward and done via an internet connection once provisioned by DriveWealth. [block:callout] { "type": "success", "title": "FIX Order Management Endpoints", "body": "fixapi01.drivewealth.io:6950\nfixapi02.drivewealth.io:6950" } [/block] [block:callout] { "type": "success", "title": "FIX Market Data Endpoints", "body": "fixmds01.drivewealth.io:6940\nfixmds02.drivewealth.io:6940" } [/block] [block:api-header] { "type": "basic", "title": "Connecting to PROD" } [/block] Clients are responsible for initiating connections to the DriveWealth server using SSL. Once the connection is established, the client should verify the identity of the server using the SSL certificate and then initiate the normal FIX logon process. Partners typically utilize stunnel to created the secure connection. [block:callout] { "type": "info", "title": "stunnel Connections", "body": "stunnel acts as a proxy between the client's FIX application and DriveWealth. The FIX application will target the stunnel IP and port and stunnel will pass the traffic to DriveWealth in a secure tunnel." } [/block] [block:api-header] { "type": "basic", "title": "Market Data Connection" } [/block] The market data connection is intended to keep the FIX session management overhead to the minimum, allowing for low latency delivery of market data. The messages sent on this connection are not persisted and will not be available to be resend on recovery. Further the sequence number will be explicitly reset on a reconnection and logon. [block:callout] { "type": "info", "body": "Connectivity to market data is available from Friday 18:00 ET to Friday 17:30 ET.", "title": "Market Data Availability" } [/block] [block:api-header] { "type": "basic", "title": "Order Management Connection" } [/block] The order management connection persists all messages sent. The sequence is reset at the end of each trading week (Friday 5:30 pm NY time). [block:callout] { "type": "info", "body": "Connectivity to Order management is available from Friday 18:00 ET to Friday 17:30 ET.", "title": "Order Management Availability" } [/block] Multiple servers are available for fail-over and it is recommended that client systems make use of this high availability.