Procountor

At a Glance

Difficulty

⚡MODERATEVendor-Issued Credentials — API access is requested from Procountor rather than created in a self-service developer portal.

Authentication

OAuth 2.0Bearer token — not OAuth. Procountor issues an API token that you configure in Apideck; there is no consent-screen redirect flow.

Webhooks

No webhooks — change detection is polling-based.

Partnership Required

No(Credentials are requested via Procountor's integrations form; certification applies only to the optional Partner Programme.)

Partnership Application

Developer Portal↗

Apideck Credentials

Not available

Costs

Procountor publishes no API usage fees; the cost is the consumer's own Procountor subscription. A free product trial is available.

Sandbox Availability

Available(Procountor runs a separate Public Testing Server with its own base URL and its own credentials.)

Account Type Required

Active Procountor environment

Consumer Access Level

A Procountor user with API rights to authorize the connection

Rate Limits

Documented by Procountor: 60 requests/second per client on the production server; 90 requests/minute per client on the testing server.

Responsibility matrix

Environments

Testing

Request a private testing environment through Procountor's form at https://dev.procountor.com/contact/request-testing-environment/. You receive credentials for the Public Testing Server, which runs the same platform as production but cannot enact real financial transactions. The connector is configured against https://api-test.procountor.com, while Procountor's own documentation lists the testing base URL as https://pts-api.procountor.com — use whichever address Procountor issues you with your testing credentials.

Production

Live customer data at https://api.procountor.com. Credentials are environment-specific, so moving from testing to production means changing both the server address and the credentials — testing credentials CANNOT be used against production accounts.