...
Page Properties | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
Resources & Remarks Modification History
|
As of Version | 2.4 |
---|---|
HTTP Method | POST |
Response Format | JSON |
Description | This Interceptor can be trigger by
A multipart request body is posted. It always contains a "data" part, that contains an object list with the metadata of the affected objects. On an import or content update it can contains further parts as with renditions. The majority of the metadata in the "data" part is still raw. That means it is not yet normalized, validated and system properties are not yet set. Only content properties are available in case of import or content update. For more details take a look at the examples below. If the regular import route should be continued, pass the multipart to http://registry/api/dms/objects. |
Requirements for external endpoint | The target URL must be a POST endpoint accepting a multipart request body and returning a list of objects. |
Affected API Requests | POST /api/dms/objects/{objectId} |
Restart Service | Repository service |
Header | Authorization-Header |
Predicate | The predicate is applied on all objects of the object list in the "data" part. If at least one object matches, the interceptor is called. |
Examples
Import with Content
...