Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Warning

The Webhooks implementation is currently in 

Status
colourRed
titleBETA
 mode. Please check this page frequently for more updates. 


Overview

Webhooks allows you to subscribe to events that happens within the Arken Application. When an event is triggered, a HTTP POST will be executed using your assigned endpoint URL. 

Webhooks are configured by account basis. Once configured, the webhook will be triggered each time an event occurs. 


In this document:

Table of Contents

Set-up

Note

The Webhook functionality can only be configured via Arken Public API.

To enable webhooks, you need to have the following:

  • An active Arken Account, mainly your Arken Account Hash Identifier
  • Your Arken API Access Key and Secret Key 
  • Your API endpoint that will be receiving the callback from Arken
  • Your API endpoint security details - This should be a secret header key or Open ID Connect Access and Secret Keys

To enable the webhook subscription, you need to call the HTTP POST /Event/Subscription endpoint providing the following details:

  • Your Arken Account Hash Identifier
  • The HTTP POST Url where Arken needs to send the events to 
  • The Callback API Version number (if available)
  • The security details needed for Arken to execute a post, i.e. Secret Header  value or Open ID Connect Access and Secret Keys

Events

Event Categories

When configuring a webhook, you will be sent the following events:

Event CategoryEvent TypeDescription
AccountUpdateUpdates were conducted on your current account
ClientCreateA new client has been created

UpdateAn existing client has been updated

DeleteAn existing client has been deleted
DocumentDataCreateA new document data entry has been created

UpdateAn existing document data has been updated

DeleteAn existing document data has been deleted
UserCreateA new Arken user is added under your current Account

UpdateAn existing Arken user is updated

DeleteAn existing Arken user is deleted
FileStoreGetFileDetailDownloadAn existing document has been fetched for download

UploadA document has been created and is ready to be downloaded

Delivery attempts and retries

The Arken service will attempt to deliver your webhooks in near-real time. If the webhook sendout encounters an issue, the Arken system will try to attempt sending the event 3 times prior to abandoning the sendout. Arken Webhooks cannot be manually retried after this time, though you can query for the event using the Event endpoints to reconcile your data with any missed events. For more information on accessing the Event endpoints, please see the /wiki/spaces/MAIN/pages/100433931 page. 


Sample Webhook Client Code

Attached below is a sample code on receiving Webhooks on your system.  

View file
nameevent.api.webhook.client.zip
height250

The sample attached contains a .NET core application that has one post endpoint that will receive the event.