Data integration with Edge Encryption
-
- UpdatedAug 1, 2024
- 2 minutes to read
- Xanadu
- Edge Encryption
Data integration with Edge Encryption
To integrate third-party data with an instance using Edge Encryption, you must route the data through the Edge Encryption proxy server using supported integrations. Supported integrations use base system encryption rules that map data in each payload to fields in a table.
Upload data to fields marked for encryption
Edge Encryption does not support importing data from or exporting data to Excel, CSV, XML, or other file types to or from fields with encryption configurations defined.
- ODBC driver
Encrypt requests and query data through the Edge Encryption proxy server using the ODBC driver.
Learn more: Edge Encryption ODBC driver integration
- MID Server
You can configure the MID Server to route data through an Edge Encryption proxy server. However, some restrictions apply.
Learn more: Edge Encryption MID Server integration
- REST/SOAP web services
Use REST/SOAP web services to update or retrieve record data through the Edge Encryption proxy server.
Learn more: Web services
- JSONv2 web service
Use JSONv2 web service APIs to update or retrieve record data through the Edge Encryption proxy server. Base system encryption rules support data retrieval and data modification APIs.
- To insert a single record using the data modification API, use the insert() or insertMutiple() methods.
- To insert multiple records using the data modification API, use the insertMultiple() method.
Learn more: JSONv2 Web Service
To encrypt data from custom third-party integrations not listed above, create custom encryption rules. See Define a custom encryption rule.
Upload attachments to records marked for encryption
Attachments can be uploaded to tables with attachment encryption configured using REST and SOAP web services.