API Key

API key, application key, access key, authentication key, API token
An API key is a unique code that identifies your application to an external service or platform. Essential for secure links between systems.

What is an API Key?

An API key is a unique set of characters that acts as a digital key that identifies your application, website or system to an external service. This key provides access to specific functionalities of a platform and determines what actions you are allowed to perform. For an SMB, this means that you can securely link with, for example, your payment provider, CRM system or e-mail marketing tool without having to log in manually each time.

How an API key works in practice

When you link between two systems, you send the API key along with each request as an identifier. The receiving service checks whether this key is valid and which rights are attached to it. For example, an ecommerce store that sends orders to a shipping platform sends an API key with each new order. The shipping platform thus recognizes which ecommerce store is making the request and which rates and settings apply. The key acts as a digital signature confirming that the request is legitimate. Unlike a password, you don't have to enter an API key manually every time, the system uses it automatically in every communication between the two platforms.

Why API keys became necessary

Before the advent of API keys, systems had to communicate with usernames and passwords, which was insecure because these credentials were often sent in plain text. As companies began building more automated links between their Web site, CRM, accounting and marketing tools, the need for a more secure method arose. API keys offer a middle ground: they are unique per link, you can revoke them without modifying your main account, and you can define which actions are allowed per key. An employee who leaves no longer needs access to your entire Google account; you simply revoke the specific API key used for that integration. This granularity makes API keys the standard for virtually all modern web development and system integrations.

What API keys bring to your business

API keys automate processes that otherwise require manual work. An ecommerce store can automatically sync stock levels with an external warehouse system, a lead form can create contacts directly in your CRM, and your website can request real-time shipping costs from PostNL or DHL. For an SME with limited IT capacity, this means less error-prone manual input and faster turnaround times. A practical example: a B2B wholesaler in Eindhoven linked their ecommerce store to their existing ERP system via API keys, allowing customers to instantly see current prices and delivery times without the administration having to manually synchronize files every night. At Monkey Vision we regularly build these kinds of links, where the API key is the crucial link between your website and the underlying systems you already use.

Applications of API Key

API keys occur in virtually every business process where systems talk to each other. From payment processing to marketing automation, from inventory links to analytics, anywhere you want to replace manual work with an automated exchange of data, an API key comes into play. Here are the most common scenarios in which SMBs deploy API keys.

Payments and transactions in ecommerce stores

Every ecommerce store has a link to a payment provider such as Mollie, Adyen or Stripe. When a customer pays, your ecommerce store sends a payment request via API to the provider, using the API key as identification. The provider thus recognizes your account, applies the correct rates and sends confirmation back to your system. Without this key, the payment provider would not know to which account the amount should be transferred. In practice, you often use two keys: a test key for the development environment and a live key for the production environment. This prevents you from accidentally triggering real payments during testing. A common mistake is that the test-key accidentally remains live after a website update, preventing customers from making real payments.

CRM and marketing automation links

When you have a contact form on your website and want to automatically put new leads into ActiveCampaign, HubSpot or Salesforce, it is done through an API key. The key gives your website permission to create contacts in your CRM account without anyone having to log in manually. You can also restrict permissions per key: one key for contact creation only, another for retrieving segment lists. This is more secure than one general access. A web design agency we know in Utrecht uses API keys to synchronize the registrations of their online courses directly with their email marketing, including tags based on the chosen course type. This saves hours of manual copying and pasting each week and avoids typing errors in email addresses.

Analytics and tracking integration

Google Analytics, Hotjar, Matomo and other analytics tools use API keys to exchange data. For example, you can use the Google Analytics API to automatically retrieve reports and display them in your own dashboard, or forward conversion data to your advertising platform for better optimization. The API key ensures that only your system has access to your specific analytics data. For an ecommerce store with multiple sales channels, this is valuable: you use API keys to retrieve data from Google Analytics, your advertising platform and your shipping system and combine them into one overview. Without API keys, you would have to manually log into four different tools every day to get a complete picture.

