Overview

The following table provides an overview of the integration points that are available for exchanging data with Oracle Insurance Gateway:

The list is sorted on alphabetical order.

Click the triangle in front of the name of the integration point to reveal available operations. Click the name of the integration point to go to the description page of the integration point.

Access Tokens

POST	/accesstokens/accesstoken retrieves an OAuth2 access token.
POST	/accesstokens/newaccesstoken retrieves a new OAuth2 access token.
POST	/accesstokens/anticsrftoken retrieves an anticsrf token.

Agents

GET	/agent downloads an Agent jar file
GET	/agent/{version} checks if given Agent version matches the version of Gateway’s Agent jar file.

Base Views

POST	/baseviews generates the base views.
POST	/{viewname}/regenerate regenerates the base view with given view name.
DELETE	/{viewname} drops the base view with the given view name.

Credentials

GET	/credentials retrieves an overview of the REST clients
GET	/credentials/{code} retrieves the credential with this code.
PUT	/credentials/{code} creates or updates the credential with this code.
DELETE	/credentials/{code} removes the credentials for the credential key with this code.
GET	/credential/export extracts a JSON file with credentials stored in secret.
POST	/credetials/import uploads a JSON file with credentials to an application.

Data Sets

POST	/import/datasetdefinition/{datasetDefinitionCode}/dataset/{dataSetCode} starts the data exchange import process.
POST	/import/datasetdefinition/{datasetDefinitionCode} starts the data exchange import process.
GET	/export/datasetdefinition/{datasetDefinitionCode}/dataset/{dataSetCode} retrieves the data set content.
POST	/export/datasetdefinition/{datasetDefinitionCode}/dataset/{dataSetCode} starts the data exchange export process.
POST	/createandexport/datasetdefinition/{datasetDefinitionCode}/dataset starts the full config migration and export process.
PATCH	/dataset/{id} updates the selected config migration set based on operation.
PUT	/datasetdefinition/{datasetDefinitionCode}/dataset creates or updates the config migration and export process.

Data File Sets

GET	/datafilesets gets defined data file sets in the system.
POST	/datafilesets creates the data file set with dat files.
PUT	/datafilesets updates the data file set with dat files.
POST	/datafilesets#multipart creates the data file set and uploads the zip file to it.
GET	/datafilesets/{datafilesetcode} retrieves the data file set.
POST	/datafilesets/{datafilesetcode} adds the data file to the data file set.
DELETE	/datafilesets/{datafilesetcode} deletes the data file set.
GET	/datafilesets/{datafilesetcode}/zip retrieves the zip file of the data file set.
POST	/datafilesets/{datafilesetcode}/zip adds the zip file to the data file set.
PUT	/datafilesets/{datafilesetcode}/zip zips the contents of all data files in the data file set.
PUT	/datafilesets/{datafilesetcode}/unzip unzips the contents of all data files in the data file set.
PUT	/datafilesets/{datafilesetcode}/datafiles updates the data file in the data file set.
DELETE	/datafilesets/{datafilesetcode}/datafiles/{datafilecode} deletes the data file from the data file set.
GET	/datafilesets/{datafilesetcode}/datafiles/{datafilecode}/data retrieves the data file content.
POST	/datafilesets/{datafilesetcode}/datafiles/{datafilecode}/data adds the data file content.

---

The generic datafilesets API supports, in addition to the standard generic API operations, the GET and the PATCH operation on /generic/datafilesets/key/{key}. This enables retrieving and updating a datafileset based on its datafileset code.

Dynamic Logic

Invalidate Dynamic Logic
POST	/dynamiclogic/invalidateall invalidates all dynamic logic.
Test Dynamic Logic
POST	/testdynamiclogic/{dynamicLogicCode} executes the dynamic logic of signature Test Unit.

Eclipse

PUT	/eclipse/activate submits a request to activate the eclipse module.
GET	/eclipse/expirytimes gets the device expiry and key expiry for the eclipse module.
GET	/eclipse/pingagency request to ping agency.
GET	/eclipse/healthcheck check whether the eclipse module is activated or not.

Exchanges

