Procurify · Rate Limits
Procurify Rate Limits
Procurify does not publicly disclose specific numerical rate limits in its developer documentation. The documentation notes that requests which are too large or take too long may result in timeouts, and that repeated offenses can lead to suspension of API access. Customers should contact support if they experience timeout issues. Tokens issued via the OAuth 2.0 client credentials flow expire after 24 hours and must be refreshed.
Procurify Rate Limits is the machine-readable rate-limit profile for Procurify on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 3 rate-limit definitions.
Tagged areas include Spend Management, Procurement, Purchase Orders, Accounts Payable, and Vendor Management.
3 Limits
Spend ManagementProcurementPurchase OrdersAccounts PayableVendor ManagementBudget TrackingProcure-to-PayERP Integration
Limits
Token Expiry token
1
Tokens are scoped to domain and email. A new client credentials request is required for each 24-hour period or whenever the token expires.
Request Size and Timeout request
unspecified
No specific byte or row limit is published. Developers should paginate large data sets and avoid bulk requests that may exceed server limits.
General Rate Limiting api
unspecified
Contact support@procurify.com to understand applicable limits for your integration use case.