How to connect to Procountor

Connecting Procountor is short: there are no credentials to enter in Vault. The API credentials belong to the integration you are connecting to, and its provider has already configured them. Your side is making sure your Procountor environment is ready and that the integration has the Procountor API key it needs, then connecting in Vault.

The work is in the prerequisites, not the connection itself.

Prerequisites

An active Procountor environment. The connection targets the Procountor company you already use — a production environment for live data, or the testing environment if your provider is still validating the integration.
A Procountor user with API rights. Rights are granted inside Procountor by a user who can manage users. A user who can sign in to the Procountor UI does not automatically have API rights. This matters because the integration reads your data as a specific Procountor user, not as "your company" in general — see the next point.
An API client key, if your provider asks for one. Many Procountor integrations are activated by the customer generating an integration-specific key: sign in to the Procountor UI, open the Basics menu at the top right, go to the API client keys page, paste the client ID your provider gives you, and click create. Procountor shows the key once and lets you copy it — hand it back to your provider through a secure channel. Procountor describes these keys as "credentials bound to a specific user, company and client application", so the user you are signed in as when you create the key, and that user's company, are what the integration will act as from then on. Only do this if your provider asks; see Procountor's M2M authentication documentation for the full description.

You do not need a developer account of your own.

Steps

Open Vault and select Procountor.
Click Connect. There are no credential fields to fill in and no Procountor sign-in step — Vault does not ask you for a Procountor username, password or company, because the integration's credentials are configured by its provider.
Wait for the connection to show as connected before using it. If it does not, work through Troubleshooting below.

Because Vault never asks which Procountor user or company to use, that choice is not made here. It was made when the API client key in prerequisite 3 was created, and it is changed by replacing that key — not by connecting again.

Notes

Testing and production are separate. Procountor's Public Testing Server and production are different environments with different credentials, and Procountor states that "the production user accounts are not available on the testing server or vice versa". So a key you created while your provider was validating on the testing server cannot be reused in production: expect your provider to ask you to create a new API client key in your production environment when the integration goes live.
Some Procountor features are inactive in the testing environment. Procountor's General information page states that the testing environment does not execute actual financial transactions or receive statements from banks, does not send out any mail, and does not allow password changes or resets without logging in to the Procountor UI. If you are connecting a test environment, do not read those as connection failures.
You can cut access off at any time, from either side. Disconnecting in Vault stops the integration's access through Apideck. On the Procountor side, an API client key can be revoked in the Procountor UI on the same Basics → API client keys page you created it on, which invalidates it for the provider as well.
The rights of the user behind the API key define what the integration sees. The integration never has more access than the Procountor user whose API client key was created for it, so restricting that user restricts the integration.

Troubleshooting

The connection does not come up as connected, or turns invalid. Nothing you enter in Vault can cause this, so it is almost always one of two things on the other side: the Procountor user behind the API client key does not have API rights, or the access token your provider configured has expired — Procountor access tokens last one hour, and they are the provider's to renew. Ask whoever administers your Procountor environment to grant API rights to that user, and tell your provider the connection is failing so they can check their token.

The integration reports the wrong company. The company is fixed by the API client key, because Procountor binds each key to one user and one company. Check which Procountor company the user who created the key belongs to. If it is not the company the integration should be reading, the fix is a new key, not a new connection: revoke the old key on Basics → API client keys, create a replacement while signed in as a user in the correct company, and hand that key to your provider.

Everything connects, but some records are missing. Check the Procountor rights of the user whose API client key the integration uses — accounting data that user cannot see in the Procountor UI is not returned through the API either. Widening that user's rights widens what the integration sees; you do not need to reconnect in Vault for that to take effect.

The integration worked and then stopped. Confirm the Procountor user whose API client key the integration uses is still active and still holds API rights — a disabled or downgraded user breaks the integration's access. Restoring that user's API rights is the fix; if the user has been removed outright, revoke the old key and create a replacement key while signed in as an active user with API rights, then hand it to your provider. If that user is fine, the problem is on the provider's side rather than yours — their configured token expires hourly and has to be renewed by them.

You were asked for a client ID or an API key. That request comes from your integration provider, not from Vault — see the third prerequisite above. Vault itself never asks you for Procountor credentials.

If none of the above applies, contact your integration provider first; for anything on the Apideck side of the connection, contact Apideck Support.

Reference

Procountor developer documentation — the vendor's API documentation hub
M2M authentication — creating and revoking an integration-specific API client key in the Procountor UI
General information — how the testing environment differs from production