Page Comparison

...

Status	What it means
200	The Request was received and executed successfully.
400	The Request was received, but contained Bad Data, so was not executed.
401	The Request was received, but your User permissions are not authorized to perform the requested operation.
403	The Request was received, but you lack the User permissions to perform the requested operation.
404	The Request was received, but the desired End Point was not found.
405	The Request was received, but you are not allow allowed to perform the requested operation.
503	This Response indicates PCR-360 is presently unavailable, and likely is in a Maintenance Window.

Configuring REST Headers

Depending on the desired formatting of the request, there are two headers that can be sent. Depending on the 'Access Mode' for a User's Requests, other headers may be required. Please see the API Permissions page for more details

...

The recommended method for reading data in the API is using the SQL REQUEST type. This allows you to specify a raw SQL query to the API and get back the results in the specified format. The SQL API request requires using the POST HTTP method.

Using cURL CURL this example queries all records in the SERVICES table and specifies the content type is JSON encoded and requests data returned JSON encoded:

...

This servicedesk REQUEST variant allows access to PCR-360 Service Desk items and related data. View full details on Service Desk API Calls.

Service Desk Actions

This REQUEST type is deprecated.

The servicedesk REQUEST type allows access to PCR-360 Service Desk items and related data. View full details on Service Desk Action API Calls.

Getting LIST Values

Excerpt

To retrieve LIST values from the API send a request structured as below:

Code Block

language	xml

https://url/endpoint.json?LIST=VALUE

All List Types will be returned from the Endpoint the request was sent to. The format is different depending on the LIST requested, but should look similar to the example below.

Code Block

language	xml

{
    "status": "success",
    "page": 1,
    "count": 11,
    "total_count": 3,
    "sd_action": [
        {
            "RECID": 237,
            "VALUE": "Add"
        },
        {
            "RECID": 238,
            "VALUE": "Change Types"
        },
        {
            "RECID": 239,
            "VALUE": "Add Locations"
        }
    ]
}

Writing Data

The PCR-360 API allows an outside application to create or update Service, Equipment, or Service Desk items or submit SNMP traps. The basic write request is much like a read request; the URL is built in a similar fashion. Like the read requests, all API write operations are done via an HTTP(s) request (using cURL or some other method). You will need to build the URL to describe the request you are making.

...

The cable REQUEST type allows writting writing PCR-360 Cables and related data. View full details on Cable API Calls.

...

The contact REQUEST type allows for adding and updating PCR-360 Contact Records and related data. View full details on Contact API Calls.

Custom

Custom API is available starting in version 2.1.4.0
The Custom REQUEST type allows the API to invoke custom PHP logic that is saved in the application. This is very useful when interfacing with an application where you cannot control the format or data in the outbound requests. The structure of a custom request type is dependent on the identifier specified in the Custom Logic > API entry. For more information on the syntax and capabilities available in the Custom Logic > API interface, see Custom Logic Syntax.

...

For troubleshooting API Requests, navigate to 'Admin > API > API Request Log' to view a record of all Requests made to the API and the Response. For more details, see the API Request Log page.

SNMP

Simple Network Management Protocol (SNMP) will capture events from network device(s). It is used for collecting information used on a form and configuring, network devices, such as servers, printers, hubs, switches, and routers. PCR-360 can listen for SNMP Events and set up automatic Notifications and Escalations according to the User or organizational needs. Currently PCR-360 supports both SNMPv1 and SNMPv2c. There is no support for SNMPv3 at this point in time. For more information see the SNMP page.

Child pages (Children Display)

sort	title

Versions Compared

Old Version 13

New Version Current

Key