← Back to docs
Guides
GUIDEAuthentication and tokens
Authentication guide
This guide explains how Entylink authentication works across company data routes, webhook routes, and dashboard account routes so teams can wire the correct token type into each workflow.
When to use it
Practical implementation contexts
Configure a server-side API client for company search and company lookup
Use dashboard sessions for account routes such as key management and usage
Avoid mixing token types between data routes and dashboard-only routes
Auth
Access model
Authentication
Data routes accept an API key or dashboard session through `Authorization: Bearer ...`. Account routes such as `/v1/keys` and `/v1/usage` require a dashboard session.
Header examples
# API key on company-data routes
curl "https://api.entylink.com/v1/search?q=revolut&items_per_page=10" \
-H "Authorization: Bearer etl_live_..."
# Session token on dashboard account routes
curl https://api.entylink.com/v1/keys \
-H "Authorization: Bearer eyJhbGciOiJIUzI1NiIs..."
Parameters
ParameterTypeDescription
AuthorizationheaderBearer token header used on authenticated requests
etl_live_...API keyUse for search, company, officers, PSCs, filings, and webhooks
session tokenJWTReturned by sign-up or log-in and used for dashboard account routes
Success and failure examples
Authenticated response + 401 exampleReference
Successful authenticated request:
{
"data": {
"items": [
{
"company_number": "08804411",
"company_name": "REVOLUT LTD",
"company_status": "active"
}
]
}
}
401 unauthorized:
{
"error": "unauthorized",
"message": "Missing or invalid Authorization header. Use: Bearer <api_key_or_session>",
"status": 401
}Related pages
Keep moving from docs into implementation and evaluation
Next step
Move from docs into a real registry workflow.
Entylink is built for teams embedding UK company data, verification, and monitoring into products rather than manually browsing the register.