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.