When an API key is the right choice and when it is not

API keys are ideal for server-to-server communications and background processes that do not require direct user interaction. They are less suitable for situations where individual users need access to their own data, such as a customer portal where someone views their own order history. For that, you're better off using OAuth or session-based authentication. An API key is also not the best choice if you exchange highly sensitive data without additional encryption, because the key itself is a static string that can be misused if stolen. In that case, add additional layers of security such as IP whitelisting or time-based tokens. However, for standard SME applications such as a link between your website and your accounting software, your CRM or your shipping partner, an API key is the fastest and most reliable method.

Want to apply this to your business? Monkey Vision helps SME entrepreneurs with web design, SEO and smart digital solutions. Schedule a no-obligation meeting and find out what's possible for you.

Schedule an introduction

Frequently Asked Questions

No, although both serve for access control, they work differently. A password you enter when logging in as a user, an API key your system uses automatically in any communication between two applications. A password is associated with a person, an API key with a specific link or application. You can have multiple API keys for different purposes, each with its own permissions. If a key is leaked, you revoke only that key without resetting your entire account. Another difference: API keys are often sent in the header of an HTTP request, while passwords go through secure login forms. In practice, you combine both: you log in with your password to create an API key, and then your system uses that key for automated tasks.

Choose an API key for links between your own systems or fixed services that do not require user permissions per session, such as your ecommerce store that forwards orders to your shipping partner. OAuth tokens are used when individual users give access to an external app to do something on their behalf, such as "Log in with Google" or an app that posts tweets on your behalf. For SMBs, internal automations and fixed integrations run on API keys, external apps that authorize customers themselves use OAuth. An ecommerce store that automatically sends invoices to your accounts: API key. A scheduling app in which customers link their own Google Calendar: OAuth. API keys are easier to implement but less flexible for situations with changing users. In doubt? Look at who initiates the action: your system automatically = API key, an end user giving permission = OAuth.

Start with one concrete automation that now takes manual work. Think of new website contacts that you manually put into your CRM every day, or orders that you copy-paste to your shipping portal. Identify which tools you already use and check in their documentation to see if they offer an API. Most modern platforms like Mollie, ActiveCampaign or WooCommerce have an "API" or "Integrations" section in the settings where you can create a key. Read the documentation of both platforms you want to link, or engage a developer for the technical implementation. Always test in a development environment with test keys before going live. Never store API keys in your code or in public repositories, use environment variables or a secure configuration manager. For more complex links to multiple systems, an automation platform or custom integration may be worth the investment.

The biggest mistake is putting API keys hardcoded into your website code, making them visible in your GitHub repository or source code. This happens more often than you think and leads to abuse. Always use environment variables or a secrets manager. A second pitfall: assigning too broad permissions to a single key. Rather, create multiple keys with specific permissions per function, so that in case of an incident, you only need to revoke that one key. Also pay attention to rate limits: Many APIs limit the number of requests per minute. If your system sends a request too often, you will be temporarily blocked. Test this beforehand. Don't forget to revoke old keys you no longer use, because every active key is a potential security risk. And finally, document which key is used for what, otherwise six months from now no one will remember which integration stops when you delete a key.

The best approach depends on how many links you have and how technical your team is. Do you have one or two simple integrations? Then it is often sufficient to enter the API keys via the plugin settings of your CMS and regularly check whether they are still actively used. Want to connect multiple systems or automate complex workflows? Then schedule a free 30-minute integration scan at Monkey Vision. We will walk through your current toolstack, identify which links save the most time and give you a concrete roadmap including security advice. You get instant insight into what APIs are available, what is feasible within your budget and what you can do yourself. No sales pitch, just practical advice tailored to your situation.

About the author

Monkey Vision

Monkey Vision is a full-service digital agency in Remote, specializing in web design, SEO and AI automation for SMEs. The knowledge base is compiled by our team of online strategists and continuously updated based on current insights.

Publication date: 26-04-2026
Last update: 26-04-2026