You can mimic the import functionality you see in Operator by making your own import process for JSON files.
We'll assume you know how to upload files through the API and that you have access to a TempFile.ID or ClientFile.ID.
As JSON is a very flexible format, here is an example of the expected file content:
[
{
"name": "thing1",
"description": "This is a thing."
},
{
"name": "thing2",
"description": "This is another thing."
},
{
"name": "thing3",
"description": "This is yet another thing."
}
]interface IPostBody {
// Previously uploaded temp file ID or Client File ID.
// One of these is required.
"TempFile.ID": string;
// File name used for creating an import record.
// Eg: 'my-file.json'.
// If you specify a Client File ID, this is not needed as the name is already known.
"TempFile.Name": string;
"ClientFile.ID": string;
// Specifies how the features should be imported.
// Eg: 'A' for add, 'U' for update, 'R' for replace (delete before importing).
// You can also use 'U+A' to update or add (our default).
// Or 'U+A+D' to update or add, then delete any Entities not in the JSON.
// These are all relative to the specified Entity Type.
"ImportMode": "A" | "U" | "R" | "U+D" | "U+A" | "U+D+A";
// Set to true to skip features that fail to import.
// If false, the first failure will stop the import.
"SkipFailedFeatures"?: boolean;
// Destination Entity Type.
"EntityType.ID": string;
// Array of Nextspace Tag IDs to apply to all imported Entities.
"AddLayerIDs"?: number[];
// Data mapping for the JSON properties to the target Entity Type schema.
"DataMapping": any;
}interface IResponse {
"PendingActionID": number;
}When the Pending Action is marked as completed, here is the result to expect:
interface IResult {
// Number of failed to import features.
"CountFailed": number;
// Number of successfully imported features.
"CountImported": number;
}