Table of Contents | ||||
---|---|---|---|---|
|
...
By default, 20 items will be returned at a time. However, the User can retrieve up to 50 items in a single API call by changing the ‘limit’ field. If you wish to retrieve more than 50 listings, you can do so by using the 'page' field and making more than one API call.
These parameters are added in addition to any fields from the specific data types.
These parameters are added in addition to any fields from the specific data types.
Parameter | Default | Description |
---|---|---|
limitLIMIT | 20 | Number of listings to show. Maximum is 50. |
pagePAGE | 1 | Page number to show. To view more than 50 listings, make successive API calls while incrementing this field. |
Response Data
Name | Datatype | Searchable | Notes |
---|---|---|---|
SD_TYPE | string | Yes | The type of the SD item (e.g. Inquiry), use TYPE for search |
SD_NUMBER | string | Yes | The unique identifier for a service desk item |
DUE_DATE | string | Yes | The date established for the service desk item to be completed |
DESCRIPTION | string | Yes | A brief description of the service desk item |
OWNER | string | Yes | Name of the service owner – either a Contact or Dept. Hierarchy |
CSR | string | Yes | The Customer Service Representative |
REQUESTOR | string | Yes | The contact that initiated the service desk item |
SD_SOURCE | string | Yes | The originating source of the service desk item (e.g., email or phone) |
SD_STATUS | string | Yes | Current status of the service desk item |
SERVICEDESK_REMARKS | list | No | All remarks or comments for the service desk item and its actions |
SERVICEDESK_EMAIL | list | No | The email thread concerning the service desk item |
SERVICEDESK_ATTACHMENTS | list | No | List of attachment documents and files |
SERVICEDESK_ACTIONS | list | No | List of all actions for the service desk item |
SERVICEDESK_EQUIPMENT | list | No | List of all equipment to be used/associated with the service desk item |
SERVICEDESK_CONTACTS | list | No | List of contacts for the service desk item |
SERVICEDESK_CHARGES | list | No | List of all charges to be billed on the service desk item |
SERVICEDESK_LABOR | list | No | List of the labor performed by worker and when performed |
SERVICEDESK_WORKFLOW | list | No | List of all workflow on the service desk item |
SERVICEDESK_GLA | list | No | All G/L Accounts associated with this service desk item |
SERVICEDESK_CABLE | list | No | List of cable paths for the service desk item |
...
Type | Description | Extra Parameters* | Searchable | Results | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
CONTACTS | Retrieve available Contacts | CTYPE - Type of contact. Example: "worker" | yes | Contacts
| |||||||||||
DEPTHIER | Retrieve available Departments | Coming Soon | Department Hierarchy
| ||||||||||||
EQP_CATALOG | Retrieve available Equipment Catalogs | yes | Equipment Catalog
| ||||||||||||
CHARGE_CATALOG | Retrieve available Charge Catalogs | yes | Charge Catalog
| ||||||||||||
PRCODE | Retrieve available Problem Codes | no | Problem Code
| ||||||||||||
RESCODE | Retrieve available Resolution Codes | no | Resolution Code
| ||||||||||||
CSRS | Retrieve available Customer Service Representatives (CSR) | no | CSR
| ||||||||||||
SD_STATUS | Retrieve available Service Desk Statuses | no | SD Status
| ||||||||||||
SDTYPES | Retrieve available Service Desk Types (Some may not be currently valid for creating or updating SD records via the API) | no | SD Types
| ||||||||||||
UDFS | Retrieve available User Defined Fields (UDF) | SDTYPE - Retrieve UDFs for only a specific SD Type | no | UDF
| |||||||||||
WORKGROUPS | Retrieve available Workgroups | no | Workgroups
| ||||||||||||
LABOR_TYPE | Retrieve available Labor Types | no | Labor Types
| ||||||||||||
SD_CHRG_ACTION | Retrieve available Service Desk Charge Actions | no | SD Charge Actions
| ||||||||||||
URGENCY | Retrieve available Service Desk Urgency values | no | SD Urgency
| ||||||||||||
AUTH_CODE_TYPE | Retrieve available Auth Code Types | no | SD Auth Code
| ||||||||||||
BANDWIDTH | Retrieve available Bandwidth values | no | SD Bandwidth
|
Extra Parameters can be appended to the URL in standard Query String fashion.
Write Call
Excerpt |
---|
Note: The List Calls are used to locate the proper List Recid value that needs to be passed in the Endpoint Call. Details for the Call can be found in the Options section of the Available Fields for the various API Call Types. |
Available Fields
Field | Required | Data Type | Options | Default | Notes | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
recid | Only when updating | Integer | Identifier of the record to be updated | ||||||||||||||
due_date | No | String | The date when the Service Desk item is due. | ||||||||||||||
type | Yes | String | "SO" - Service Order | Service desk type | |||||||||||||
source | No | String | Lists
| "API" | Code for the source of the Service Desk Item. List Type must be SD_SOURCE. | ||||||||||||
urgency | No | String | Lists
| Set the urgency on the Service Desk Item. | |||||||||||||
csr | Yes | Integer | Lists
| The customer service representative assigned to the Service Desk item. The Record ID of the Service Rep to be assigned is a required field. | |||||||||||||
owner | No* | Integer | Lists
| Record ID of either the Contact or the Department owner. | |||||||||||||
owner_type | No* | String | "contact" or "department" | Type of owner. | |||||||||||||
requestor | No | Integer | Lists
| Record ID for the name of the person (contact) who is requesting the Service Desk item. | |||||||||||||
description | No | String | A description of the service desk item | ||||||||||||||
assoc_proj | No | Integer | Record ID of the project or problem associated with the service desk item. | ||||||||||||||
remarks | No | String | Service Desk remarks. These remarks show up on the "Activity/Remarks" tab of Service Desk. | ||||||||||||||
udf_IDENTIFIER | No | mixed | IDENTIFIER of UDF preceded by “udf_”. Example: udf_FIELD123 | ||||||||||||||
udf_UDF-RECID | Yes* | Integer | UDF-RECID is the RECID of the UDF to assign the value to. Example: udf_684=value
| ||||||||||||||
udf_UDF-IDENTIFIER | Yes* | Mixed | Lists
| IDENTIFIER is the unique Identifier of the UDF to assign the value to. Example: udf_LEGACYNUM=value
|
...
Key | Value |
---|---|
Content-Type | application/json |
Pcr-Html-Encoded | TRUE |
Body:
Key | Value |
---|---|
recid | 143658 |
type | SO |
csr | 1 |
Results
If the request is successful, the SD Number will be returns as follows:
Toggle cloak |
---|
...
Field | Required | Data Type | Options | Default | Notes | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
prob_code | noyes | Integer | Lists
| Record ID of the trouble code.problem | |||||||||||||
owner | noyes | String | The details or description of the trouble | res_Integer | Lists
| Record ID of either the Contact or the Department owner. | |||||||||||
owner_type | yes | String | "contact" or "department" | Type of owner. | |||||||||||||
problem | no | String | The details or description of the trouble | ||||||||||||||
res_code | no | Integer | Lists
| Record ID of the Resolution Code. | |||||||||||||
resolution | no | String | The details or description of the Resolution | ||||||||||||||
service | no | Integer | Record ID for the Service with the trouble | ||||||||||||||
equipment | no | Integer | Record ID for the Equipment with the trouble |
...
Key | Value |
---|---|
Content-Type | application/json |
Pcr-Html-Encoded | TRUE |
Body:
Key | Value |
---|---|
recid | 267870 |
prob_code | 4 |
owner | 1 |
owner_type | "contact" |
type | IN |
csr | 1 |
Results
If the request is successful, the SD Number will be returns as follows:
Toggle cloak |
---|
...
Key | Value |
---|---|
Content-Type | application/json |
Pcr-Html-Encoded | TRUE |
Body:
Key | Value |
---|---|
recid | 355989 |
type | ES |
csr | 1 |
Results
If the request is successful, the SD Number will be returns as follows:
Toggle cloak |
---|
...
Key | Value |
---|---|
Content-Type | application/json |
Pcr-Html-Encoded | TRUE |
Body:
Key | Value |
---|---|
sd_recid | 5434 |
type | SO |
udf_IDENTIFIER | 1 |
Results
If the request is successful, the RECID(s) of the new Service Desk UDF records will be returned in the same order as provided:
Toggle cloak |
---|
...
If the supplied API key has write privileges to write Service Desk Remarks, it is easy to insert Remarks for the new or existing Service Desk Item. On the write request just add remarks=value
to the query, where value is a text string.
A separate request can also be made.
- "curl" indicates the program you're trying to use.
- -X POST tells curl you want to make a POST request (change POST to GET to make a GET request, etc)
- --data "…" is a query string of parameters to send as the POST data. i.e. "foo=bar&bat=baz&etc=123" and so on.
- the URL to request. Notice at the end is "json". This is the format you want the response returned in. "json", "php" and "xml" are your available options.
Available Fields
Field | Required | Data Type | Options | Default | Notes |
---|---|---|---|---|---|
type | yes | String | type must be REMARKS | ||
sd_recid | yes | intInteger | The RECID Recid of the Service Desk item to add the remark toItem | ||
remarks | yes | stringString | The remarks to saveremark to add to the service | ||
sda_recid | no | Integer | Recid of the Service Desk Action. *Conditionally Required for use on a Service Desk Action. |
Request Example
Call:
Code Block | ||
---|---|---|
| ||
POST DOMAIN/KEY/servicedesk.json |
...
Key | Value |
---|---|
Content-Type | application/json |
Pcr-Html-Encoded | TRUE |
Body:
Key | Value |
---|---|
sd_recid | 999 |
type | SOREMARK |
remarks | This is a Remark from the API |
Results
If the request is successful, the SD Number will be returns as follows:
Toggle cloak |
---|
...
Key | Value |
---|---|
Content-Type | application/json |
Pcr-Html-Encoded | TRUE |
Body:
Key | Value |
---|---|
estimate_recid | 56487 |
charge_catalog | 1 |
type | EST_CHARGES |
Results
If the request is successful, the RECID of the new service desk estimate charge is returned as follows:
Toggle cloak |
---|
...
Key | Value |
---|---|
Content-Type | application/json |
Pcr-Html-Encoded | TRUE |
Body:
Key | Value |
---|---|
estimate_recid | 55073 |
labor_type | Regular |
workgroup | 1 |
hours | 1h 45m |
type | EST_CHARGES |
Results
If the request is successful, the RECID of the new service desk estimate labor record is returned as follows:
Toggle cloak |
---|
...
Key | Value |
---|---|
Content-Type | application/json |
Pcr-Html-Encoded | TRUE |
Body:
Key | Value |
---|---|
estimate_recid | 78451 |
eqp_catalog | 1 |
eqp_quantity | 1 |
eqp_billable | 1 |
type | EST_CHARGES |
Results
If the request is successful, the RECID of the new service desk estimate equipment record is returned as follows:
Toggle cloak |
---|
...
Key | Value |
---|---|
Content-Type | application/json |
Pcr-Html-Encoded | TRUE |
Body:
Key | Value |
---|---|
sd_recid | 78451 |
gla | 1 |
gla_type | Default |
gla_percent | 100 |
type | GLA |
Results
If the request is successful, the RECID of the new service desk GLA record is returned as follows:
Toggle cloak |
---|
...
Below is the proper format for making a separate request.
Note: "type=EQUIPMENT" to indicate that this is to create an Equipment record.
...
Field | Required | Data Type | Options | Default | Notes |
---|---|---|---|---|---|
type | yes | String | type=EQUIPMENT is Required | ||
sd_recid | yes* | Integer | The RECID of the Service Desk item that the Equipment is for. | ||
sd_number | yes* | String | The Number of the Service Desk item that the Equipment is for. | ||
equipment | no | Integer | RECID for the Equipment to be added. Used only for Cabling and Asset type Equipment. | ||
equipment _id | no* | Integer | Equipment ID for the Equipment. Conditionally Required for Cabling type Equipment. | ||
to_location | no | Integer | RECID of the Location the Equipment will be moved to. | ||
from_location | no | Integer | RECID of the Location the Equipment will be moved from. | ||
qty | yes | Integer | Quantity of the Equipment to be added | ||
billable | no | Integer | 1 or 0 | defaulted to Catalog setting | Mark whether the Equipment item is Billable. |
sda_recid | no* | Integer | The RECID of the Action on the Service Desk item the Equipment is for. | ||
sda_number | no* | String | The Service Desk Action Number. | ||
asset_tag | no* | String | The Asset Tag for the Equipment. Conditionally Required for Asset type Equipment. | ||
override_gla | no | Integer | RECID of the GLA to override billing for this Equipment. | ||
eqp_catalog | no* | Integer | Equipment Catalog RECID *Required if not Cabling or Asset equipment |
...
Key | Value |
---|---|
Content-Type | application/json |
Pcr-Html-Encoded | TRUE |
Body:
Key | Value |
---|---|
sd_recid | 78451 |
qty | 1 |
type | EQUIPMENT |
eqp_catalog | 1 |
Results
If the request is successful, the RECID of the new Service Desk Add Equipment record is returned as follows:
Toggle cloak |
---|
...
Below is the proper format for making a separate request.
Note: "type=LABOR" to indicate that this is to create an Equipment record.
...
Key | Value |
---|---|
Content-Type | application/json |
Pcr-Html-Encoded | TRUE |
Body:
Key | Value |
---|---|
type | LABOR |
sd_recid | 66116 |
labor_type | Regular |
date | 2019/04/25 |
hours | 1.25 |
workgroup | 1 |
worker | 1 |
billable | 0 |
Results
If the request is successful, the RECID of the new Service Desk Add Labor record is returned as follows:
Toggle cloak |
---|
...