DAM Integrations Explained: The Four Connections Beeldbank.nl Offers (Canva, API, OAuth, SSO)

Integration terms can sound like jargon when you are choosing an image bank. Canva link, API, OAuth, SSO: each one answers a practical question about daily work. Can designers reach the images from the tool they already use? Can another system fetch images? How do people log in? The image bank documents four of these connections, and this guide explains what each term means and when to use it.

What an Integration Means for Daily Work

An integration is a connection between the image bank and another tool, so that work does not stop at the edge of one system. Without an integration, a person downloads a file, finds it in a folder and uploads it somewhere else. With one, the second tool can reach the images directly. Beeldbank.nl documents four working connections.

As a buyer you do not need to understand the technology. You need to be able to say, for each integration, which task in your organisation it affects and who will use it. For each connection, identify the team member who will use it daily. When you can point to that person, you know what Beeldbank.nl offers and how it fits your workflow.

Canva: Designers Reach Images from Inside Designs

A Canva connection exists so that designers can use images directly in designs. When linked, the practical effect is that a designer reaches the organisation's images from inside the design tool, instead of leaving the tool to look in a folder.

The Canva link shows up in the Canva sidebar where designers work. A designer on your team can test it before you decide, because designers will notice if it is awkward or slow. For a step-by-step look at how the connection works, read Mediabank with a Canva Link.

API: A Door for Custom Connections

An API is a door that lets software talk to software. An API connects the image bank to other systems, so that images are available there too. It is the way to connect to the systems your organisation already uses.

An API is not a finished connection. A developer inside your organisation or one you hire has to build and maintain the custom connection. The useful questions are practical: Is there written documentation available? Which actions does the API allow, and which are not possible? Who looks after the connection when either system changes?

If nobody in your organisation will build anything themselves, an API is not a feature you will use directly. It matters if a developer, supplier or agency will do the work on your behalf. Beeldbank.nl documents an API so that developers can build connections to WordPress, InDesign, TYPO3 and other platforms.

SSO and Azure: One Account for Staff

Single Sign-On, or SSO, lets staff log in with one account instead of keeping a separate password for the image bank. Beeldbank.nl offers optional SSO as a one-time connection for organisations that want this convenience. You choose whether to add it.

For organisations that work with Azure or Entra ID, the image bank connects to the organisation's own login. The connection is arranged for a one-time fee of 990 euros. This eliminates separate passwords and simplifies access management.

When you compare vendors, ask the same two questions about login: is SSO included or priced separately, and is the price once or recurring? Put the answers in one sheet so you can compare clearly.

OAuth: Account Verification That Runs Behind the Scenes

OAuth is a widely used protocol for letting one system verify who you are on behalf of another. The protocol handles verification securely without creating a new password. Many image banks use OAuth for account approval and verification. You do not set it up yourself, and nothing about it needs a decision from you as a buyer. It is a fair topic to discuss with your IT colleague.

Integration Checklist for Vendor Comparison

Use this table to record what each vendor offers. The Beeldbank.nl column shows what is documented. Fill in facts from your conversations with other vendors. This checklist helps you compare the four core integrations: which ones are included in the base price, which cost extra, and which require additional setup or custom development.

Integration topic	Requirement	How Beeldbank.nl handles it	Your other vendor
Canva connection	Designers use images directly in designs	Yes, included in the base product
API	Other systems can connect with documentation	Yes, documented API available
Single Sign-On	One account for staff, included or extra	Optional, one-time setup available
Azure or Entra ID	Connect to organization login with one-time pricing	Yes, one-time fee of 990 euros
Account verification	Secure protocol for account checks	OAuth protocol

Integrations to Ask About During a Demo

Take this list to every demo so answers can be compared afterwards.

• Design tools: Is there a connection with the tool our designers use, and can one test it?
• API: Is it documented, and who maintains a connection once someone builds it?
• Login: Can staff use one account, and is that included or an extra cost?
• Your identity system: Does it work with the system our organisation already uses, and what does setup need from us?
• Verification: Which protocol checks accounts, and what does our IT colleague need to know?

From Integration to Daily Use

Integrations decide how images reach other tools. The next question is what leaves the image bank and in which shape. Beeldbank.nl offers practical tools for both: a Canva connection for designers, an API for developers, optional SSO for login convenience and Azure or Entra ID for organisations that use Microsoft identity. From there, your team decides which integration fits which workflow.

The image bank documents four connections: Canva, API, optional SSO and OAuth. These connections are documented and working, ready for your team to evaluate. Bring a designer, an IT colleague and the person who manages the images to your next demo, and let each of them ask their own question. For details on how these integrate with specific platforms, see Beeldbank.nl for Designers and Web Teams.