---
title: "Event Handling Status Update"
method: POST
path: "/entities/asset/{asset_id}/callback/{event_id}"
tags: ["4. Assets"]
---

# Event Handling Status Update

`POST /entities/asset/{asset_id}/callback/{event_id}`

Provide an update on the handling of a given event by a given asset.

This endpoint allows asset controllers to report back the status of event handling. The `asset_id` can be either the Axle UUID or an external ID if `asset_id_is_external` is true.

Note: This will not work for non-UUID external asset IDs.

## Path parameters

- `asset_id` string, uuid, required
- `event_id` string, required

## Query parameters

- `asset_id_is_external` boolean

## Request body

- EventResponse — Response for an asset event status update.
  - `timestamp` string, date-time, required — Timestamp for the response (UTC)
  - `status` 'RECEIVED' | 'ACCEPTED' | 'REJECTED' | 'FAILED' | 'EXECUTED', required — Status values for asset event handling. - RECEIVED: Event was received by the system - ACCEPTED: Event was accepted for processing - REJECTED: Event was rejected (invalid or not applicable) - FAILED: Event processing failed - EXECUTED: Event was successfully executed

## Response `200`

Status update successfully recorded

- unknown

## Other responses

- `404` — Asset not found or not authorized to access
- `422` — Validation Error

---

[API](https://skmtc.dev/axle/apis/axle-api-docs.md) · [All operations](https://skmtc.dev/axle/apis/axle-api-docs/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/axle/axle-api-docs/revisions/75be7f9a952f/schema)