The available Execution Type (FIX Tag 1031) definitions and values within Docs Rate Schedules are being updated to align with industry standardization of these indicators, and will take place September 30th, 2019, impacting both the User Interface, as well as API data.
This update will result in changes to the definitions of execution types W, Y, C, G, H, and D, and the system ceasing to support newly created, or newly amended rate schedules with Execution Types other than those listed below in Table A:
|C||Vendor-provided Platform billed by Executing Broker|
|G||Sponsored Access via Exchange API or FIX provided by Executing Broker|
|H||H Premium Algorithmic Trading Provider billed by Executing Broker|
|D||Other, including Other-provided Screen|
As of September 30th, 2019, the following changes will take place for both the SOAP and REST APIs. Updated REST API documentation is attached to this email for reference and review, noting new execution method codes and descriptions on pages 10-11.
- Rate Schedule Download: No Change to Exec Type codes.
- Rate Schedule Upload: Only supported Exec Type codes, listed above, will be valid for schedule uploads. Exec Type codes outside of this list will fail validation, and not be uploaded.
- Rate Schedule Download: Historical rate lines (those existing before Sept. 30th) for Execution Types of C, G, H, and D will be passed with an “L” prefix, denoting their Legacy status. Firms will need to ensure that any necessary mapping or system updates are in place in order to accept these legacy codes on schedules accessed via API after Sept. 30th.
- Rate Schedule Upload: Only the supported Exec Type codes, listed in above in Table A, will be valid for schedule uploads. Exec Type codes outside of this list will fail validation, and not be uploaded.
|Exec Type – Before Sept. 30th||Exec Type - Sept. 30th and forward|
- Firms will need to ensure that systems consuming REST API data are able to support legacy codes being passed for rate lines containing Execution Types of C, G, H, and D, listed in Table B as of September 30th.
- Firms will need to ensure that rate schedule uploads on and after 30th only reference the supported Execution Types listed in Table A, and pass the proper Exec Type code for the method of execution denoted by a rate line.