The translation layer for your application landscape

One key.
Every system.

CrossRef knows which record in system A belongs to system B. A simple, secure source of truth for ID translation — without mapping tables scattered across integrations.

Explore the API →See how it works
✓ OAuth 2.1✓ REST API✓ MCP included✓ SaaS / On-Premise
CrossRef integration visual
The problem → solved

Stop teaching every integration
the same mappings.

Applications use different identifiers for the same customer, employee, article or account. CrossRef centralises those relationships, so every integration can ask one service for the right key.

AFAS · accountKL-10042 · Acme B.V.
HR · employeeEMP-4471 · Jane Doe
↔
Exact · accountEX-9981 · Acme B.V.
CRM · employeeUSR-00839 · Jane Doe
↗

Faster integrations

No custom mapping tables per connector.

✓

Fewer errors

One reliable source for identifier translation.

∞

Easy to extend

Add systems without redesigning every flow.

◎

Full visibility

See exactly which records are linked.

Security

Modern access control.
Minimal data exposure.

OAuth 2.1

Authorization Code + PKCE

CrossRef uses the OAuth Authorization Code flow with PKCE. Access tokens protect the API while tenant roles determine which operations a user may perform.

Authorization: Bearer <access_token>
scope: crossref-api offline_access
Included

Built-in MCP server

The same tenant-scoped identifier graph is available to compatible MCP clients through the authenticated /mcp endpoint.

tools: crossref_get_corresponding_key · crossref_get_linked_records · crossref_link_records
auth: Authorization Code + PKCE
◉

Role-based access

Admin, Manager and Member permissions are evaluated within the selected tenant.

ID

No business payloads

CrossRef stores identifier relationships and their configuration, not source-system business records.

⌁

Tenant isolation

Every API request is bound to exactly one customer and database schema.

≡

Structured logging

Structured application and security logging for operations and diagnostics.

Developers

Built for integration developers.

CrossRef is deliberately small: authenticate once, resolve identifiers, inspect relationships and create links. Use the REST API from code or integration platforms, or use the included MCP server from compatible AI developer tools.

Interactive · Demo

CrossRef API Playground

Experience the CrossRef flow before opening Swagger. No real credentials or customer data are used.

Demo environment · OAuth 2.1
SourceInput
CrossRef
TargetOutput
Resolved keyEX-9981
Ready for a demo request
Generated requestGET
Response200 OK · application/json

    


    

      
OAuth 2.1
See the authentication step
This playground uses simulated data and does not request a token. Real clients sign in with Authorization Code + PKCE and request the crossref-api scope.

      
New · MCP included
Use the same graph from AI tools
Switch the code tab to MCP to see the equivalent tool call. The same CrossRef authorization model applies.
AI / IDE→MCP→CrossRef→ERP / CRM / HR

    

  





Quick start
Resolve an identifier
Example: translate AFAS account KL-10042 into its Exact identifier.


OAuth 2.1
Authorization Code + PKCE
Start the Authorization Code flow at CrossRef, use PKCE, and send the issued access token as a Bearer token. Request the crossref-api scope and offline_access when a refresh token is needed.
Authorization: Bearer <access_token>
scope: crossref-api offline_access


REST API
Core endpoints
GET
/crossref/{domain}/Apps/{app}/{key}/{to_app}Resolve a corresponding key
GET
/crossref/{domain}/Apps/{app}/{key}Get all records linked to a key
POST
/crossref/{domain}/Apps/{app}/{key}/{to_app}/{to_key}Link two records
GET
/crossref/{domain}/AppsList applications in a domain
POST
/crossref/{domain}/AppsAdd an application


Included
The same key graph, available through MCP
Compatible MCP clients can call the same tenant-scoped CrossRef operations through the authenticated /mcp endpoint.
AI / IDE→MCP→CrossRef→AFAS · Exact · CRM · ERP
crossref_get_corresponding_key({ domain: "account", application: "AFAS", key: "KL-10042", toApplication: "Exact" })
→ ["EX-9981"]


Access model
Tenant-scoped roles & permissions
Permissions are read from the active tenant membership and enforced per endpoint.
AdminFull access
  • Create & manage domains
  • Manage applications
  • Query & link records
  • Access to every public REST operation
MemberOperational
  • Manage applications
  • Query & link records
  • No domain management
ManagerFocused access
  • Browse domains and applications
  • Query and resolve identifiers
  • No changes to domains, applications or links


Open API documentation →Request developer access


Hosting
Your infrastructure or ours.
Both deployment models run the same CrossRef API.
Self-hosted
Infrastructure control
  • Run the same ASP.NET Core application yourself
  • Manage your own infrastructure and backups
  • Use your own SQL Server configuration
  • Authorization Code + PKCE and MCP
Hosted
Managed deployment
  • Customer data is isolated by database schema
  • Updates are released through the managed deployment pipeline
  • Users and roles are managed per customer
  • Authorization Code + PKCE and MCP


CrossRef
Ready to simplify your integrations?
One central service for record linking across your application landscape.

























The contact form is temporarily unavailable. Email us at info@web-bis.eu.