/api/v1/search
Search records
Search assets, people, locations, and subscriptions in one request.
Last updated
Request
GET /api/v1/search
Requires at least one of assets:read, people:read, locations:read, or subscriptions:read. See token permissions.
Send Authorization: Bearer YOUR_API_TOKEN and Accept: application/json.
Query parameters
-
searchstring Required - The text to search for, up to 255 characters.
-
per_pageinteger Optional - The maximum number of results for each record type. Accepts
1–100; defaults to10.
Example
Set ASSETCENTER_API_TOKEN as described in the quick start. Replace example record and option IDs with values from your organization.
curl --request GET "https://my.assetcenter.app/api/v1/search?search=lenovo&per_page=5" \
--header "Authorization: Bearer $ASSETCENTER_API_TOKEN" \
--header "Accept: application/json"
Response
200 OK. One array per record type the token can read. Records use the same shape as each type’s list endpoint; the asset is abbreviated here.
{
"data": {
"assets": [
{
"id": 123,
"asset_tag": "LAP-042",
"manufacturer": "Lenovo",
"model": "ThinkPad T14",
"serial_number": "PF3K9X2",
"status": "available",
"category_id": 7,
"created_at": "2026-09-07T16:00:00.000000Z",
"updated_at": "2026-09-07T16:00:00.000000Z"
}
],
"people": [],
"locations": [],
"subscriptions": []
}
}
Behavior and constraints
Each record type is matched the same way as the search parameter on its list: assets, people, locations, and subscriptions. Results in each group are newest first by ID. Types the token cannot read are left out of data entirely, rather than returned empty. There is no pagination; to page through every match of one type, use that type’s list endpoint with search.
Errors
401 means the token is missing, expired, revoked, or not a customer API token. 403 means a required permission or administrator access is missing. 422 identifies invalid or unsupported input; inspect the errors object when present. 429 means a rate limit was reached. See error handling and rate limits.