AWA Agent API
-
- UpdatedJan 30, 2025
- 16 minutes to read
- Yokohama
- API reference
The AWA (Advanced Work Assignment) Agent API provides endpoints to manage agent presence, channel availability, and workload.
This API requires the Advanced Work Assignment (com.glide.awa) plugin and the awa_integration_user role. For more information, refer to Advanced Work Assignment.
AWA Agent - GET /now/awa/agents/{user_id}
Returns the current agent presence state and channel availability.
URL format
Versioned URL: /api/now/{api_version}/awa/agents/{user_id}
Default URL: /api/now/awa/agents/{user_id}
Supported request parameters
Name | Description |
---|---|
api_version | Optional. Version of the endpoint to access. For example, v1 or v2. Only specify this value to use an endpoint version other than the
latest.
Data type: String |
user_id | Sys_id of the work item.
The work item must meet the following criteria:
Data type: String Table: AWA Work Item [awa_work_item] |
Name | Description |
---|---|
None |
Header | Description |
---|---|
presence.channels.available | Flag that indicates whether the channel is available.
Possible values:
Data type: Boolean |
presence.channels.sys_id | Channel sys_id.
Data type: String Table: Service Channels [awa_service_channel] |
presence.sys_id | Presence state sys_id.
Data type: String Table: Presence States [awa_presence_state] |
Headers
The following request and response headers apply to this HTTP action only, or apply to this action in a distinct way. For a list of general headers used in the REST API, see Supported REST API headers.
Header | Description |
---|---|
Accept | Data format of the response
body. Supported types: application/json or
application/xml.
Default: application/json |
Content-Type | Data format of the
request body. Supported types: application/json or
application/xml.
Default: application/json |
Header | Description |
---|---|
None |
Status codes
The following status codes apply to this HTTP action. For a list of possible status codes used in the REST API, see REST API HTTP response codes.
Response body parameters (JSON or XML)
Example: Sample cURL request
AWA Agent - GET /now/awa/agents/{user_id}/capacities
Returns an agent's channel capacities, universal capacity, and the current workload to see if the agent can handle a case.
Use the AWA Agent - PUT /now/awa/agents/{user_id}/capacities method to modify the channel and universal capacities of an agent.
URL format
Versioned URL: /api/now/{api_version}/awa/agents/{user_id}/capacities
Default URL: /api/now/awa/agents/{user_id}/capacities
Supported request parameters
Name | Description |
---|---|
api_version | Optional. Version of the endpoint to access. For example, v1 or v2. Only specify this value to use an endpoint version other than the
latest.
Data type: String |
user_id | Sys_id of the agent listed. Data type: String Table: User [sys_user] |
Name | Description |
---|---|
None |
Name | Description |
---|---|
None |
Headers
The following request and response headers apply to this HTTP action only, or apply to this action in a distinct way. For a list of general headers used in the REST API, see Supported REST API headers.
Header | Description |
---|---|
Accept | Data format of the response
body. Supported types: application/json or
application/xml.
Default: application/json |
Header | Description |
---|---|
None |
Status codes
The following status codes apply to this HTTP action. For a list of possible status codes used in the REST API, see REST API HTTP response codes.
Response body parameters (JSON or XML)
Example: Sample cURL request
The following example shows how to get the capacity and workload values for a user.
A successful response includes capacity values and workload for each channel.
AWA Agent - GET /now/awa/agents/{user_id}/presence_states
Returns an agent's presence states and indicates whether the agent is available or in another presence state.
URL format
Versioned URL: /api/now/{api_version}/awa/agents/{user_id}/presence_states
Default URL: /api/now/awa/agents/{user_id}/presence_states
Supported request parameters
Name | Description |
---|---|
api_version | Optional. Version of the endpoint to access. For example, v1 or v2. Only specify this value to use an endpoint version other than the
latest.
Data type: String |
user_id | Sys_id of the agent listed. Data type: String Table: User [sys_user] |
Name | Description |
---|---|
None |
Name | Description |
---|---|
None |
Headers
The following request and response headers apply to this HTTP action only, or apply to this action in a distinct way. For a list of general headers used in the REST API, see Supported REST API headers.
Header | Description |
---|---|
Accept | Data format of the response
body. Supported types: application/json or
application/xml.
Default: application/json |
Header | Description |
---|---|
None |
Status codes
The following status codes apply to this HTTP action. For a list of possible status codes used in the REST API, see REST API HTTP response codes.
Response body parameters (JSON or XML)
Example: Sample cURL request
The following example shows how to get the presence states for a specified agent.
The response body lists the agent's possible presence states and indicates that the agent is available.
AWA Agent - PUT /now/awa/agents/{user_id}
Sets the state of a specified agent’s presence and, if provided, sets the agent’s channel availability for that state.
URL format
Versioned URL: /api/now/{api_version}/awa/agents/{user_id}
Default URL: /api/now/awa/agents/{user_id}
Supported request parameters
Name | Description |
---|---|
api_version | Optional. Version of the endpoint to access. For example, v1 or v2. Only specify this value to use an endpoint version other than the
latest.
Data type: String |
user_id | Sys_id of the agent. Data type: String Table: User [sys_user] |
Name | Description |
---|---|
None |
Headers
The following request and response headers apply to this HTTP action only, or apply to this action in a distinct way. For a list of general headers used in the REST API, see Supported REST API headers.
Header | Description |
---|---|
Accept | Data format of the response
body. Supported types: application/json or
application/xml.
Default: application/json |
Content-Type | Data format of the
request body. Supported types: application/json or
application/xml.
Default: application/json |
Header | Description |
---|---|
None |
Status codes
The following status codes apply to this HTTP action. For a list of possible status codes used in the REST API, see REST API HTTP response codes.
Example
AWA Agent - PUT /now/awa/agents/{user_id}/capacities
Enables updating an agent's maximum capacity (workload) for channel capacities and universal capacity.
Use the AWA Agent - GET /now/awa/agents/{user_id}/capacities method to retrieve the current channel and universal capacities of an agent.
URL format
Versioned URL: /api/now/{api_version}/awa/agents/{user_id}/capacities
Default URL: /api/now/awa/agents/{user_id}/capacities
Supported request parameters
Name | Description |
---|---|
api_version | Optional. Version of the endpoint to access. For example, v1 or v2. Only specify this value to use an endpoint version other than the
latest.
Data type: String |
user_id | Sys_id of the agent listed. Data type: String Table: User [sys_user] |
Name | Description |
---|---|
None |
Name | Description |
---|---|
channels | Mandatory if updating the maximum value of one or more channels for the
specified agent. JSON object containing one or more key-value pairs mapping the
channel to its maximum capacity for each channel assigned to the agent. Data type: Object The pair is in the following format:
|
universal_capacity | Mandatory if universal capacity is being updated. Maximum capacity for the agent across all service channels. If an agent's current workload equals the maximum universal capacity, additional work items won't be assigned to the
agent.
Data type: Number |
Headers
The following request and response headers apply to this HTTP action only, or apply to this action in a distinct way. For a list of general headers used in the REST API, see Supported REST API headers.
Header | Description |
---|---|
Accept | Data format of the response
body. Supported types: application/json or
application/xml.
Default: application/json |
Header | Description |
---|---|
None |
Status codes
The following status codes apply to this HTTP action. For a list of possible status codes used in the REST API, see REST API HTTP response codes.
Status code | Description |
---|---|
200 | Successful. The request was successfully processed. |
400 | Bad Request. A bad request type or malformed request was detected. |
404 | Not found. The requested item wasn't found. |
Response body parameters (JSON or XML)
Example: Sample cURL request
The following example shows how to change the agent's universal capacity and the maximum capacity for a specified channel.
A successful response includes the updated capacity values.