POST	/exchanges/{\type}/{code} submits an integration with post parameters or a raw payload.
GET	/exchanges/{type}/{code} submits an integration with query parameters.
POST	/exchanges/{type}/{code}/withParameters submits an integration with parameters key/value pair that can be user defined
POST	/exchanges/{id}/signoff signs off the exchange. Mark the exchange as Completed.
POST	/exchanges/{id}/failure reports failure for the exchange. Mark the exchange as Failed.
POST	/exchanges/{id}/recover recovers a failed exchange. Marks the exchange as Started and resumes from the last failed step.

Events

POST	/events/{eventType} stores an event in the event store.
PUT	/events/{eventType} stores an event in the event store.

Integrations

GET	/integrations/{type}/{code}/validate requests on-line validation of the configuration of an integration with a max duration in seconds.

Key Stores

POST	/keystores creates a keystore.
GET	/keystores retrieves a keystore.
DELETE	/keystores/{keystorename} deletes the keystore.
GET	/keystores/{keystorename}/keys retrieves the list of keys that are configured for the given keystore.
POST	/keystores/{keystorename}/keys creates a private and public key pair.
GET	/keystores/{keystorename}/keys/{alias} retrieves the PEM string representation of the public key certificate.
DELETE	/keystores/{keystorename}/keys/{alias} deletes a key pair form the key store.
POST	/keystores/{keystorename}/keys/{alias} imports a new certificate.
GET	/keystores/export extracts a JSON file with keystores stored in secret.
POST	/keystores/import uploads a JSON file with keystore to an application.

Non-Entity Cache

POST

/nonentitycache/invalidateall invalidates and re-populates no-entity caches, such as Flex Code System Setup, Dynamic Field Setup, Field Details Setup, Dynamic Record Setup. Since these no-entities are cached during application startup, this is important for scenarios where there is a mismatch between the data in the Database and in the cache.

Notifications

POST	/notifications submits a notification to resume a notification based on correlation id.
PUT	/notifications submits a notification to resume a notification based on correlation id.
POST	/notifications/custom submits a notification to resume a notification based on correlation id. The schema is in a custom format.
PUT	/notifications/custom submits a notification to resume a notification based on correlation id. The schema is in a custom format.

OAuth2 Client Configuration

PUT	/{id}/setclientsecret cerates or updates the client secret.

Objects

GET	/objects/generate returns the object skeleton file.

Outbound Integration Point

GET	/outboundintegrationpoints retrieves all endpoints an Oracle Health Insurance application sends messages to. This IP is a runtime catalogue that shows all outbound integration points, their endpoints and the endpoint characteristics.

Properties

Properties The generic properties API supports, the standard generic API operations on properties.
Property definitions
GET	/properydefinitions/{propertyName} retrieves an overview of the Oracle Health Insurance system property definitions. Query parameters are: ** ?name=<prefix> (optional) Returning only the system property definitions that have their name starting with the given prefix.
GET	/properydefinitions/{propertyName} resource retrieves the system property definition with the given property name.
Current Properties
GET	/currentproperties retrieves all the properties currently set to value Query parameters are: ** ?name=<prefix> (optional) Returning only the properties that have their name starting with the given prefix.
GET	/currentproperties/{propertyName} retrieves the property with the given propertyName.

Task Processing

GET	/tasksprocessing returns the status and statistics of the queue.
POST	/taskprocessing starts or stops the task queue.
GET	/tasksprocessing/{id}/restart restarts the task with this id.

---

The /generic/tasks API supports only search and retrieval operations.

Purge

POST	/purge/events requests the purge of events.
GET	/purge/events/{id} fetch the purge event resource by id.
POST	/purge/technicaldata requests the purge of technical data.
GET	/purge/technicaldata/{id} fetch the purge technical data resource by id.
POST	/purge/exchanges requests the purge of exchanges.
GET	/purge/exchanges/{id} fetch the purge exchange resource by id.

User Information

GET	/userinformation retrieves the userinformation of the logged in user.
PUT	/userinformation/userpreference updates a user’s preferences.

User Provisioning

PUT	/users creates or updates a user.
GET	/users/{loginName} retrieves the user.
DELETE	/users/{loginName} deletes the user.

The generic /users API supports only search and retrieval operations.