The Assets API lets your applications request finished Databook assets, such as account plans, meeting briefs and other decks and documents, and download them without opening the Databook app. It gives you the same asset library and generation engine your users already rely on in Databook, so you can put it wherever your team works.
Why use the Assets API
Databook assets are customer-ready decks and documents, built from Databook's account intelligence and your organization's own templates. Until now, your team had to open the Databook app to create them. With the Assets API, you can:
Meet your team where they work: request an asset from your CRM, an internal portal or your own front end, instead of switching to another app
Cut preparation time: turn an account or meeting into a ready-to-use deck or document in a single request
Keep your standards: every asset uses the templates and content already set up for your organization, so output is consistent wherever it is requested
Keep your controls: the API respects the same access, entitlements and limits as the Databook app, so you don't need to manage a separate set of permissions
What it can do
Show the assets available to a user: list the assets the signed-in user can create, with each asset's name, description and whether it is about a company or a person
Find the right company: search for companies by name to choose who the asset is for
Find the right person: for assets about an individual, such as a briefing on a named executive, list people at the chosen company with their job titles
Request an asset: start generating an asset for a chosen company and, where needed, a person
Track progress: see the status of every asset a user has requested, or check a single request
Download the finished file: get a secure download link once the asset is ready
How it works
Your application authenticates with Databook and passes an access token with each request.
It lists the assets the user can create, so they can choose one.
The user searches for a company. If the asset is about a person, your application also lists people at that company so the user can choose one.
Your application submits the request and receives an ID for the new asset.
Assets take time to generate, so your application checks the request's status until it shows as completed.
Your application requests a download link and passes the file to the user.
Full request and response details, including every endpoint and field, are in the API documentation under Media assets.
Example use cases
One-click assets in your CRM: a seller clicks a button on an account record to request an account plan, and downloads the file when it is ready
Your own seller portal: a front end that shows each user the assets they can create, lets them pick an account and a person, and lists their past assets with download links
Other apps and workflows: add Databook assets to any internal tool or workflow your team already uses
What to expect
Assets are generated, not instant: generation runs in the background. Check the status of a request until it is completed, then download the file
Status updates are by polling: there are no webhooks or notifications when an asset is ready, so your application needs to check periodically
Companies fully available in Databook: company search returns companies that are fully set up in Databook, so assets are built on complete account data
Some assets need a person: assets about an individual need both a company and a person. If your application leaves out the person, the request fails, so check whether an asset is about a company or a person before you request it
Access matches the Databook app: users only see and can request the assets their role and organization allow, including any premium assets they are entitled to
Limits worth knowing
Limit | Value |
Request rate | Rate limiting is applied to keep the service reliable |
Assets generating at once | Each user can only have a limited number of assets generating at the same time, as in the Databook app |
Retries | Requests that go over a limit are not retried automatically. Your application should queue requests and try again |
Notifications | Polling required (no webhooks) |
Getting access
Assets API access requires an entitlement and credentials from Databook. Contact your account team to get set up. There is nothing extra to configure: the assets available through the API are the ones already set up for your organization in Databook.
If your organization limits asset generation to a set of key accounts, the API returns an error message when you request an asset for a company outside that list.