How do I install the API Governance And Rate Limits skill?

Run npx skillmds add pranavnagrecha/api-governance-and-rate-limits in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is API Governance And Rate Limits safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: executes scripts, makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with API Governance And Rate Limits?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is API Governance And Rate Limits free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published API Governance And Rate Limits?

PranavNagrecha (@pranavnagrecha) published this skill. Their other Agent Skills are listed on their SkillMD profile.

API Governance And Rate Limits by pranavnagrecha

Name: API Governance And Rate Limits
Rating: 4.2 (5 reviews)
Author: PranavNagrecha

API Governance And Rate Limits

Monitor and govern Salesforce API consumption: per-user limits, org allocation, lightning-rest limits, and backoff. NOT for designing new endpoints — use security/api-security-and-rate-limiting.

PranavNagrecha fc8d730 7 files · 19.9 KB Updated Sep 8, 2026 15 repo stars

File contents

API Governance and Rate Limits

Salesforce orgs have a 24-hour API allocation (varies by license). Hitting it halts all integrations. This skill builds a governance dashboard (API usage by consumer), a throttling pattern for heavy consumers, and an escalation runbook when usage trends toward limits.

Adoption Signals

Orgs with 10+ integrations or periodic '24-hour limit exceeded' incidents.

Required when a single integration consumes more than 30% of the daily API allocation.
Required before contracting a new integration partner — establishes per-consumer quotas and the alerting baseline.

Recommended Workflow

Pull /services/data/v60.0/limits/ daily; record DailyApiRequests.Max and Remaining.
Attribute usage via EventLogFile ApiTotalUsage events — per user/consumer-key.
Identify top 3 consumers; review whether Bulk API 2.0 or Composite API could replace per-row calls.
Implement throttling on heaviest consumer (token bucket in the middleware layer, not in Salesforce).
Set 70% / 85% alerts; escalate at 85%.

Key Considerations

Bulk API 2.0 jobs are not counted in the REST 24h allocation (separate bucket).
Composite API collapses N calls to 1 from the allocation standpoint.
Platform Events and Pub/Sub have separate limits.
LWC @wire calls count toward user limits — be careful with auto-refresh.

Worked Examples (see `references/examples.md`)

Throttle heavy ETL — ETL hit 95% at 3am
Composite for UI — LWC needed 5 parallel fetches

Common Gotchas (see `references/gotchas.md`)

Auto-refresh LWC — Open dashboard burns 1000 calls/hour per user.
Retry storms on 429 — Doubles consumption.
Anonymous allocation — Can't tell who is burning it.

Top LLM Anti-Patterns (full list in `references/llm-anti-patterns.md`)

Shared integration user across consumers
No allocation dashboard
Retry without backoff

Official Sources Used

Apex REST & Callouts — https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_callouts.htm
Named Credentials — https://help.salesforce.com/s/articleView?id=sf.named_credentials_about.htm
Connect REST API — https://developer.salesforce.com/docs/atlas.en-us.chatterapi.meta/chatterapi/
Private Connect — https://help.salesforce.com/s/articleView?id=sf.private_connect_overview.htm
Bulk API 2.0 — https://developer.salesforce.com/docs/atlas.en-us.api_asynch.meta/api_asynch/
Pub/Sub API — https://developer.salesforce.com/docs/platform/pub-sub-api/guide/intro.html

---name: api-governance-and-rate-limitsdescription: Monitor and govern Salesforce API consumption: per-user limits, org allocation, lightning-rest limits, and backoff. NOT for designing new endpoints — use security/api-security-and-rate-limiting.---# API Governance and Rate LimitsSalesforce orgs have a 24-hour API allocation (varies by license). Hitting it halts all integrations. This skill builds a governance dashboard (API usage by consumer), a throttling pattern for heavy consumers, and an escalation runbook when usage trends toward limits.## Adoption SignalsOrgs with 10+ integrations or periodic '24-hour limit exceeded' incidents.- Required when a single integration consumes more than 30% of the daily API allocation.- Required before contracting a new integration partner — establishes per-consumer quotas and the alerting baseline.## Recommended Workflow1. Pull `/services/data/v60.0/limits/` daily; record `DailyApiRequests.Max` and `Remaining`.2. Attribute usage via EventLogFile `ApiTotalUsage` events — per user/consumer-key.3. Identify top 3 consumers; review whether Bulk API 2.0 or Composite API could replace per-row calls.4. Implement throttling on heaviest consumer (token bucket in the middleware layer, not in Salesforce).5. Set 70% / 85% alerts; escalate at 85%.## Key Considerations- Bulk API 2.0 jobs are not counted in the REST 24h allocation (separate bucket).- Composite API collapses N calls to 1 from the allocation standpoint.- Platform Events and Pub/Sub have separate limits.- LWC `@wire` calls count toward user limits — be careful with auto-refresh.## Worked Examples (see `references/examples.md`)- *Throttle heavy ETL* — ETL hit 95% at 3am- *Composite for UI* — LWC needed 5 parallel fetches## Common Gotchas (see `references/gotchas.md`)- **Auto-refresh LWC** — Open dashboard burns 1000 calls/hour per user.- **Retry storms on 429** — Doubles consumption.- **Anonymous allocation** — Can't tell who is burning it.## Top LLM Anti-Patterns (full list in `references/llm-anti-patterns.md`)- Shared integration user across consumers- No allocation dashboard- Retry without backoff## Official Sources Used- Apex REST & Callouts — https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_callouts.htm- Named Credentials — https://help.salesforce.com/s/articleView?id=sf.named_credentials_about.htm- Connect REST API — https://developer.salesforce.com/docs/atlas.en-us.chatterapi.meta/chatterapi/- Private Connect — https://help.salesforce.com/s/articleView?id=sf.private_connect_overview.htm- Bulk API 2.0 — https://developer.salesforce.com/docs/atlas.en-us.api_asynch.meta/api_asynch/- Pub/Sub API — https://developer.salesforce.com/docs/platform/pub-sub-api/guide/intro.html

Frequently asked questions