polymarket-api

Retrieve and normalize Polymarket profile, activity, event, and market data.

Updated Feb 21, 2026
One-click install
npx skills add https://github.com/aquarius-wing/polymarket-dev-tools --skill polymarket-api
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: polymarket-api
Source: https://github.com/aquarius-wing/polymarket-dev-tools/tree/main/.cursor/skills/polymarket-api
Command: npx skills add https://github.com/aquarius-wing/polymarket-dev-tools --skill polymarket-api

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides clear integration guidance and mapping rules to retrieve, normalize, and ingest Polymarket profile, activity, event, and market data while avoiding common pitfalls like timestamp mismatches, signature errors, and JSON-in-string fields.

Core Features & Use Cases

  • Endpoint Reference: Consolidated URLs and documentation pointers for profiles, activities, events, and CLOB endpoints.
  • Data Normalization: Guidance on handling second-level Unix timestamps, casing normalization for enums, numeric conversions, and fallback handling for missing relations.
  • CLOB Authentication: Step-by-step HMAC construction with URL-safe Base64 and required headers for L2 authenticated requests.
  • Use Case: Build a backend sync that fetches activities and events, normalizes timestamps and prices, verifies CLOB credentials, parses nested JSON-string fields, and writes canonical records to a database.

Quick Start

Use the polymarket-api skill to fetch public profiles and activities for a list of wallet addresses, normalize timestamps and sides, and parse nested market JSON fields for database ingestion.

Frequently Asked Questions about polymarket-api

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I authenticate Polymarket CLOB API requests using HMAC?

Authenticate Polymarket CLOB API requests by constructing an HMAC signature using URL-safe Base64 and passing the required headers. The process involves step-by-step HMAC construction to satisfy L2 authenticated request requirements for secure endpoint access.

How do I normalize Polymarket API timestamps for database ingestion?

Normalize Polymarket API timestamps for database ingestion by converting second-level Unix timestamps, applying casing normalization for enums, and handling fallbacks for missing relations. This ensures canonical records are written correctly during backend synchronization.

What is the best way to parse nested JSON-string fields in Polymarket market data?

Parsing nested JSON-string fields in Polymarket market data requires explicit JSON-string parsing of nested fields within event and market records. This handles complex nested structures retrieved from Polymarket APIs for analytics pipelines and marketplace tooling.

Can I use Polymarket API data for backend synchronization and analytics pipelines?

Yes, you can use Polymarket API data for backend synchronization and analytics pipelines by fetching public profiles, activity lists, event details, and nested market records. The integration retrieves and normalizes this data specifically for database ingestion workflows.

Why does my Polymarket API integration fail with timestamp mismatches and signature errors?

Polymarket API integration failures with timestamp mismatches and signature errors often stem from incorrect second-level Unix timestamp handling or HMAC construction issues. Proper field normalization and URL-safe Base64 signature generation are required to avoid these common pitfalls.