Overview

The Pacejet API uses automatic governance controls to manage how integrations consume resources, returning appropriate messages, and transaction control details to help applications maximize the use of available resources. Each Pacejet user location receives a default set of "governance units" appropriate to a subscription and API access licenses; generally each API endpoint governance includes a number of permitted calls within a defined unit of time. Individual governance allocations can be expanded for any specific customer location by contacting the support or customer success team.

Managing Request Limits for Maximum Throughput

It is a best practice for maximizing integration throughput, applications should dynamically react to governance limits, tailoring integration activities to align with messages received from Pacejet. For example, when an application receives a 429 "Too Many Requests" response code from Pacejet, the integration can use the "Requests-Remaining" count and "Requests-Reset" date-time values in response headers to dynamically determine when to continue integration processing. By dynamically responding to these values, applications can automatically increase throughput when governance limits are expanded (e..g through request to support or customer success).

Applications should dynamically respond to 429 "Too Many Request" response codes,
using the "Requests-Remaining" count and "Requests-Reset" date-time values to decide
when to resume integration processing transactions.

Diagnosing New Integrations and Monitoring Governance Usage

The Pacejet API log provides visibility of API requests and responses, outside of application-specific integration coding, providing easier diagnostics for new integrations and better long-term monitoring. From a governance perspective, standard 429 "Too Many Requests" response codes will show in the API Log to help integrators and support teams see when system growth may have exceeded a current level of assigned governance.

The Pacejet API provides visibility of governance 429 "Too Many Request" response codes,
allowing new integrations to be more easily diagnosed and simplifying long-term management.

Standard Governance Settings for Pacejet Locations

The following chart summarizes the current standard governance limits issued with new Pacejet locations. This information may change over time and expands as new API endpoints are added to Pacejet. Please contact support or your customer success manager to get a copy of the latest governance limits set for your location.