⚠️ Linux only. Custom actions apply exclusively to Linux-managed devices. This endpoint is not applicable to Android, iOS, or Windows devices.

Retrieves all custom actions defined for the tenant. Returns a list of CustomActionRead objects representing every custom action in the tenant, including their name, type, state, position settings, options, and audit metadata. Supports ordering to control the sort order of results. Use this endpoint to enumerate available custom actions before assigning them to a Blueprint or deploying them to Linux devices.

About Custom Actions

Custom actions allow operators to define custom scripts and commands that can be surfaced on Linux devices, either within a Blueprint's settings sections or as device Quick Actions. Each custom action has a type (button, toggle, radio, or dropdown), a state (draft, active, or inactive), and one or more options, each of which contains a Linux platform script. Only active custom actions can be deployed to devices. Custom actions are managed separately from blueprints but referenced within Blueprint settings via position_in_blueprints.

Key Query Parameters

ordering — Sort results by a specified field; prefix with - for descending order (e.g., -created_at for newest first)

Common Use Cases

List all custom actions before deciding which to include in a Blueprint V2 configuration

Audit the state of all custom actions to identify which are active vs. draft or inactive

Retrieve id values for use in subsequent GET, PUT, or DELETE calls on specific custom actions

Best Practices

Filter mentally by state in your integration logic: only active custom actions can be deployed to devices; drafts are not eligible

Use ordering=-created_at to surface recently created or modified actions first

Pair with GET /v2/custom-actions/{custom_action_id}/ when you need the full option and script payload for a specific action

Workflow

Call GET /v2/custom-actions/ to retrieve the full list of tenant custom actions

Review the state and position_in_blueprints fields to identify which actions are deployment-ready

Use the returned id values to fetch, update, or delete individual custom actions as needed