---
url: "https://predictiontoolkit.com/news/struct-polymarket-sunset/"
publisher: "PredictionToolkit"
dateModified: "2026-11-02"
---

[← Polymarket news](<https://predictiontoolkit.com/news/>) 

# Struct announced a 2026-09-30 cutoff for Polymarket services

By PredictionToolkit · Updated 2026-11-02

## Reported event

**Event type:** service change · **Event date:** 2026-09-17

On 2026-09-17, Struct announced permanent shutdown of all its Polymarket APIs and Explorer on 2026-09-30 at 23:59 UTC and asked customers to migrate data and integrations. The announced deadline is now past.

## What the notice said

The statement set a migration deadline for customers. It should be read as a dated provider announcement, not a new service-change alert or an independent observation of endpoint shutdown.

## Who should inspect dependencies

Operators using Struct endpoints, webhooks or Explorer data should review the notice and their application dependencies. The directory has no customer accounts, logs, credentials or connected Struct integration. Its 2026-09-07 feature and $49 pricing notes are historical and were removed as current catalog facts.

## Other APIs have different tasks

The official Polymarket overview separates Data API positions/activity from CLOB books and signed order operations. Their existence does not establish Struct-compatible schemas, history, entitlements, costs or automatic migration. Read each destination’s documentation and expected fields; do not copy private credentials between providers.

## Migration review

-   List the Struct endpoints and dependencies your application uses.
-   Export data you need where it remains available.
-   Validate identifiers, response fields and historical coverage with the replacement.
-   Complete client checks before relying on a new integration.

## What remains unobserved

The notice still records the announced schedule. This directory has not independently observed the shutdown of endpoints or billing outcomes. Check the provider’s service status and your own integration rather than inferring them from the past deadline.

## Continue researching

-   [Struct: Retired Polymarket API and Migration](<https://predictiontoolkit.com/tools/struct/>)  · context: Read the historical profile.
-   [Polymarket Data API: turn public activity into wallet analytics](<https://predictiontoolkit.com/tools/polymarket-data-api/>)  · context: Review the distinct positions/activity surface.
-   [Polymarket CLOB API: read books and implement order handling](<https://predictiontoolkit.com/tools/polymarket-clob-api/>)  · context: Review books and private-order requirements.
-   [Struct alternatives for Polymarket data](<https://predictiontoolkit.com/tools/struct/alternatives/>)  · context: Compare task-specific alternatives.