> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getprimo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Sync a device software state

> Trigger a resync of ONE device's software from the MDM provider (Fleet) so its install state (installed/failed/in_progress) is refreshed. Runs in the background; re-read with `getDeviceSoftware` afterwards. To resync the whole company catalog instead, use `syncCompanySoftwares`. This reads what the MDM already knows, and only the software rows: to make the device itself re-report its inventory after a fix, use `refetchDevice` first; to refresh the rest of Primo's device record from the MDM, use `syncPrimoDevice`.

<span className="badge-write">Key: Write</span><span className="badge-company">Scope: Company</span>


## OpenAPI

````yaml https://api.getprimo.com/openapi.json post /devices/{deviceId}/software/sync
openapi: 3.1.1
info:
  title: Public API - BETA
  description: Read docs on https://docs.getprimo.com/
  version: '1.0'
  contact: {}
servers:
  - url: https://api.getprimo.com
security:
  - apikey: []
tags: []
paths:
  /devices/{deviceId}/software/sync:
    post:
      tags:
        - Devices
      summary: Sync a device software state
      description: >-
        Trigger a resync of ONE device's software from the MDM provider (Fleet)
        so its install state (installed/failed/in_progress) is refreshed. Runs
        in the background; re-read with `getDeviceSoftware` afterwards. To
        resync the whole company catalog instead, use `syncCompanySoftwares`.
        This reads what the MDM already knows, and only the software rows: to
        make the device itself re-report its inventory after a fix, use
        `refetchDevice` first; to refresh the rest of Primo's device record from
        the MDM, use `syncPrimoDevice`.
      operationId: syncDeviceSoftware
      parameters:
        - name: deviceId
          required: true
          in: path
          schema:
            type: string
      responses:
        default:
          description: ''
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/DeviceSoftwareActionResult_Output'
components:
  schemas:
    DeviceSoftwareActionResult_Output:
      type: object
      properties:
        success:
          type: boolean
          const: true
        message:
          type: string
          description: A human-readable description of the action
      required:
        - success
        - message
      additionalProperties: false
  securitySchemes:
    apikey:
      scheme: bearer
      bearerFormat: API key
      type: http
      description: >-
        Use your Primo API key in the Authorization header as `Bearer
        <API_KEY>`.

````