ConnectIT 365
REST Endpoint (Import)
If the REST connection in the other system is confgured, no other configuration is needed on the import definition card. On the import definition card there is information available for the REST Connection. For Authentication see also: Authentication with OAuth 2.0
It is possible to set up and import definition that will serve as a POST, PUT and DELETE endpoint, to be used by external systems.
The external party will have to do a POST, PUT or DELETE call to https://***/api/v2/WebServices, using the following headers:
*** this part is in the defintion card and depending on the API in the general settings
Key | Value |
|---|---|
Tenant (3) | See image below |
Environment (3) | See image below |
Company | See image below |
Id | Definition No. of the import definition |
Content-Type | application/json (1) |
Base-URL (2) | The Base URL for webservices |
Accept | application/json or application/xml or text/xml |
It is only possible to post a JSON body. XML input is not supported.
Base-URL should not be provided for Microsoft SAAS tenants.
Should not be provided for OnPrem installations.
Processing
Asynchroon processing
If this setting is turned on, the data will first be imported in the queue whitin ConnectIT and will be processed from there tot the specific table. If this setting is turned of, the data will directly be insert in the table, whitout using the queue.
Delete Allowed
To prevent external parties from deleting content, it is possible to set the definition to not allow DELETE actions. Keep in mind that when delete actions are allowed, external parties that can authorize of your endpoint can delete all records.
To create new records, the external party should perform a POST action. To change an existing record, PUT should be used.
The JSON body in the request should represent the JSON definition lines to be able to process the content.