Skip to main content

Accept a pending entry

POST 
/api/v1/resources/pending/accept

Recognizes a pending Platform / Device Type / Group / Version. Resources are auto-created from the reported values (existing ones are just cleared); a Version is created via the pending-versions flow.

Request​

Body

required

    type stringrequired

    Possible values: [PLATFORM, DEVICE_TYPE, GROUP, VERSION]

    Which kind of pending entry this is (platform / device type / group / version)

    token stringrequired

    Identifier of the pending entry. For PLATFORM/DEVICE_TYPE/GROUP it is the reported token; for VERSION it is "projectName@version".

    reason string

    Optional free-text note explaining the decision; stored on the pending entry for audit

    name string

    Display name for the created resource. For PLATFORM/DEVICE_TYPE, defaults to the reported token. For GROUP it is a display name distinct from the numeric unit (the unit becomes the group id); defaults to "Unit ".

    description string

    Optional description for the created resource (e.g. a unit/group description).

    parentGroupId number

    GROUP only: id of the parent unit to nest the new unit under. Omit to create a root unit.

    assignReportingDevices boolean

    Default value: true

    GROUP only: attach the devices that reported this unit to the newly created unit. Defaults to true; set to false to skip.

    isDraft boolean

    VERSION only: create the version as a draft release. Defaults to true.

    username string

    Username performing the action. Populated from the auth token by the gateway (used when a VERSION accept creates the project/release on the user behalf).

Responses​

Entry accepted and recognized

Loading...