The Polymarket US developer portal is the place where developers on the US platform find documentation and request access. It is separate from the international trading API, so a developer who uses one should not assume the other works in the same way. This guide explains what to check before you start.

Why the US platform has a separate API

The polymarket us developer portal and the international API serve different systems. The international platform and the US platform run different systems. For background, read the prediction markets guide. The Polymarket Institute page on exchange data notes that the US platform has its own documentation and its own API. The same page points developers to the docs for the platform they actually trade on, so start there.

The help center article on the API explains that public market data and trading access are two different things. Read the article before you assume a key from one platform works on the other.

Check your account before using the Polymarket US developer portal

Access on the US platform depends on your account status. Some developer tools ask you to verify your identity in the US app before you can create keys. Plan for that step, because it can take longer than writing the first request.

Keep the key secret

Keep the key secret when you receive it. Store it in a secure place on your server and never place it in front-end code or a shared document. If you lose it, request a new one and stop using the old one.

What to check in the documentation

  • The base address for US requests, which differs from the international API.
  • The authentication method for each endpoint. Read the parts that cover orders and account data separately.
  • The rules for rate limits, which can change over time.
  • Whether a feature you need is available for your account type in your country.

Use the US API with care

Before you write code against the polymarket us api, test a read-only call. The help article on the API is a good place to start. If your plan includes automated trading, review the bot risks first, and check the app versions guide to confirm which platform matches your account.

Common mistakes

  • Using international credentials on the US platform, or the reverse.
  • Writing code before reading the authentication section.
  • Treating third-party tutorials as official. Use them only as a starting point and check each claim against the official docs.

Key takeaways

  • The US developer portal serves the US platform, which has its own API.
  • Check which platform your account uses before you request keys.
  • Store keys securely and confirm details in the official documentation.

API access, identity checks and platform rules change. Check the official documentation before you build.