Events

Cloud Elements supports events via polling or webhooks depending on the API provider. If you would like to see more information on our Events framework, please see the Event Management Guide.

Supported Events and Resources

Cloud Elements supports polling events for Clover. After receiving an event, Cloud Elements standardizes the payload and sends an event to the configured callback URL of your authenticated element instance.

You can set up events for the following resources:

• timesheets
• employees
• payments
• roles

Polling

You can configure polling through the UI or in the JSON body of the /instances API request .

Configure Polling Through the UI

For more information about each field described here, see Parameters.

To authenticate an element instance with polling:

1. Enter the basic information required to authenticate an element instance as described in Authenticate with Clover .
2. Enable events: Switch Events Enabled on.
3. Add an Event Notification Callback URL.
4. Use the Event poller refresh interval (mins) slider or enter a number in minutes to specify how often Cloud Elements should poll for changes.
5. Select the resources to poll.
6. Advanced users can further configure polling:
   • Click to edit the polling configuration JSON directly.
   • Click to access the poller configuration.
7. Optionally type or select one or more Element Instance Tags to add to the authenticated element instance.
8. Click Create Instance.
9. Log in to Clover, and then allow the connection.

After successfully authenticating, we give you several options for next steps. Make requests using the API docs associated with the instance, map the instance to a virtual data resource, or use it in a formula template.

Configure Polling Through API

Use the /instances endpoint to authenticate with Clover and create an element instance with polling enabled.

To authenticate an element instance with polling:

1. Get an authorization grant code by completing the steps in Getting a redirect URL and Authenticating users and receiving the authorization grant code.

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

   {
     "element":{
       "key":"clover"
     },
     "providerData":{
       "code": "<AUTHORIZATION_GRANT_CODE>"
     },
     "configuration":{
       "oauth.api.key": "<Clover app Key Name>",
       "oauth.api.secret": "<Clover app Secret Name>",
       "oauth.callback.url": "<Clover app Callback URL Name >",
       "clover.sandbox": "<true or false>",
       "merchantId": "<Clover app Merchant ID>",
       "event.notification.enabled": true,
       "event.notification.callback.url": "http://mycoolapp.com",
       "event.poller.refresh_interval": "<minutes>",
       "event.poller.configuration":{
       "timesheets": {
         "url": "/hubs/employee/timesheets?where=out_and_override_time >'${date:yyyy-MM-dd'T'HH:mm:ssXXX}'",
         "idField": "id"
       },
       "employees": {
         "url": "/hubs/employee/employees?where=modifiedTime>'${gmtDate:yyyy-MM-dd'T'HH:mm:ssXXX}'",
         "idField": "id"
       },
       "payments": {
         "url": "/hubs/employee/payments?where=modifiedTime>'${gmtDate:yyyy-MM-dd'T'HH:mm:ssXXX}'",
         "idField": "id"
       },
       "roles": {
         "url": "/hubs/employee/roles?where=modifiedTime>'${gmtDate:yyyy-MM-dd'T'HH:mm:ssXXX}'",
         "idField": "id"
       }
     }
     },
     "tags":[
       "<Add_Your_Tag>"
     ],
     "name":"<INSTANCE_NAME>"
   }
   

3. 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. See the Overview for details.

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

Example cURL with Polling

curl -X POST \
https://api.cloud-elements.com/elements/api-v2/instances \
-H 'authorization: User <USER_SECRET>, Organization <ORGANIZATION_SECRET>' \
-H 'content-type: application/json' \
-d '{
"element": {
  "key": "clover"
},
"providerData":{
  "code": "<AUTHORIZATION_GRANT_CODE>"
},
"configuration": {
  "oauth.callback.url": "https;//mycoolapp.com",
  "oauth.api.key": "Rand0MAP1-key",
  "oauth.api.secret": "fak3AP1-s3Cr3t",
  "clover.sandbox": "false",
  "merchantId": "5HBxxxxxxxxxxxx",
  "event.poller.configuration":{
        "timesheets": {
          "url": "/hubs/employee/timesheets?where=out_and_override_time >'${date:yyyy-MM-dd'T'HH:mm:ssXXX}'",
          "idField": "id"
        },
        "employees": {
          "url": "/hubs/employee/employees?where=modifiedTime>'${gmtDate:yyyy-MM-dd'T'HH:mm:ssXXX}'",
          "idField": "id"
        },
        "payments": {
          "url": "/hubs/employee/payments?where=modifiedTime>'${gmtDate:yyyy-MM-dd'T'HH:mm:ssXXX}'",
          "idField": "id"
        },
        "roles": {
          "url": "/hubs/employee/roles?where=modifiedTime>'${gmtDate:yyyy-MM-dd'T'HH:mm:ssXXX}'",
          "idField": "id"
        }
      }
    }
  },
  "tags": [
    "Docs"
  ],
  "name": "API Instance with Polling"
}'

Parameters

API parameters not shown in Cloud Elements are in code formatting.