Asset Router
Integration guide
Start in your workspace, then connect your systems.
flowchart TD
accTitle: Publish terms and control access
accDescr: The publisher defines terms in Asset Router and links them from its site. The publisher server checks authorisation before delivering content to an application.
A[Define resources and permitted uses] --> B[Publish licence terms]
B --> C[Link terms from your website]
C --> D[Application requests authorisation]
D --> E[Your server checks the token]
E --> F[Your server delivers the content]
Discovery and protection are separate
Publishing a reference makes the licence discoverable. Your server must also check the token to protect a download. The content stays on your infrastructure.
Choose the resources and permitted uses. A single file can be identified by its exact URL.
Open the workspace and create your publisher profile. Describe each resource or collection, permitted uses and licence conditions. An individual PDF can be identified by its exact URL; it does not need a new folder structure. Publish only terms you are entitled to grant.
Publish the licence reference on your site. For protected content, also connect the token check to your server.
AssetRouter hosts the machine-readable licence document. Publish the supplied reference on your website, for example in robots.txt. This is a website change, not a DNS record. Updating the licence in AssetRouter updates the hosted document.
A reference advertises terms; it does not protect a download. For protected content, your server must check the access token before returning the resource. Follow the resource-server contract and, if relevant, the CDN guide. Close any alternate public download path to the same protected resource.
Confirm existing agreements or offer terms customers can accept. Payments stay in your existing channels.
Customers can declare an existing licence in their library. Review the customer, covered resources and expiry before confirming it. A declaration alone does not authorise access. You can also record a licence sold directly. You receive payment through your existing channels; AssetRouter does not collect it.
An offer that permits acceptance in AssetRouter can grant rights after its stated conditions are met. A request for access does not create a new sale by itself. Revoke or update rights when the underlying agreement changes. AssetRouter does not read your ERP: you provide the relevant information manually or through an agreed integration.
Consult and export authorisation records. Additional continuity services are optional.
You can consult and export your requests and authorisations. AssetRouter signs its service records; you do not need a signing key. The record establishes the service decision, not delivery or use of the content.
The hosted base requires no backup installation in your infrastructure. Independent copies and an emergency replacement service are optional paid arrangements that must be prepared and tested in advance. Without that option, operation depends on AssetRouter availability.
Start with standard self-service setup. Request a quote if you need a custom integration.
Use the API reference for server integration. Standard self-service setup is free; custom integration and ongoing support are quoted separately.