Skip to main content

Events

Currently, EnableNow supports the following webhook events:

  1. Transactions Fetched
    Occurs when transactions has been fetched successfully from the bank. This event will also be called on auto-synchronize or manual execution of a consent refresh (see Consent Refresh).
  2. Consent Accounts Updated
    Occurs when accounts from a consent has been updated.
  3. Consent Status Updated
    Occurs when a consent status has been retrieved and saved.
  4. Categorization Job Completed
    Occurs when a categorization job has been completed.
  5. Analysis Job Completed
    Occurs when an analysis job has been completed.
  6. DataBridge Share Created
    Occurs when a databridge share has been created.
  7. DataBridge Share Updated
    Occurs when a databridge share has been updated.

Transactions Fetched​

Event name: transactions.fetched

When transactions have been fetched from the bank, a webhook event is triggered with the following Data structure:

{
  "event": "transactions.fetched",
  "data": {
    "userId": "<user_id>",
    "externalUserId": "<external_user_id>",
    "consentId": "<consent_id>"
    "addedTransactionsCount": "<number_of_inserted_transactions>"
  }
}

Please note that the userId will only be filled, when the consent was created with a user_id.

Event name: consent.accounts.updated

When the accounts of a consent are retrieved and saved, a webhook event is triggered with the following Data structure:

{
  "event": "consent.accounts.updated",
  "data": {
    "userId": "<user_id>",
    "externalUserId": "<external_user_id>",
    "consentId": "<consent_id>"
  }
}

Please note that the userId will only be filled, when the consent was created with a user_id.

Event name: consent.status.updated

When a status of a consent is updated, a webhook event is triggered with the following Data structure:

{
  "event": "consent.status.updated",
  "data": {
    "userId": "<user_id>",
    "externalUserId": "<external_user_id>",
    "consentId": "<consent_id>",
    "status": "<updated_consent_status>"
  }
}

Please note that the userId will only be filled, when the consent was created with a user_id.

Categorization Job Completed​

Event name: categorizationjob.completed

When a categorization job is completed, a webhook event is triggered with the following Data structure:

{
  "event": "categorizationjob.completed",
  "data": {
    "userId": "<user_id>",
    "externalUserId": "<external_user_id>",
    "consentId": "<consent_id>",
    "jobId": "<categorization_job_id>"
  }
}

Please note that the userId will only be filled, when the consent was created with a user_id.

Analysis Job Completed​

Event name: analysisjob.completed

When an analysis job is completed, a webhook event is triggered with the following Data structure:

{
  "event": "analysisjob.completed",
  "data": {
    "jobId": "<analysis_job_id>"
  }
}

DataBridge​

Our DataBridge feature will send different kinds op webhook events based on the used feature.

Share Created​

Event name: databridge.share.created

When a DataBridge Share is created, a webhook event is triggered with the following Data structure:

{
  "event": "databridge.share.created",
  "data": {
    "expirationDateUtc": "<expiration_date_utc>", //2026-04-30T12:00:00
    "consentIds": [],
    "accountIds": [],
    "analysisIds": [],
    "reference": "<reference>"
  }
}

Share Updated​

Event name: databridge.share.updated

When a DataBridge Share is updated, a webhook event is triggered with the following Data structure:

{
  "event": "databridge.share.updated",
  "data": {
    "expirationDateUtc": "<expiration_date_utc>", //2026-04-30T12:00:00
    "reference": "<reference>"
  }
}