{"id":7664,"date":"2025-12-09T17:57:17","date_gmt":"2025-12-09T23:57:17","guid":{"rendered":"https:\/\/librarytestdev.wpenginepowered.com\/?post_type=doc&#038;p=7664"},"modified":"2026-01-06T17:07:47","modified_gmt":"2026-01-06T23:07:47","slug":"adding-a-epex-spot-account","status":"publish","type":"doc","link":"https:\/\/library-staging.tradingtechnologies.com\/setup\/exchanges-emea\/epex-spot\/task-epex-spot\/adding-a-epex-spot-account\/","title":{"rendered":"Adding a EPEX SPOT Account"},"content":{"rendered":"\n<!-- pages using refernce-tab-list layout will not trigger this condition. The Heading will be set in that layout file-->\n\n  \n    \n\n\n <!-- pages using refernce-tab-list layout will not trigger this condition. The Heading will be set in that layout file-->\n\n  \n     <!-- in source YML header, should also match the filename\/url -->\n       \n        \n\n        \n      \n          \n      \n\n\n <!-- pages using refernce-tab-list layout will not trigger this condition. The Heading will be set in that layout file-->\n\n  \n    \n\n\n\n\n\n\n\n\n\n\n            <div>\n\n\n\n    <p>To add a EPEX Spot account:<\/p>\n\n    <ol>\n\n<li>Click <b>Accounts<\/b> in the left navigation pane.<\/li>\n\n<li><p>Click <b>+New Account<\/b> at the top of the Accounts screen.<\/p><p>The <b>Account Information<\/b> section is displayed.<\/p>\n\t <!--\n<p><img decoding=\"async\" class=\"img-responsive\" src=\"Content\/ttus-new-account.png\"> <\/img> <\/p> \n<p><img decoding=\"async\" class=\"img-responsive\" src=\"Content\/oms-account.png\"> <\/img> <\/p> \n\n-->\n\n    <p><img decoding=\"async\" class=\"img-responsive\" src=\"https:\/\/library-staging.tradingtechnologies.com\/wp-content\/uploads\/2025\/12\/ttus-new-cfe-acct1-2.png\">  <\/p>\n    <p><img decoding=\"async\" class=\"img-responsive\" src=\"https:\/\/library-staging.tradingtechnologies.com\/wp-content\/uploads\/2025\/12\/oms-admin-23.png\">  <\/p>\n\n    <\/li>\n\n\n\n    <li>\n        <p>In the <b>Account Name\/Number<\/b> field when creating an account, enter the up to 10-character\n            exchange-provided account name, which is required for order routing. For an internal sub-account, enter the\n            up to 10-character exchange-provided account name. The user&#8217;s routing\/clearing account is sent to the\n            exchange as Tag 1. If the user has an internal sub-account mapped to a routing\/clearing parent account, the\n            sub-account is routed to the exchange as Tag 440 and the parent account is sent as Tag 1.<\/p>\n    <\/li>\n\n    <!-- <p>The <b>Displayed Broker<\/b> field shows your company name.<\/p> -->\n\n\n<li>If this is a sub-account, select a &#8220;parent&#8221; account in the <b>Parent<\/b> field.<\/li>\n\n<li>Click the <b>Type<\/b> field and select an account type.\n\t<p> Use this field to define the routing behavior for the account and set up its\n\t\t<a href=\"ac-accounts-and-sub-accounts.html#tiered-risk\">account hierarchy for tiered risk<\/a>. All order routing\n\t\tis based on the user account. Select one of the following:\n\n\t<\/p><ul>\n\n\t\t<li>\n\t\t\t<p><b>Routing (external clearing)<\/b>: Defines the parent account as a clearing account sent to the exchange\n\t\t\t\ton all orders. If assigned to a user, the account appears in the user&#8217;s list of routable accounts. When\n\t\t\t\tselected by a user, the account is used to route orders and identify the account to the exchange (e.g,\n\t\t\t\tFIX Tag 1). If configuring this account as an omnibus account, select this option. If an internal\n\t\t\t\tsub-account is assigned to a parent account, the sub-account inherits the exchange connectivity of the\n\t\t\t\tparent account.<\/p>\n\n\n\n\t\t<\/li>\n\n\n\t\t<li>\n\t\t\t<p><b>Routing (internal sub-account)<\/b>: Defines the account as a sub-account that is not routed to the\n\t\t\t\texchange. This allows you to assign the user to an internal account for routing and risk purposes, even\n\t\t\t\tthough a parent account will be sent to the exchange as the actual clearing or omnibus account.<\/p>\n\n\t\t\t<p><b>Tip<\/b>: Sub-accounts set as &#8220;Routing (internal sub-account)&#8221; can be selected by client trading\n\t\t\t\tapplications for submitting orders, but only their parent account&#8217;s clearing account is routed to the\n\t\t\t\texchange.<\/p>\n\n\n\t\t<\/li>\n\n\t\t<li>\n\t\t\t<p><b>Non-Routing<\/b>: Not sent to the exchange. Recorded internally and can be used for back-office\n\t\t\t\tpurposes, or as a parent risk account that allows you to group a set of sub-accounts together and set\n\t\t\t\trisk for the non-routing parent.<\/p>\n\n\t\t\t<p><b>Tip<\/b>: Accounts set as &#8220;Non-Routing&#8221; are not selectable by client trading applications.<\/p>\n\n\t\t<\/li>\n\n\t\t<li>\n\t\t\t<p><b>Audit Trail Only<\/b>: Not sent to the exchange. Use this account type for the TT FIX Inbound Drop Copy\n\t\t\t\tservice, which allows third parties to import their data sources into TT. When selected, the &#8220;Order\n\t\t\t\tCross Prevention&#8221; option is disabled for this account.<\/p>\n\n\n\t\t<\/li>\n\n\t\t<li>\n\t\t\t<p><b>Error Routing<\/b>: An account that can be used to route order reject messages created by FIX Order\n\t\t\t\tRouter or FIX Inbound Drop Copy to specific Drop Copy sessions. Error accounts can be assigned to users\n\t\t\t\tand to FIX Order Routing and Inbound FIX Drop Copy sessions. An error account is not routed to the\n\t\t\t\texchange and is not part of account hierarchies.\n\n\n\t\t<\/p><\/li>\n\n\t<\/ul>\n\t\n\n<\/li><li id=\"aotc-rules\">To prevent order crossing using this account or any of its sub-accounts, click the\n\t<a href=\"#aotc-section\"><b>Order Cross Prevention<\/b><\/a> field and select an order crossing rule. The TT Trade\n\tapplication performs the following order actions based on which rule is selected:\n\n\t<ul>\n\n\t\t<li><b>Not Applied<\/b> \u2014 No order cross prevention rule is applied to the account.\n\t\t<\/li><li><b>Reject New<\/b> \u2014 Reject a new order that could potentially fill resting orders in the same account or account tree. Applies to only Limit orders and native Iceberg orders.<\/li>\n\n\n\t\t<li><b>Cancel Resting (wait for ACK)<\/b> \u2014 Send a cancel request to the exchange for the \n\t\t\tresting order. When the exchange acknowledges the request and cancels the order, submit the new order. Applies to only Limit orders and native Iceberg orders.<\/li>\n\n\t\t<li><p><b>Position Transfer<\/b> \u2014 \n         When a match is detected, the resting order is canceled or the working order quantity is reduced by the size of the aggressive order. A fill is created by TT and sent to each account. If the aggressive order was larger than the resting order, then the remainder of it will be sent to market.  For a description of how Position Transfer works, refer to <a href=\"ocp-position-transfer.html\">Position Transfer<\/a>.<\/p>\n\n\n\n\t\t <\/li><li><p><b>Position Transfer (if resting order is best bid\/offer)<\/b> \u2014 This rule works the same as <b>Position Transfer<\/b> except that the internal matching occurs only if an order has the potential to fill a resting order at the current best bid\/ask price.<\/p> \n\n\t\t \t<p><b>Note<\/b>: When using this rule, the resting order may get matched and filled at the exchange while the aggressive order is in flight.<\/p>\n\n\t\t \t\n\t\t\t\n\t\t<\/li><\/ul>\n\t<\/li>\n\n\n\n\n\n<li>Optionally, check one of the following options:\n\n\t\t<ul>\n\n\t\t<li><strong>Use Reject New instead of Position Transfer within the same account<\/strong> \u2014 When enabled, this setting prevents the use of position transfer within the same account and uses &#8220;Reject New&#8221; for order cross prevention. This setting is active when &#8220;Position Transfer&#8221; is selected for the account, otherwise, it is grayed-out.<\/li>\n\n\n\t\t<li><b>Go to market with Position Transfer balances w\/o waiting for Cancel\/Reducing ACK<\/b> \u2014 When enabled, Position Transfer does the following if the aggressive order quantity is larger than the resting order quantity:\n\t<ul>\n\t\t<li>Reduces the aggressive order quantity by the amount of the resting order<\/li>\n\t\t<li>Submits a request to the exchange to cancel the resting order, followed immediately by an order for the remaining quantity without waiting for acknowledgement that the resting order was canceled or reduced.\n\t\t<\/li>\n\t\t<!-- <li>After receiving acknowledgement that the resting order is canceled, internal fills are created and transferred to each trader's account.<\/li> -->\n\t<\/ul>\n\n<p>For example, if a 2-lot Sell order is resting when a 10-lot Buy order is entered that matches, Position Transfer immediately sends a cancel request to the exchange for the Sell order, followed by an 8-lot Buy order. Position Transfer then waits for the exchange to acknowledge that the 2-lot Sell order was canceled successfully. After receiving acknowledgement, the 2-lot fills are created internally and transferred to each trader&#8217;s account.\n<\/p>\n\n<p>Using this option, you can submit part of the order to the market sooner while the remainder of the order waits to be transferred. You can also reduce the risk of the entire aggressive order being rejected while waiting for the position transfer to complete.<\/p>\n\n<p><b>Note<\/b>: With this option, there&#8217;s a risk that the crossing orders may match at the exchange if the two traders are using separate exchange connections on two different order routing servers.<\/p>\n\n<!-- <p>When applying the Position Transfer rule to prevent order crossing, consider the following:<\/p>\n\n            <ul>\n\t\t\t\t <li>The Trade application uses the price of the resting order and not the newly submitted (held) order.<\/li>\n\n\t\t\t\t<li>Position Transfer is only applied to Limit and Native Iceberg order types.<\/li>\n\n\t\t\t\t<li>Orders submitted by ADL algos behave the same as non-ADL orders with regards to risk and fills.<\/li>\n\t\t\t\t<li>Position Transfer applies to orders for exchange-defined spreads and \n\t\t\t\t\tstrategies. Upon matching on price, synthetic spread and leg fills are created for the account.\n\t\t\t\t<\/li>\n\n\t\t\t<\/ul> -->\n\n\n<\/li><li><b>Disable trading (this account only)<\/b> \u2014 Disables trading for this account. This checkbox is checked by\n\tdefault.<\/li>\n\n\n\n<li><b>Disable trading (sub-accounts)<\/b> \u2014 Disables trading for all child accounts of this\n\tparent account.<\/li>\n\n<li><b>Disable trading (autoliquidate)<\/b> \u2014 Checked automatically after auto-liquidate is triggered\n\ton an account. Increase the credit limit and uncheck this option to restore trading to a liquidated account. This\n\tsetting can only be checked by the Setup application when an account is liquidated (i.e., you cannot manually check\n\tthis setting).<\/li>\n\n\n<li><b>Disable trading (max order limit reached)<\/b> \u2014 trading will be disabled after the specified maximum order limit, specified in connections, has been breached. \n<\/li>\n\n<li><b>Include on Score<\/b> \u2014 This account will be utilized for TT score Surveillance models.<\/li>\n\n<li><b>Include on FIX Drop Copy<\/b> \u2014 The trades from this account will be included on the FIX drop copies generated.<\/li>\n\n\n\n<\/ul>\n<\/li>\n\n\n\n\n<li>Optionally, configure the <b>Prevent Duplicate Orders<\/b> settings:\n\n\t<ul>\n\t\t<li><b>Check Quantity<\/b> \u2014 Sets the number of duplicate orders to allow within\n\t\t\tthe configured time frame.<\/li>\n\t\t<li><b>Check Time Frame<\/b> \u2014 Sets the time frame in milliseconds and enables the duplicate order check\n\t\t\tfor the account. Enter a value from 1-999999999. When the number of orders for the same instrument and price\n\t\t\tset in the <b>Check Quantity<\/b> field occurs within the configured time frame, the\n\t\t\tduplicate orders are rejected. When <b>Check Time Frame<\/b> is blank, no duplicate order check is\n\t\t\tapplied to the account.<\/li>\n\n\t\t<li><b>Apply to sub-accounts<\/b> \u2014 Copies the &#8220;Prevent Duplicate Orders&#8221; settings from the parent account\n\t\t\tto their child accounts. This ensures that any sub-accounts added to the shared parent account cannot have a\n\t\t\tdifferentmissing value in this field . When checked, the value cannot be changed on any sub-accounts added\n\t\t\tby your company or a shared company.\n\t<\/li><\/ul>\n\n\n<\/li>\n\n\n\n\n<li>In the <b>Order Management System (OMS) Settings<\/b> section, configure the following:\n\n\t<ul>\n\n<li><b>Lock fill notifications on new staged orders<\/b> \u2014 Controls how fills are reported back to the care order originator. When this setting is checked, new care orders are automatically locked when they are claimed. Fills for locked orders will have to be manually allocated and released. When unchecked, fills and fills prices are immediately released back to the customer using the average prices calculated by TT. This setting supports the Lock and Release functionality in TT OMS.<\/li>\n\n\n<li><b>Only combine orders with the same price<\/b> \u2014 Restricts how care orders are bulked. When this setting is checked, only care orders with the same price can be added as part of a bulk order. When unchecked, care orders at different prices can be bulked. Bulking requires that all care orders have the same product and Buy\/Sell side. This setting supports the Bulking functionality in TT OMS.<\/li>\n\n\n<li><b>Only combine orders with the same account<\/b> \u2014 Restricts how care orders are bulked. When this setting is checked, only care orders with the same account can be added as part of a bulk order. When unchecked, care orders in different accounts can be bulked. Bulking requires that all care orders have the same product and Buy\/Sell side. Supports the Bulking functionality in TT OMS.<\/li>\n\n\n<li><b>Only combine orders with the same customer<\/b> \u2014 Restricts how care orders are bulked. When this setting is checked, only care orders with the same order profile can be added as part of a bulk order. When unchecked, care orders with different customer order profiles can be bulked. Bulking requires that all care orders have the same product and Buy\/Sell side. Supports the Bulking functionality in TT OMS.<\/li>\n\n<\/ul>\n\n\n\n<\/li><li>Click <b>Create<\/b>. <p>The new account appears in the Accounts list in the data grid. Sub-accounts appear as nested\n\t\tunder their parent account.<\/p>\n<\/li>\n\n\n\n<\/ol>\n\n\n\n    <h2 id=\"epex\">Configuring EPEX Spot exchange properties<\/h2>\n\n    <!-- Include the steps for accessing the exchange properties -->\n    <ol>\n\n\t<li>Click <b>Accounts<\/b> in the left navigation pane and select an account in the data grid.<\/li>\n\t\t<li>Click the <b>Exchanges<\/b> tab for the selected account.<\/li>\n\t\t<li>Click the <b>Select an Exchange<\/b> selector to find and select \n\t\t\t\n\t\t\t\n\n\t\t an exchange.\n\t\t \n\t\t <\/li>\n\t\t<li>Configure the settings in the <b>Exchange Properties<\/b> section.\n\n\n    <p><img decoding=\"async\" class=\"img-responsive\" src=\"https:\/\/library-staging.tradingtechnologies.com\/wp-content\/uploads\/2025\/12\/ttus-new-epex-acct2.png\">  <\/p>\n\n\n    <p>Configure the following settings:<\/p>\n\n    <ul>\n\n        <li>\n            <p><b>Account Type<\/b> \u2014 Select either <b class=\"gui\">Customer Account<\/b> or <b class=\"gui\">Own Account<\/b>. An account type is required to submit orders for Spot products.<\/p>\n        <\/li>\n\n        <li>\n            <p><b>Trading Capacity<\/b> \u2014 Indication of whether the trader is trading for their own proprietary\n                account (Deal), acting as a market maker (Match), or acting in the capacity of agent (Any other\n                capacity). This setting is required. Valid values:<\/p>\n            <ul>\n                <li>\n                    <p>Deal: 1815=5 &#8220;Principal (Proprietary)&#8221;<\/p>\n                <\/li>\n                <li>\n                    <p>Match: 1815=6 &#8220;Market Maker&#8221;<\/p>\n                <\/li>\n                <li>\n                    <p>Any other capacity: 1815=1 &#8220;Customer (Agency)&#8221;<\/p>\n                <\/li>\n            <\/ul>\n\n        <\/li><li>\n\n            <p>The <b>Clearing Account<\/b> field can be used to set the TT account value in Tag 1 on order\n                actions sent to the exchange. If the user has an internal sub-account mapped to a routing\/clearing\n                parent account, the sub-account is routed to the exchange as Tag 440 and the parent account name is\n                replaced with the <b>Clearing Account Override<\/b> as Tag 1.<\/p>\n\n            <p>The clearing account override name is\n                user-defined and this field is optional.<\/p>\n        <\/li>\n\n        <li><b>Customer Order Handling Instruction<\/b> \u2014 Available values include:\n            <ul>\n                <li>Desk<\/li>\n                <li>Electronic (Default)<\/li>\n                <li>Vendor-provided Platform, billed by Executing Broker<\/li>\n                <li>Sponsored Access via Exchange API or FIX, provided by Executing Broker<\/li>\n                <li>Premium Algorithmic Trading Provider, billed by Executing Broker<\/li>\n                <li>Other, including Other-provided Screen<\/li>\n\n\n            <\/ul>\n        <\/li>\n\n\n        <li><b>TT SMP ID<\/b> \u2014 A user-defined, alphanumeric identifier used to tag orders so the TT system can\n            match potential crossed trades. For more information on TT Self Match Prevention, refer to the <a href=\"\/user-setup\/ocp-tt-self-match-prevention-by-id.html\">TT\n                Self Match Prevention By ID<\/a> section in the Setup help.<\/li>\n\n        <li><b>TT SMP Instruction<\/b> \u2014 Sets the TT Self Match Prevention (TT SMP) behavior and determines which\n            order is canceled (resting or aggressing) if self-match prevention occurs. For more information on TT Self\n            Match Prevention, refer to the <a href=\"\/user-setup\/ocp-tt-self-match-prevention-by-id.html\">TT\n                Self Match Prevention By ID<\/a> section in the Setup help.<\/li>\n\n\n\n        <!-- Include Direct Electronic Access description -->\n\n\n\n        \t<li><b>Direct Electronic Access<\/b> \u2014 Sets whether or not the order is sent from direct\/sponsored access, or from another source. Valid values:\n\t\t\t\t\t<ul>\n\t\t\t\t\t\t<li>None<\/li>\n\t\t\t\t\t\t<li>Yes<\/li>\n\t\t\t\t\t<li>No<\/li>\n\t\t\t\t<\/ul>\n\t\t\t<\/li>\n\n        <p>Sent to the exchange in Tag 1724.<\/p>\n\n        <\/ul><\/li>\n\n\n        <li><b>Liquidity Provision<\/b> \u2014 Indication of market making. Valid values:\n\t\t\t\t\t<ul>\n\t\t\t\t\t\t<li>None<\/li>\n\t\t\t\t\t\t<li>Yes<\/li>\n\t\t\t\t\t<li>No<\/li>\n\t\t\t\t<\/ul>\n        <\/li>\n\n\n        <li><b>Commodity Derivative Indicator<\/b> \u2014 Indication of whether the order is for hedging purposes to reduce risk. Valid values:\n\t\t\t\t\t<ul>\n\t\t\t\t\t\t<li>None<\/li>\n\t\t\t\t\t\t<li>Yes<\/li>\n\t\t\t\t\t<li>No<\/li>\n\t\t\t\t<\/ul>\n        <\/li>\n\n\n        <li><b>Investment Decision ID<\/b> \u2014 User or firm who made the trading decision. Enter a registered ID\/Short Code.<p>This field supports up to 15 characters.<\/p>\n        <\/li>\n        <li><b>Investment Decision Qualifier<\/b> \u2014 Determines if the trading decision was made manually by a user or automatically by an automated trading application using this account. This is an optional field. Select one of the following: \n\t<ul>\n\t\t<li><b>Manual<\/b>: Indicates the trading decision was made by a person.\n\t\t<\/li><li><b>Automatic<\/b>: Indicates the trading decision was made by an automated trading application.\n\t<\/li><\/ul>\n<\/li>\n\n        <li><b>Execution Decision ID<\/b> \u2014 User or firm that submitted the order. Enter a registered ID\/Short Code.<p>This field supports up to 15 characters.<\/p>\n        <\/li>\n\n\n        <li><b>Execution Decision Qualifier<\/b> \u2014 Determines if the user or firm sent the order manually or automatically using an automated trading application with this account. This is an optional field. Select one of the following: \n\t<ul>\n\t\t<li><b>Manual<\/b>: Indicates the order was sent manually.\n\t\t<\/li><li><b>Automatic<\/b>: Indicates the order was sent automatically.\n\t<\/li><\/ul>\n<\/li>\n\n        <li><b>Secondary Execution Decision ID<\/b> \u2014 Secondary user or firm associated with the order. This field can be used for trading on behalf of clients and used for internal reporting purposes. Enter a registered ID\/Short Code.\n        <\/li>\n\n        <li><b>Client ID<\/b> \u2014 Customer identification. Enter the customer&#8217;s legal entity identifier (LEI\/Short Code).\n\n        <p>Enter an 8-byte value: Own Account (00000000), Pending Allocation (00000001), Aggregation of multiple Client\n            Orders (00000003), or free-form ID.<\/p>\n        <\/li>\n\n        <li><b>Secondary Client ID<\/b> \u2014 Secondary customer identifier associated with the order. This field can be used for trading on behalf of clients and used for internal reporting purposes. Enter the customer&#8217;s legal entity identifier (LEI\/Short Code).\n\n        <\/li>\n\n        <li><b>Client ID Type<\/b> \u2014 Identifies the type of client submitting the order. Select either &#8220;Firm&#8221; or\n            &#8220;Natural Person&#8221;.<\/li>\n\n\n        \n<li><b>Execution Firm<\/b> \u2014 Identifies the firm or user managing the account. Enter a user-defined value.<\/li> \n\n\n\n\n        <li><b>Free-form 1-20<\/b> \u2014 Optional, user-defined text fields that can be populated for TT and FIX client application users. These values are not sent to the exchange, but are visible in the Order Book, Fills, and Audit Trail widgets and on FIX Drop Copy records.<\/li> \n\n\t\t<p><img decoding=\"async\" class=\"img-responsive\" src=\"https:\/\/library-staging.tradingtechnologies.com\/wp-content\/uploads\/2025\/12\/account-fft-26.png\">  <\/p> \n\n\n        <li><b>Apply to all sub-accounts<\/b> \u2014 Allows a company creating a sub-account or sharing an account with another company to apply the parent account exchange field to the sub-account. This ensures that any sub-accounts added to the shared parent account cannot have a different value in this field and that the value is sent to the exchange. Check the checkbox next to each field to apply its value as needed. When checked, the value cannot be changed on any sub-accounts added by your company or a shared company.<\/li>\n        <li><b>Lock sub-accounts<\/b> \u2014 Allows a company creating a sub-account or sharing an account with another company to lock the value in a sub-account exchange field even if the sub-account is configured with a more specific order tag default match. This ensures that any child accounts (sub-accounts) created from the shared parent account cannot have a different value in this field and that the value is sent to the exchange. When checked, the value cannot be changed on any sub-accounts added by your company or a shared company. <b>Note<\/b>: The <b>Apply to all sub-accounts<\/b> setting must be enabled for the field in order to enable the <b>Lock sub-accounts<\/b> setting.\n\n<\/li>\n\n        <li><b>Client Can Override<\/b> \u2014 Determines if a user can override the value in this field when submitting orders from trading applications or APIs. Check the check box to unlock the field and allow a user to override the value. When unchecked, the field is locked and the user cannot change it. <!--This setting is unchecked by default.-->\n\n\t\t\t<\/li>\n\n\n\n    \n\n    <!-- Save Changes button -->\n    \n\t\t<li>Click <b>Save Changes<\/b>.<\/li>\n\t<\/ol>\n\n\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>To add a EPEX Spot account: Click Accounts in the left navigation pane. Click +New Account at the top of the A [&hellip;]<\/p>\n","protected":false},"author":2,"template":"","meta":{"_acf_changed":false,"footnotes":""},"docs-category":[683],"class_list":["post-7664","doc","type-doc","status-publish","hentry","docs-category-task-epex-spot"],"acf":[],"_links":{"self":[{"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/doc\/7664","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/doc"}],"about":[{"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/types\/doc"}],"author":[{"embeddable":true,"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/users\/2"}],"version-history":[{"count":0,"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/doc\/7664\/revisions"}],"wp:attachment":[{"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/media?parent=7664"}],"wp:term":[{"taxonomy":"docs-category","embeddable":true,"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/docs-category?post=7664"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}