Magistry has withdrawn gift-card issuance tools from third-party applications connecting through OAuth, according to a September 30 entry in its official shipping log.

The tools remain available through merchants' own API keys. The same restriction covers tools that create refunds or cancel orders, the company says.

The access restriction within the published operation registry

Magistry groups its API into reads, automatic writes and proposed writes. Its developer page publishes 105, 44 and 34 operations in those groups respectively, counted on October 19. These categories explain why an integration needs to distinguish access to information from permission to execute or propose a change; they do not establish that every listed operation is available to every external application. [S02] [S03]

operations

Source

Magistry developer platform, counted October 19, 2026

Vendor-published inventory counts, not counts constructed from release-note bullets. They cover the whole registry and do not show how many tools a third-party credential can reach, how many issue gift cards, or whether the September change reduced incidents.

Show data tableHide data table

Scroll left or right to see all columns

Magistry publishes a registry breakdown by operation tier (operations)
Category	Published registry operations
Read	105 operations
Automatic write	44 operations
Proposed write	34 operations

The September 30 announcement described a restriction on the route through which an external application could trigger a financial action

Magistry has withdrawn gift-card issuance tools from third-party applications connecting through OAuth, according to a September 30 entry in its official shipping log. The tools remain available through merchants' own API keys. The same restriction covers tools that create refunds or cancel orders, the company says. The access restriction within the published operation registry Magistry groups its API into reads, automatic writes and proposed writes. Its developer page publishes 105, 44 and 34 operations in those groups respectively, counted on October 19. These categories explain why an integration needs to distinguish access to information from permission to execute or propose a change; they do not establish that every listed operation is available to every external application. [S02] [S03] Magistry publishes a registry breakdown by operation tier The developer page explicitly reports these counts for October 19, 2026, across its whole MCP and REST registry. Published registry operations Read: 105 operations Automatic write: 44 operations Proposed write: 34 operations Vendor-published inventory counts, not counts constructed from release-note bullets. They cover the whole registry and do not show how many tools a third-party credential can reach, how many issue gift cards, or whether the September change reduced incidents. Magistry developer platform, counted October 19, 2026 The September 30 announcement described a restriction on the route through which an external application could trigger a financial action

Your free reader account