Supported APIs

The following sections list the supported APIs.

POST api/connector/SubmitRecords

Submit records to AvePoint Opus. You need to download the JSON file of each connection from Settings > Connector to prepare the record information. You can only submit up to 15 records at a time.

Example

{ "id": " ",
"confilictOption": "Overwrite",
"data": [
    {
    "rowKey": "SingleText",
    "leafName": "SingleText",
    "termFullPath": "Taxonomy",
    "timeCreated": "DateTime",
    "timeModified": "DateTime",
    "createdBy": "SingleText",
    "modifiedBy": "SingleText",
    "_Multiple_%20_Text_%20_Column": "MultipleText",
    "_DateTime_%20_Column": "DateTime",
    "_Single_%20_Choice_%20_Column": "SingleChoice",
    "_Multiple_%20_Choice_%20_Column": "MultipleChoice",
    "_People_%20_or_%20_Group_%20_Column": "PeopleOrGroup",
    "_Number_%20_Column": "Number"
    }     
    ] 
    }

Request Information

ElementDescriptionTypeRequired
idThe ID of the connection.GUIDYes
conflictOptionThe conflict resolution when there are records with the same unique key.Valid values are:Overwrite to overwrite the record information in AvePoint Opus.Skip to skip submitting the record to AvePoint Opus.StringYes
rowKeyThe unique key of the record.StringYes
leafNameThe internal name of the built-in Name column in the connection.StringYes
termFullPathThe internal name of the built-in Classification column in the connection.The value must be the full path of a term in AvePoint Opus.StringNo
timeCreatedThe internal name of the built-in Created time column in the connection.The format of the value must follow the date and time format configured in Settings > General settings.StringYes
timeModifiedThe internal name of the built-in Modified time column in the connection.StringYes
createdByThe internal name of the built-in Created by column in the connection.StringNo
modifiedByThe internal name of the built-in Modified by column in the connection.StringNo

AvePoint Opus supports creating custom columns of different types to meet your requirements for variable record properties. When submitting records with custom columns, enter the internal name of each custom column you have defined in the connection. Values of custom columns are optional. For details, refer to Create a Connection.

  • For the Single line of text type of column, value should be a single line of text.

  • For the Multiple lines of text type of column, value should be multiple lines of text.

  • For the Date and Time type of column, value should be a date and/or time.

  • For the Choice (single selection) type of column, value should be the numerical order of the correct option, not the option name.

  • For the Choice (multiple selections) type of column, value should be the numerical orders of the correct options separated by commas in square brackets.

  • For the Person or Group type of column, value should be the full email address of users and/or groups separated by commas in square brackets. If the user or group does not exist in AvePoint Opus, AvePoint Opus will query it in the Microsoft Entra that is authorized via the app profile in AvePoint Online Services.

  • For the Number type of column, value should be a number.

Response Information

ElementDescriptionType
MessageThe request details.String
FailedItemsIf some records failed to be submitted to AvePoint Opus, this parameter would appear, displaying the records failed in the request.The value contains:Item is the information of the item that failed in the request.Message is the details about the failure.Array (Object)

POST api/connector/GetDueRecords

Retrieve the records whose disposed due date is earlier than the specified time.

Example

{id: " ",
disposalDueDate: 2024-04-01 00:59:34,
startIndex: "",
itemsPerPage: 15}

Request Information

ElementDescriptionTypeRequired
idThe ID of the connection.GUIDYes
disposalDueDateThe disposal due date.The format of the value must follow the date and time format configured in AvePoint Opus > Settings > General settings.StringYes
startIndexThe page index of the last request.StringNo
itemsPerPageThe number of records that you want to request on one page.The valid value is a number between 0 and 100.IntYes

Response Information

ElementDescriptionType
messageThe details about the action.String
pageIndexThe page index of the records that are queried in the request.String
queriedItemsThe records that match the request information.Array

POST api/connector/DisposeRecords

Update the status of records as Destroyed in AvePoint Opus. You can only update the status for up to 15 records at a time. If manual approval is enabled, after record reviewers approve or reject the records, you can use this API to update the status of the approved records as Destroyed in AvePoint Opus.

Example

{disposalIds: ["Item RowKey1","Item RowKey2"]}

Request Information

ElementDescriptionTypeRequired
Item RowKeyThe unique ID of the record that you want to update as Destroyed in AvePoint Opus.StringYes

Response Information

ElementDescriptionType
messageThe request details.String
failedItemsThe items that failed in the request.Array (["Row Key1", "Row Key2"])