Import API

The Import API makes it possible to create or update records in batches. The behavior of this API is similar to the Import functionality as exposed via the GUI.

Importing records in batches through the API is the preferred way of building (one-way) integrations with discovery tools and directory services . It allows for easily managed integrations and performs better compared to sending separate create/update REST API calls for each record.

This page is organized as follows:

Generating an import file
Uploading an import file
Polling for the import progress
Viewing the import log

Generating an Import File

Data can be imported into R-Service using UTF-8 or UTF-16LE encoded comma-separated values (CSV) or tab-separated values (TSV) files.

Each record in a CSV or TSV import file needs to be defined on a separate line. Each line of text is essentially a row of a spreadsheet. The first line of text is reserved for the column headers.

Each column header references a field of the record type. Not all column headers are required. If a column for a field is left out of an import file, it will cause the corresponding field to be set to its default value (usually this means that it is left empty) when the import causes new records to be generated. For existing records a missing column means that the corresponding field value will not be updated during the import.

Each type of import file is described in a separate page within this section of the R-Service Developer documentation. An example CSV file can be downloaded from each of these pages, so there is an example available for each type of import file.

Detailed information concerning the formatting of the values within the columns of an import file can be found in the Data Types section. Use the Enumerations API to obtain a complete and up-to-date overview of all the values that can be selected in the fields that offer a fixed list of options (i.e. enumerations).

When in doubt, it is always possible to register a record with specific field values and relations to construct an example of what needs to be imported. Once that is done, an export can be performed. The export file will then contain the example with the values that need to be entered in the columns of an import file.

Create or Update?

As stated above, each line in an import file represents one record in R-Service. If the record already exists in R-Service, it will get updated during the import. If the record does not yet exist, a new record will be created. The following steps are taken to determine whether a record already exists:

Each record in R-Service is assigned a unique ID . If the ID column is present in the import file and a value is specified for a specific row, then R-Service will try to find the existing record using this identifier.
If the ID column is not present or if its value is empty for a specific row, and the Source and Source ID columns are present and have a value, then these two values are used to find an existing record. If an existing record with this Source / Source ID combination is found, it will get updated. Alternatively, if such a record does not yet exist, then a new record will be generated. This new record will get the Source and Source ID values specified in the import file.

As the Source and Source ID values are known by the external tool, this second step makes it easy for this external tool to fill out these values correctly. It eliminates the need for the external tool to know the IDs of the records it maintains in R-Service. 3. For some import types a special column is also accepted as a unique identifier:

* `organizations_contact_details`
 :
 *Organization*
 \- the organization’s name
* `people`
 :
 *Primary Email*
 \- the person’s email address
* `people_contact_details`
 :
 *Person*
 \- the person’s email address

This step was introduced to enable updates of previously created Organization and Person records without first having to contact R-Service to find their ID .

Relating to Another Record

R-Service records often have links to other R-Service records. Each Person record, for example, can be related to a Site record. To indicate that a record has a link with another record, a unique value of the related record needs to be specified. This unique value is the Name field (which is unique within the account to which the record belongs) for the following records types:

So, to indicate that a Person record is to be related to a specific Site, use the name of this Site to establish the link.

The name of a Person record, however, should not be used to relate a record to a Person record. That is because the name of a Person record does not need to be unique within the account to which it belongs. The primary email address of the Person should therefore be used to establish links with Person records.

Configuration items (CIs) are also special. Software versions have a unique name within the account to which they belong, so the name of software versions should be used to establish links. The name of software license certificates and other CIs do not need to be unique. Such CIs have a Label field, which value must be unique within the account. Hence, the label of such CI records can be used to link them to other records.

To relate a product category to a CI, the product category’s reference should be used. The reference of a product category is unique within the account.

To relate a custom collection element to a custom collection, the custom collection’s reference should be used. The reference of a custom collection is unique within the account.

The records of the types listed below have an ID that is unique within the account to which they belong. Use this ID to establish links with such records.

Relating to Multiple Other Records

Some records can be related to multiple records of the same record type. For example, multiple Person records can be related as members to a Team record. To relate multiple Person records as members to a Team record, ensure that the primary email addresses of the members are separated by a line break. In addition, a double quote must be placed before the primary email address of the first member and a double quote must be placed after the primary email address of the last member of the Team.

Example:

"frank.watson@widget.com
grace.weller@widget.com
rodney.wilson@widget.com
thomas.wicker@widget.com
tom.waters@widget.com"

Note that if you are preparing an import file using a spreadsheet, then you only need to ensure that each reference to a record is placed on a separate line within the cell of the spreadsheet. The spreadsheet application should automatically ensure that the double quotes are correctly added when you save the file as a comma-separated values (CSV) file or tab-separated values (TSV) file.

Relating to Different Accounts

