Background

NGP VAN builds and maintains CRM platforms that power campaigns and organizations of all sizes, and in collaboration with large, distributed clients and integration partners. (Outside of the political market, NGP VAN products are branded as EveryAction.) While NGP VAN does not own any voter or client data, we play a key role in helping campaigns and vendors integrate securely, efficiently, and at scale.

As a developer, it’s important to understand how these platforms are structured and how your integration interacts with them. The voter data in VAN may be managed differently than person level data you’ve worked with, so don’t hesitate to reach out to [email protected] with any questions.

The client platforms and NGP VAN API support team are shared resources across a broad ecosystem of campaigns and partners. During high volume periods like Get Out The Vote (GOTV), database usage and support tickets increase exponentially. Our goal is to ensure that every integration can sync data quickly and reliably, but it’s equally important for developers to use these shared resources responsibly to keep data flowing smoothly across the ecosystem.

As of November 2025, we have launched updates to API access – including clearer policies, refined rate management, and a dedicated partnership program – to help integrations perform smoothly and scale with growing demand throughout the cycle.

Rate Limit Requirements

Our APIs are tuned for expected usage patterns, with some endpoints optimized for high-frequency operations and others designed for bulk or asynchronous data processing. Rate limits vary depending on the type of integration and partnership tier.

We maintain two rate categories:

• Vendors who participate in our API Partnership Program.
• Custom integrations built by clients for their own use.

These tiers ensure stability across our shared infrastructure while giving high-volume partners room to scale.

Vendor: API Partnership Program

To explore upgraded limits or partnership benefits, reach out to [email protected].

Clients: Custom Integrations

To explore upgraded limits or partnership benefits, reach out to [email protected].

Endpoint Rate Categories

Each API endpoint is assigned a rate category — High, Medium, or Low — based on its typical data volume and processing cost. These categories determine how many requests per second (rps) are allowed under your integration tier.

High-throughput endpoints

Designed for rapid, transaction update such as canvassing data.

• POST /people/{vanId}/canvassResponses
• POST /people/{personIdType}:{personId}/canvassResponses

Low- throughput endpoints

Used for matching or bulk imports that require heavier processing or background jobs

• POST /people/find
• POST /people/findOrCreate
• POST /bulkImportJobs
• GET /bulkImportJobs/{jobId}
• GET /bulkImportJobs/resources
• GET /bulkImportMappingTypes
• GET /bulkImportMappingTypes/{mappingTypeName}
• GET /bulkImportMappingTypes/{mappingTypeName}/{fieldName}/values

Medium-throughput endpoints:

All other endpoints not listed above.

Implementation Best Practices

Error Handling & Replay Logic

• Design for retries: Your application should be able to replay API calls automatically when transient errors or rate limits occur.
• Fallback options: If automated retries aren’t possible, provide a contingency workflow (for example, a CSV upload through the VAN user interface).
• This ensures that data integrity is maintained even during high-volume periods like GOTV.

Data Integrity for Phone and SMS Apps

• When syncing disposition data (e.g., wrong number, disconnected, opt-in status), use the phoneId field to ensure updates are correctly associated.
• Example:

{
  "canvassContext": {
    ...
    "phoneId": 867
  }

More information is available in the API documentation section here.

Performance Optimization

• Run test or “dry run” syncs with NGP VAN prior to high-volume events such as GOTV or EOQ.
• Contact [email protected] for recommendations on optimizing request patterns or batching operations.

Data Corrections & Support

• If data is synced incorrectly and requires backend remediation, the client must contact NGP VAN support directly.
• Vendors cannot request database rollbacks or edits on behalf of clients.
• Include specific examples and record IDs when submitting support requests to speed resolution.

Collaboration & Communication

• Reach out proactively if you anticipate unusual traffic or integration behavior that could affect shared system performance.
• The API support team can assist with scaling strategies, error analysis, and rate management.

Previous Throttling Guidelines