<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Broker API Hub: IG API changes</title>
    <link>https://openbrokerapi.com/brokers/ig</link>
    <description>Dated changes, each with the page it was read on. Independent and unofficial.</description>
    <language>en-GB</language>
    <lastBuildDate>Mon, 12 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://openbrokerapi.com/feeds/ig.xml" rel="self" type="application/rss+xml"/>
    <item>
      <title>IG: IG&apos;s REST reference opened on 12 Oct 2026 at labs.ig.com/rest-trading-api-reference.html,...</title>
      <link>https://openbrokerapi.com/changes</link>
      <description>IG&apos;s REST reference opened on 12 Oct 2026 at labs.ig.com/rest-trading-api-reference.html, after refusing our reader in September. It prints the working order paths with a hyphen: /working-orders, /working-orders/otc and /working-orders/otc/{dealId}. This site had recorded /workingorders, the spelling in IG&apos;s own deprecated Java sample. The three records now carry the reference spelling and are marked conflicting, because IG&apos;s two sources disagree and neither was tested against a host. The address without .html answered 500 the same day, so the eighteen records that linked it now link the page for their own call. Source: IG Labs REST trading API reference: /working-orders, https://labs.ig.com/reference/working-orders.html</description>
      <pubDate>Mon, 12 Oct 2026 00:00:00 +0000</pubDate>
      <category>Documentation</category>
      <guid isPermaLink="false">urn:openbrokerapi:change:ig-2026-10-12-71</guid>
    </item>
    <item>
      <title>IG: Re-read against IG&apos;s reference on 12 Oct 2026, four IG records changed which fields they...</title>
      <link>https://openbrokerapi.com/changes</link>
      <description>Re-read against IG&apos;s reference on 12 Oct 2026, four IG records changed which fields they call required. Required now means only what the page marks as not null: size alone on DELETE /positions/otc; currencyCode, epic, expiry, forceOpen, guaranteedStop and size on POST /positions/otc; currencyCode, epic, expiry, guaranteedStop, level and size on POST /working-orders/otc. The page marks searchTerm optional on the market search. The _method header on deleting a working order is now recorded as optional, not required: IG&apos;s reference documents a plain DELETE, and IG&apos;s FAQ offers a POST with _method: DELETE only for clients that cannot send a body on a DELETE. This describes IG&apos;s page, not a test of what the host accepts. Source: IG Labs REST trading API reference: /positions/otc, https://labs.ig.com/reference/positions-otc.html</description>
      <pubDate>Mon, 12 Oct 2026 00:00:00 +0000</pubDate>
      <category>Documentation</category>
      <guid isPermaLink="false">urn:openbrokerapi:change:ig-2026-10-12-72</guid>
    </item>
    <item>
      <title>IG: Three IG Labs addresses this site cited answered 500 on 12 Oct 2026 without a file ending...</title>
      <link>https://openbrokerapi.com/changes</link>
      <description>Three IG Labs addresses this site cited answered 500 on 12 Oct 2026 without a file ending and opened with one: the REST trading API guide, the FAQ and the streaming API guide now sit at rest-trading-api-guide.html, faq.html and streaming-api-guide.html. The IG record links the working addresses. The claims read there are unchanged: the FAQ still gives 12 hours for the session tokens and the guide still gives 6 hours extended up to 72. Source: IG Labs FAQ, https://labs.ig.com/faq.html</description>
      <pubDate>Mon, 12 Oct 2026 00:00:00 +0000</pubDate>
      <category>Documentation</category>
      <guid isPermaLink="false">urn:openbrokerapi:change:ig-2026-10-12-73</guid>
    </item>
    <item>
      <title>IG: This site&apos;s streaming entry for IG now names Lightstreamer, as IG&apos;s Streaming API Guide...</title>
      <link>https://openbrokerapi.com/changes</link>
      <description>This site&apos;s streaming entry for IG now names Lightstreamer, as IG&apos;s Streaming API Guide does throughout, and no longer says IG states the 40 subscription cap cannot be increased: the guide asks you to contact IG to raise it and the FAQ says to manage it by unsubscribing. It previously said IG&apos;s pages name no streaming vendor. labs.ig.com/node/158 was dropped as a second source for two limits, since it showed an out of service notice and the FAQ carries the same figures. Source: IG Labs Streaming API Guide, https://labs.ig.com/streaming-api-guide.html</description>
      <pubDate>Mon, 12 Oct 2026 00:00:00 +0000</pubDate>
      <category>Documentation</category>
      <guid isPermaLink="false">urn:openbrokerapi:change:ig-2026-10-12-91</guid>
    </item>
    <item>
      <title>IG: IG&apos;s affiliate commission page now shows two sterling caps only, up to £1,165 and up to...</title>
      <link>https://openbrokerapi.com/changes</link>
      <description>IG&apos;s affiliate commission page now shows two sterling caps only, up to £1,165 and up to £1,270 per qualified client, and still says IG runs no revenue share. The US$2,045 international figure recorded on 21 Sep 2026 is no longer on the page, and which cap applies to which region is not stated. Read 22 Sep 2026. Partner terms, not an API change. Source: ig.com, affiliate commission, https://www.ig.com/uk/marketing-partnership/affiliate-partnerships/commission</description>
      <pubDate>Tue, 22 Sep 2026 00:00:00 +0000</pubDate>
      <category>Partner terms</category>
      <guid isPermaLink="false">urn:openbrokerapi:change:ig-2026-09-22-1</guid>
    </item>
    <item>
      <title>IG: trading-ig merged a fix on 2 Sep 2026 that replaces the node navigation calls with...</title>
      <link>https://openbrokerapi.com/changes</link>
      <description>trading-ig merged a fix on 2 Sep 2026 that replaces the node navigation calls with fetch_categories and fetch_category_instruments, saying IG appear to have removed the Node ID concept from their public API. This is the community follow up to the /marketnavigation removal reported in February. Community sourced: IG publishes no changelog that records either step. Source: GitHub: trading-ig issue 379 (community, not IG), https://github.com/ig-python/trading-ig/issues/379</description>
      <pubDate>Wed, 02 Sep 2026 00:00:00 +0000</pubDate>
      <category>Ecosystem</category>
      <guid isPermaLink="false">urn:openbrokerapi:change:ig-2026-09-02-1</guid>
    </item>
    <item>
      <title>IG: Community Python wrapper trading-ig 0.0.25 released on PyPI; needs Python 3.10 or later....</title>
      <link>https://openbrokerapi.com/changes</link>
      <description>Community Python wrapper trading-ig 0.0.25 released on PyPI; needs Python 3.10 or later. Not an IG product. Source: PyPI: trading-ig, https://pypi.org/project/trading-ig/</description>
      <pubDate>Tue, 25 Aug 2026 00:00:00 +0000</pubDate>
      <category>Ecosystem</category>
      <guid isPermaLink="false">urn:openbrokerapi:change:ig-2026-08-25-1</guid>
    </item>
    <item>
      <title>IG: A trading-ig user reported historical price downloads failing with the points allowance...</title>
      <link>https://openbrokerapi.com/changes</link>
      <description>A trading-ig user reported historical price downloads failing with the points allowance exceeded and with error.price-history.io-error, a code the user says is not in IG&apos;s API reference. Community sourced and unverified by IG. Decoded on this site at /errors/ig/price-history-io-error. Source: GitHub: trading-ig issue 374 (community, not IG), https://github.com/ig-python/trading-ig/issues/374</description>
      <pubDate>Fri, 19 Jun 2026 00:00:00 +0000</pubDate>
      <category>Ecosystem</category>
      <guid isPermaLink="false">urn:openbrokerapi:change:ig-2026-06-19-1</guid>
    </item>
    <item>
      <title>IG: IG publishes a read-only AI assistant for IG Australia on its own site: an MCP based...</title>
      <link>https://openbrokerapi.com/changes</link>
      <description>IG publishes a read-only AI assistant for IG Australia on its own site: an MCP based assistant in ChatGPT covering prices, positions and order history, with no trading. IG Australia only. Finance Magnates reported it earlier, on 28 May 2026. Source: IG AU: AI assistant, https://www.ig.com/au/trading-platforms/ai-assistant</description>
      <pubDate>Thu, 28 May 2026 00:00:00 +0000</pubDate>
      <category>Ecosystem</category>
      <guid isPermaLink="false">urn:openbrokerapi:change:ig-2026-05-28-1</guid>
    </item>
    <item>
      <title>IG: A trading-ig user reported that IG removed the /marketnavigation endpoint: it no longer...</title>
      <link>https://openbrokerapi.com/changes</link>
      <description>A trading-ig user reported that IG removed the /marketnavigation endpoint: it no longer appears in IG&apos;s docs or the REST API Companion. Reported by the community on 2 Feb 2026, not announced by IG, and no IG changelog records it. Community sourced. Source: GitHub: trading-ig issue 365, Navigation API has changed, https://github.com/ig-python/trading-ig/issues/365</description>
      <pubDate>Mon, 02 Feb 2026 00:00:00 +0000</pubDate>
      <category>Breaking</category>
      <guid isPermaLink="false">urn:openbrokerapi:change:ig-2026-02-02-1</guid>
    </item>
    <item>
      <title>IG: IG is deprecating the streaming MARKET subscription in favour of PRICE. Raised on...</title>
      <link>https://openbrokerapi.com/changes</link>
      <description>IG is deprecating the streaming MARKET subscription in favour of PRICE. Raised on trading-ig on 15 Oct 2025; the library moved its streaming sample to PRICE on 16 Apr 2026. IG publishes a migration guide our reader could not open, so no deadline is confirmed. Community sourced. Source: GitHub: trading-ig issue 356 (community, not IG), https://github.com/ig-python/trading-ig/issues/356</description>
      <pubDate>Wed, 15 Oct 2025 00:00:00 +0000</pubDate>
      <category>Deprecation</category>
      <guid isPermaLink="false">urn:openbrokerapi:change:ig-2025-10-15-1</guid>
    </item>
  </channel>
</rss>
