Last updated Sep 19, 2022

Rate this page:

Assets imports


Importing is a way to bring outside data into Assets and automatically convert it into Assets object types, objects, attributes and references. Currently, you can import data from CSV, JSON, and Assets Discovery. Each of these import types is called a module.

Assets can store and run multiple imports of different types. An import configuration is a package of information about where to find the data and how Assets will manage a specific import task. When you create a new import configuration, you have the option of creating a predefined structure and/or configuration for the objects that you create. A predefined structure and configuration is a default structure and configuration based upon the type of data you are importing, for example, a CSV, JSON, or Discovery file. You also have the option of creating an import configuration without a predefined structure and configuration - this means you would manually map your data into object types, objects, attributes, and references.

There are several ways to map data into Assets:

  • Use object type mapping to create object types.
  • Use object type attribute mapping to create attributes.
  • Use object type mapping with placeholders to create references.
  • Use child object type mapping to create parent and child hierarchies within your object schema.

To import information into Assets you’ll need to create an import configuration, map your data, and then execute the import.

For more information or to try out imports in Assets you can follow our documentation at

Types of imports

We can divide Assets import sources between file-based and external import sources.

File based imports

File based imports are performed manually by customers uploading a file with data to Assets and setting a mapping configuration to transform its contents into Assets objects.

The file types supported are:

  • Json
  • CSV
  • Discovery zip files

External imports

External imports are those where an external application or script pushes data to Assets directly, without the user having to handle a file upload manually.

The external application also handles the creation of an object schema and import mapping configuration.

Authentication and authorization for imports

While file based imports follow Assets' conventions regarding authorization, external imports authentication and authorization is handled entirely with OAuth tokens. Assets administrators will be able to obtain a token when they configure the import source in Assets' UI, and external applications or scripts can use it to call all the related APIs.

Rate this page: