Introducing the AssetCenter API

Today, we're releasing the AssetCenter API. Your team can now connect its own tools to the equipment, people, locations, and subscriptions you manage in AssetCenter.

That opens up useful possibilities: bringing inventory into an internal dashboard, recording an equipment handoff from your service desk, or adding a maintenance note when a job is completed. Your developers can build those connections around the processes your team already uses.

We're also launching an API developer guide, with getting started instructions, a quick start, and a reference page for every endpoint.

Work with your whole inventory

The API covers AssetCenter's four core resources. Each supports listing, reading, creating, updating, and deleting records, along with access to its timeline history.

• Assets: Work with equipment records and automate person, location, and storage assignments. Record condition changes, acquisitions, warranties, and decommissioning.
• People: Maintain the people in your inventory, manage their assignments, and update their active status. These are the people equipment is issued to; they are separate from user accounts that sign in to AssetCenter.
• Locations: Connect sites and their spaces to the assets, people, and subscriptions assigned to them.
• Subscriptions: Manage subscription records, billing details, contracts, assignments, and lifecycle actions such as pausing or canceling a recurring subscription.

You can also work with notes and to-dos across these resources. A reporting integration can read the records it needs, while an operational integration can make changes and leave useful context in the timeline.

Connect the steps around an equipment handoff

Consider a laptop issued through an internal service desk. Someone confirms the handoff in the ticket, then updates the asset record. With the API, your team can connect those steps.

Your integration could:

1. Identify the laptop and the person receiving it using their AssetCenter record IDs.
2. Assign the asset to that person, including a return due date when needed.
3. Add a timeline note with the ticket reference and handoff details.
4. Read the asset timeline to include the recorded history in an internal report.

When the laptop is physically returned, the same integration could put it in storage. That action removes its person assignment and marks the asset available. The recorded state follows the confirmed handoff.

These are examples of workflows you can build with the API. Your integration controls the trigger, matches the records, and sends the requests. The endpoint reference explains the fields and permissions needed for each step.

Choose what each integration can access

An active account administrator can create a token under Settings → API Access. Give it a recognizable name, select Read Only, Full Access, or Custom permissions, and choose an expiration period.

Each token belongs to the organization where it was created. You can give a reporting script read access and create a separate token with the specific permissions needed for an assignment workflow. The token is displayed once, so save it in your integration's secret storage.

The authentication guide explains permission requirements and token management. Read Only is a useful starting point for listing records and reading their timelines; workflow actions need their own permissions.

Documentation for your first request and the next steps

The new guide follows the same format as the user manual, with searchable pages and navigation by resource. Each endpoint page includes its HTTP method and path, required permissions, request fields, an example, and response details.

The quick start walks through setting a token, listing assets, reading a record and its history, and adding a note with cURL. It starts with read requests so you can inspect your own data before making a change.

For recurring integrations, the guide also covers pagination, errors and rate limits, and idempotency and retries. Workflow writes require an idempotency key, which lets an identical retry return the original successful result for 24 hours without repeating the action. Base inventory create, update, and delete endpoints do not provide that replay protection; the guide explains how to handle those separately.

Build your first connection

Choose one task your team repeats: refreshing an inventory report, recording a confirmed handoff, or adding a note after equipment is checked. Start with the records and permissions that task needs, then build from a successful request.

Open getting started to create your token, then follow the API quick start to make your first call.

By Jeremy Francis

Founder & CEO, AssetCenter