When a trust relation has been established between two R-Service accounts, it is possible for certain records of these accounts to be linked together. For example, Widget Data Center may be providing their Expense Reporting service to the Widget North America organization. After these organizations have established a trust relation between their accounts, Widget Data Center is able to register a Service Level Agreement and relate an Organization record of Widget North America to it as its customer. If the id of Widget North America’s account is “wna”, then Widget Data Center is able to define the link between the SLA record and the customer’s Organization record by placing the @ symbol between the customer’s record name and the id of the customer’s account.

This will then look as follows:

Widget North America @wna

Uploading an Import File

The upload of a CSV or TSV file is done using the following API call:

$ curl -H "Authorization: Bearer <oauth-token>" \
       -H "account: dc" \
       -X POST \
       -F type=people -F file=@/tmp/people.csv \
       https://api.r-service.tech/v1/import

The response from the Import API is a token that acts as the unique identifier for the import job. This token can be used to retrieve information about the progress of the import job.

Status: 200 OK

{
  "token": "68ef5ef0f64c012f2...e4598cdb41e68"
}

It is important to note that the API user needs to have the Account Administrator role to be able to import files using the API. In the example above, the API user specifically needs to have the Account Administrator role of the account which id is “dc”. The Authentication section describes how the api-token of the API user can be found.

In the example above it would not be necessary to specify -H "account: dc" provided that the Person record of the API user is registered in the account which id is “dc”.

Parameters

The following parameters are supported:

file

Required file — The UTF-8 encoded CSV or TSV file to import as multi-part form-data.

Required enum — The type of the file to import. Valid values, in a specific order , are:

Click on any link above to view more detailed information on the format of the import file for the given type.

Import order

It is not possible to establish a link with a record that does not yet exist in the R-Service database. If you are using import files to populate a new R-Service account, it is therefore important that the records are imported in a specific order. It is important, for example, that the Person records are loaded before an import of the Team records is performed. That allows each Team record to be linked to a coordinator, a manager, a configuration manager and several members during the import of the Team records.

The correct order is outlined by the type parameter above.

Import progress

The import process runs as a background job. Once the import job has been completed, the API user receives an email with a summary of the results.

In addition to these automated email notifications, it is also possible to check the progress of an import job automatically using the token received from the import response.

A common use case is to make sure that a People import has been completed before their contact details are uploaded, or that the Configuration Items are imported before their relations are uploaded. This is achieved by polling for the import progress every minute until state = done is returned.

Five minutes after the job is completed, the progress information is not available anymore through the API.

Example:

$ curl -H "Authorization: Bearer <oauth-token>" \
       -H "account: dc" \
       -X GET \
       https://api.r-service.tech/v1/import/68ef5ef0f64c012f2...e4598cdb41e68

Depending on the state of the import job, one of the following responses is returned:

Queued

Status: 200 OK

{
  "state": "queued"
}

The job is scheduled for execution.

Processing

Status: 200 OK

{
  "state": "processing",
  "line": 990
}

The job is being processed and the line attribute shows how much progress has been made.

Done

Status: 200 OK

{
  "state": "done",
  "results": {
    "created": 50,
    "updated": 34,
    "deleted": 0,
    "unchanged": 7,
    "failures": 0,
    "errors": 0
  },
  "logfile": "https://itrp.amazonaws.com/imports/20170831/dc/101550712561.sites.log?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJ...quest&X-Amz-Date=20170831T101630Z&X-Amz-Expires=172800&X-Amz-SignedHeaders=host&X-Amz-Signature=efffc5a...76f3b"
}

The job is complete and the response includes meta information on the affected records. If both the failures and errors attributes are zero, the entire upload was successful. If not, more detailed information on the failed records can be found in the Import Log . The URL of the import log is included at the end of the response.

Note that if the import process was able to recover from an error, the state done is returned. The response contains the state error as outlined below only when an error prevents the import job from continuing with the next row.

Error

Status: 200 OK

{
  "state": "error",
  "message": "Invalid byte sequence in UTF-8 on line 15",
  "results": {
    "created": 5,
    "updated": 2,
    "deleted": 0,
    "unchanged": 7,
    "failures": 0,
    "errors": 1
  },
  "logfile": "https://itrp.amazonaws.com/imports/20170831/dc/101550712561.sites.log?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJ...quest&X-Amz-Date=20170831T101630Z&X-Amz-Expires=172800&X-Amz-SignedHeaders=host&X-Amz-Signature=efffc5a...76f3b"
}

The import was aborted prematurely because of an unrecoverable error. A short description of the issue is provided in the message attribute. More detailed information can be found in the Import Log . The URL of the import log is included at the end of the response. Errors should always be investigated.

The results hash contains non-zero values in case the import file was partially processed.

Not Found

Status: 404 Not Found

The job was completed more than 5 minutes ago, so no progress information is available anymore. Information on the completed job can still be found in the Import Log .

Import log

Each import job that is complete (with or without errors) is entered in the System Logs of the Settings console. Log into R-Service as an Account Administrator and go to Settings => System Logs and select the Import Log view to see them all.

The Level column will contain Fatal in case an error has occurred.