SAP Open Connectors supports events via polling or webhooks depending on the API provider. For more information about our Events framework, see Events Overview.

Supported Events and Resources

SAP Open Connectors supports polling events for Orderful. After receiving an event, SAP Open Connectors standardizes the payload and sends an event to the configured callback URL of your authenticated connector instance.

You can set up polling for the transactions resource. You can also copy their configurations to poll other resources. 

Configure Polling Through the UI

To configure polling through the UI, follow the same steps to authenticate a connector instance, and then turn on events. Select the resources to poll, and then click Create Instance. For more information, see Authenticate an Connector Instance with Events (UI) or the connector-specific authentication topic.

Configure Polling Through API

Use the /instances endpoint to authenticate with Oracle HCM Cloud and create a connector instance with polling enabled.

To authenticate a connector instance with polling:

1. Construct a JSON body as shown below (see Parameters):

   {
     "element": {
       "key": "orderful"
     },
     "configuration": {
       "event.vendor.type": "polling",
       "event.poller.refresh_interval": "15",
       "event.notification.enabled": true,
       "event.poller.configuration": "{\"transactions\":{\"url\":\"/hubs/edi/transactions?where=dateFrom='${gmtDate:yyyy-MM-dd'T'HH:mm:ss.SSS'Z'}'\",\"idField\":\"id\",\"datesConfiguration\":{\"updatedDateField\":\"latestRevisionAt\",\"updatedDateFormat\":\"yyyy-MM-dd'T'HH:mm:ss.SSS'Z'\",\"updatedDateTimezone\":\"GMT\",\"createdDateField\":\"createdAt\",\"createdDateFormat\":\"yyyy-MM-dd'T'HH:mm:ss.SSS'Z'\",\"createdDateTimezone\":\"GMT\"}}}",
       "orderful.api.key": "ODiblY1Zok6MTrbcuvsEM49iIKkPPhD1qfb7kuJ8"
     },
     "name": "<INSTANCE_NAME>"
   }

2. Call the following, including the JSON body you constructed in the previous step:

   POST /instances
   

   Note: Make sure that you include the User and Organization keys in the header. For more information, see Authorization Headers, Organization Secret, and User Secret.

3. Locate the token and id in the response and save them for all future requests using the connector instance.

Example cURL with Polling

curl -X POST \
https://api.openconnectors.us2.ext.hana.ondemand.com/elements/api-v2/instances \
-H "authorization: User <USER_SECRET>, Organization <ORGANIZATION_SECRET>" \
-H "content-type: application/json" \
-d '{
  "element": {
  "key": "orderful"
},
"name": "xxxxxxxx",
"configuration": {
  "event.vendor.type": "polling",
  "event.poller.refresh_interval": "xxxx",
  "event.notification.enabled": true,
  "event.poller.configuration":"{\"transactions\":{\"url\":\"/hubs/edi/transactions?where=dateFrom>='${gmtDate:yyyy-MM-dd'T'HH:mm:ss.SSS'Z'}'\",\"idField\":\"id\",\"datesConfiguration\":{\"updatedDateField\":\"latestRevisionAt\",\"updatedDateFormat\":\"yyyy-MM-dd'T'HH:mm:ss.SSS'Z'\",\"updatedDateTimezone\":\"GMT\",\"createdDateField\":\"createdAt\",\"createdDateFormat\":\"yyyy-MM-dd'T'HH:mm:ss.SSS'Z'\",\"createdDateTimezone\":\"GMT\"}}}",
  "orderful.api.key": "xxxxxxxxxxxxxxxxxxxxxxx"
 }
}'

Parameters

API parameters not shown in SAP Open Connectors are in code formatting.