Skip to main content
Builder API keys authenticate your application with Polymarket’s relayer and enable order attribution. You’ll need these credentials to access gasless transactions and track volume.

Accessing Your Builder Profile

2

From Menu

Click your profile image → Select “Builders”

Creating API Keys

In the Builder Keys section of your profile:
  1. Click ”+ Create New” to generate a new API key
  2. Copy all three values immediately — the secret and passphrase are only shown once
  3. Store them securely in your secrets manager or environment variables
Each API key includes three components:
ComponentDescriptionExample
keyPublic identifier for your builder accountabc123-def456-...
secretSecret key for signing requestsbase64-encoded-secret
passphraseAdditional authentication valueyour-passphrase
The secret and passphrase are only displayed once when created. If you lose them, you’ll need to generate a new key.

Managing Keys

Create separate keys for different environments:
EnvironmentPurpose
DevelopmentTesting and local development
StagingPre-production testing
ProductionLive trading

Profile Settings

Your builder profile includes customizable settings:
SettingDescription
Profile PictureDisplayed on the Builder Leaderboard
Builder NamePublic name shown on the leaderboard
Builder AddressYour unique builder identifier (read-only)
Current TierYour rate limit tier: Unverified, Verified, or Partner

Environment Variables

Store your credentials as environment variables:
.env
POLY_BUILDER_API_KEY=your-api-key
POLY_BUILDER_SECRET=your-secret
POLY_BUILDER_PASSPHRASE=your-passphrase

Security Best Practices

PracticeDescription
Never commit credentialsUse .gitignore to exclude .env files
Use environment variablesLoad credentials from env vars, not hardcoded strings
Use a secrets managerAWS Secrets Manager, HashiCorp Vault, etc. for production
Separate environmentsUse different keys for dev, staging, and production
Monitor usageCheck the leaderboard for unexpected volume changes
Never expose Builder API credentials in client-side code. Your secret and passphrase must stay on your server.

Troubleshooting

Cause: You’ve exceeded your tier’s daily transaction limit.Solution:
Cause: The secret and passphrase are only shown once when created.Solution: Create a new API key. You cannot recover the original values.

Next Steps