To ensure a smooth start with our APIs, your business should meet the following conditions:
- High degree of automation.
- Professional IT environment and good infrastructure.
- Permanently available security expertise to use our APIs and safeguarding the security.
Connecting with our APIs
To connect with our APIs, you need the following:
PSD2
An eIDAS QWAC certificate issued by the Qualified Trust Service Provider of your choice.
Business
- An EV SSL certificate for transport.
- An EV SSL signing certificate for signing messages.
- An active Rabobank account.
Rabobank accepts:
- EV SSL certificates from the certificate issuers listed in the Mozilla CA Certificate report.
- X.509 format.
- RSA: key length should be at least 2048-bit.
- Certificate should be valid for a maximum of one year.
You are responsible for the application, certificate purchases, and other costs involved.
You can open a Rabobank account through our website.
Implementing
For some APIs, Rabobank actively assists customers throughout the implementation process.
Rabobank offers you a Sandbox account for end-to-end testing to ensure everything runs smoothly before going live. The Sandbox environment uses static responses, meaning it returns predefined results rather than processing real transactions. The example values in our documentation are aligned with these responses—so copying and pasting them into your requests lead to successful responses. The Sandbox URL is included directly in the API endpoint definitions for easy access.
After signing the contract, you get access to the production API where you can connect the API to your application.
Get in touch
Contact us to connect with the API.
Kick off
All set to use our APIs? Here are some tips:
- Make sure you have a working sandbox account in the Rabobank developer portal. Read Get Started to set up an account and register an Application.
- To use Rabobank API(s), a valid TLS certificate is required.
- After your account set up is complete, subscribe the API product and the Oauth 2.0 Services or Authorization Services to your application. Make sure to use the Authorization and Token URL as provided by the Oauth 2.0 Services or Authorization Services.