5 minute readRate limits restrict the number of API Transactions Per Second (TPS) an entity can make per API. DPS applies TPS rate limits to maintain stability and performance, and to ensure all users receive consistent and reliable service.
Rate limits are subject to change based on performance optimization, or specific arrangements with the DPS support team.
If you need a higher rate limit, contact the DPS support team to discuss specific requirements. DPS will evaluate the request based on factors such as usage history, business needs, and other performance measures.
Tier 0 – (50 TPS), APIs with standard spike rates.
Tier 1– (150 TPS), APIs with a mid-level spike rates.
Tier 2– (500 TPS), APIs with high spike rates.
| TPS Tier | API Name | TPS Setting |
| Tier 0 | Card Services Legacy DotNet API | 50 |
| Tier 0 | Card Transactions | 50 |
| Tier 0 | Cardholder Verification | 50 |
| Tier 0 | Card PIN Management | 50 |
| Tier 0 | Transaction Services | 50 |
| Tier 1 | Card Inquiry | 150 |
| Tier 0 | Token Services | 50 |
| Tier 1 | Card CVV2 | 150 |
| Tier 1 | Balance Services | 150 |
| Outbound | AP Maintenance Sync | N/A |
| Tier 0 | Program Services | 50 |
| Tier 0 | One Time Password | 50 |
| Outbound | Token Provisioning Yellow Path Outbound | N/A |
| Tier 0 | Account Details | 50 |
| Tier 0 | Card Activation | 50 |
| Tier 1 | Card Services | 150 |
Settings are monitored and applied separately for each API project and ID. They are not applied collectively across IDs.
Start a Project
API Overview
API Reference