SAM.gov API Rate Limits Explained

Complete breakdown of SAM.gov's API rate limits by access tier, including how to get higher limits and alternatives for high-volume use cases.

Quick summary: Public access: 10 requests/day. Entity registration: 1,000/day. Federal system users: 10,000/day.

Need More Than Just Opportunities?

Get verified contact information for contracting officers and program managers to accelerate your outreach. Try GovCon Contacts →

Rate Limits by Access Tier

What We've Observed

We work with the SAM.gov API daily. Here's what we've found about how the rate limits actually behave.

The quota is per key, not per IP

SAM.gov tracks usage by API key. If you use the same key from different servers or locations, the requests count against the same daily quota. There is no IP-based blocking or geo-restriction. The API is accessible globally.

The daily limit resets at midnight UTC

When you hit the limit, SAM.gov returns a 429 response with a Retry-After header pointing to midnight UTC. Example response:

{"code":"900804","message":"Message throttled out","description":"You have exceeded your quota. You can access API after [tomorrow] 00:00:00+0000 UTC"}

There's no partial reset or sliding window during the day. Once you're out, you wait until midnight.

10 requests goes fast

On the basic tier, 10 requests per day means 10 API calls total. Each call returns up to 1,000 records per page, so you can get a decent amount of data if you plan your queries. But if you need to run different searches (by NAICS, by agency, by state), you run out of requests quickly.

Entity registration takes 2-3 weeks

To get the 1,000/day tier, you need:

UEI Number - usually same day
SAM.gov Entity Registration - up to 10 business days
API Role Approval - a few more days after entity is active

Total: about 2-3 weeks. Free, but requires annual renewal.

What 10 Requests/Day Actually Looks Like

Here are some real scenarios:

You can do this

Search IT contracts (NAICS 541512) in California: 1 request, up to 1,000 results
Pull all awards from the last 2 days: 1 request
Check a specific solicitation number: 1 request
Get all presolicitations in Virginia: 1 request

That's 4 requests. You have 6 left for the day.

You can't do this

Search 15 different NAICS codes daily (15 requests needed)
Monitor multiple agencies with different filters
Run a search and then paginate through all results (pagination burns requests)
Build an alert system that checks for new opportunities multiple times per day

What the API Doesn't Return

Rate limits aside, there are things the SAM.gov API simply doesn't include in its responses:

Full descriptions: The API returns a URL to the description, not the description text itself. Getting the actual requirements means a separate step for each opportunity.
Historical completeness: The API surfaces recently posted or modified opportunities. Long-running vehicles (IDIQs, BOAs) posted years ago don't appear in results even if they're still accepting proposals.
Exclusions in the same call: Exclusions (debarred entities) are on a completely different API endpoint with a different schema.

These aren't rate limit issues, but they affect how many requests you actually need to get the data you want.

When SAM.gov Direct Access Makes Sense

Government agencies with .gov/.mil emails get 10,000/day. That's plenty for most internal tools.
Occasional lookups where you search for a specific solicitation or check a few opportunities per day.
Prototyping where you need to validate an idea before investing in infrastructure.
Academic research with a narrow, well-defined query scope.

When it doesn't work

Daily monitoring: If you need to check multiple NAICS codes, agencies, or states every day, 10 requests won't cover it.
Production applications: Any product that depends on fresh contract data needs more reliable throughput than 10/day.
Full descriptions: If your use case requires the actual solicitation text, you need additional infrastructure beyond the API.
Compliance screening: The exclusions API is separate, so checking debarment status requires its own request budget.

Alternatives

If SAM.gov's rate limits don't work for your use case, you have a few options:

Register for entity access (free, 2-3 weeks): Gets you 1,000/day. Good if you can wait and your volume stays under that.
Use a third-party API: Services like GovCon API provide higher limits (1,000/hour), instant access, and additional data like full descriptions and exclusions. Typically $19/month.
Enterprise platforms: several commercial tools offer web-based dashboards with unlimited access but typically start at thousands per year and don't provide API access for custom integrations.