---
title: "Retrieve the specified work activity of a work order"
method: GET
path: "/odata/workorders({workorderId})/workactivities({workactivityId})"
tags: ["WorkActivities"]
---

# Retrieve the specified work activity of a work order

`GET /odata/workorders({workorderId})/workactivities({workactivityId})`

## Request

- Base URL: `https://sb2api.servicechannel.com/v3`
- URL: `https://sb2api.servicechannel.com/v3/odata/workorders({workorderId})/workactivities({workactivityId})`
- Auth: OAuth 2
  - Authorization code: `https://sb2login.servicechannel.com/oauth/authorize`
  - Token URL: `https://sb2login.servicechannel.com/oauth/token`
- TypeScript: <https://skmtc.dev/servicechannel/apis/servicechannel-api-v-3/docs/odata/workorders(:workorderId)/workactivities(:workactivityId)/get.ts> (a function with typed inputs; its response is checked against the schema)

Returns the specified work activity of a work order.
            <br />A work activity details information about the technician's work on a service request: the time when the technician started and finished their work, the type of activity they carried out, the number of technicians who rendered the service, and other details related to the labor performed.
            <br />***Note:*** Both subscribers and providers can use this method.

## Path parameters

- `workactivityId` integer, required
- `workorderId` integer, required

## Query parameters

- `$expand` string
- `$select` string
- `$filter` string
- `$orderby` string
- `$top` integer
- `$skip` integer
- `$count` boolean

## Response `200`

The requested work activity of the specified work order is in the response.

- ServiceChannelServicesMessagingWorkordersWorkActivity: Work activity object.
  - `Id` integer: The unique numeric identifier of the work activity.
  - `WorkOrderId` integer: The unique numeric identifier of the work order for which the work activity was reported.
  - `TimeIn` string, date-time: The date and time when the technician started work on the service request.
  - `TimeOut` string, date-time: The date and time when the technician finished work on the service request.
  - `IsTimeEdited` boolean: Indicates if the time of the labor performed was modified.
  - `User` ServiceChannelServicesMessagingUsersUserInfo: The user details object.
    - `Id` integer: The unique numeric identifier of the user.
    - `UserName` string: The username of the user.
    - `UserNameOrFullName` string: The username if fullname is null or empty
    - `FullName` string: The full name of the user.
    - `Email` string: The email address of the user.
    - `LevelInfo` ServiceChannelApiModelProposalsMlpLevelSimpleModel
      - `UserId` integer
      - `LocationIds` integer[]
      - `LevelId` integer
      - `LevelName` string
      - `Order` integer
      - `UsersLocations` object
      - `CategoryChange` boolean
      - `PriorityChange` boolean
      - `CodeChange` boolean
      - `DivisionId` integer
  - `CallerId` string: Possible values: a) The GPS coordinates of the location where the technician performed the most recent action — either check-in or check-out — via the ServiceChannel Provider mobile app. b) The phone number of the technician from which they performed the most recent action — either check-in or check-out — using the IVR (Interactive Voice Response) system. c) Null value if the work activity was entered manually.
  - `ResolutionCode` string: The most recent status assigned to the work order by the technician.
  - `WorkType` string: The type of activity performed: *Repair* or *Travel*. Other values may be returned if custom types are set up for the subscriber.
  - `HasCheckInInfo` boolean: Indicates if a check-in was performed for the work activity.
  - `HasCheckListResponse` boolean: Indicates if the technician answered checklist questions.
  - `TechsCount` integer: The number of technicians who performed the work.
  - `Name` string: The technician performed the work.
  - `CreatedBy` integer: The user who created the labor.

## Other responses

- `400`: The request is not accepted due to bad syntax, missing parameters, insufficient data, etc. <br/>Error codes: 502 — WorkOrder not found 502 — Work activity is not found
- `401`: The request is not authorized. <br/>Error codes: 504 — API call rejected by security permissions
- `500`: The server was unable to complete the request due to an internal error.

---

[API](https://skmtc.dev/servicechannel/apis/servicechannel-api-v-3.md) - [All operations](https://skmtc.dev/servicechannel/apis/servicechannel-api-v-3/llms.txt) - [OpenAPI document](https://skmtc.dev/servicechannel/apis/servicechannel-api-v-3/revisions/d490d6596809?raw)
