Authentication
How to authenticate against the Event Connectors API using a Bearer API token
Every request to the Event Connectors API requires authentication via a Bearer token in the Authorization header:
Authorization: Bearer <token>Tokens are long-lived and account-scoped — they don't expire and they don't need to be refreshed.
Getting an API Token
You need an Event Connectors account
API tokens are issued against an Event Connectors account. If you do not yet have one, contact your Event Connectors representative or support@eventconnectors.nl to get set up.
Find your token in the console
If your account has the right permissions, you can see and create tokens directly:
- Sign in to the Event Connectors console at app.eventconnectors.nl.
- Navigate to Account → Tokens.
- Create a new token and copy the value.
Don't see the Tokens page?
Not every user account has rights to see or create access tokens — token management is restricted to account administrators. If you cannot find the Tokens page, or you don't have permission to create one, you can request a token through support.
Request a token via support
Email support@eventconnectors.nl and we'll create one for you. Use the link to open your mail client with the request pre-filled — fill in your account name and use case before sending.
Using the Token
Include the token in the Authorization header of every request.
curl -H "Authorization: Bearer YOUR_API_TOKEN" \
https://app.eventconnectors.nl/api/eventsconst response = await fetch("https://app.eventconnectors.nl/api/events", {
headers: {
Authorization: "Bearer YOUR_API_TOKEN",
},
});
const data = await response.json();Further Notes
- Production host: All API requests should use
https://app.eventconnectors.nl/api. If your integration still referencesapp.thefeedfactory.nl, update it to the new host. - Keep tokens secret: API tokens grant the same access as your account. Treat them as you would a password — store them in a secrets manager, not in source control.
- See the API Reference for the full endpoint list and request/response schemas.