DATE:
AUTHOR:
Mono product team
API

January Product Updates: Mono Data Enrichment v2 API and more

DATE:
AUTHOR: Mono product team

Product Highlights

Updates to the Mono Data Enrichment API

We've improved the Mono Data Enrichment API to deliver improved performance and efficiency, with the addition of the new Job Tracker endpoint. This new feature helps you monitor the status of a Transaction CategorisationTransaction Metadata and Statement Insights API request in real time.

Key Features and Changes

  • Transaction Categorization

    a. Request Method: Changed from GET to POST.

    b. Updated API Route:

  • CSV Transaction Categorization

    a. Updated Webhook Response: The webhook event for transaction metadata ("mono.events.transaction_categorisation") updates will now indicate when categorised data is available. It will include details such as the file name and a message confirming that transactions have been updated with metadata.

    Note: We no longer include categorisation data in the webhook payload. You have to now call the Retrieve Categorisation Transactions endpoint for the categorise uploaded data.

    b. Data Retention: The categorised transactions will be available for 1hour. If the endpoint is called again with the same file after this period, the full categorisation process will be re-initiated.

    c. . Updated API Route:

  • Transaction Metadata

    a. Request Method: Changed from GET to POST.

    b. Updated API Route:

  • CSV Transaction Metadata

    a. Updated Webhook Response: The webhook event for transaction metadata ("mono.events.transaction_metadata") updates will now indicate when metadata is available. It will include details such as the file name and a message confirming that transactions have been updated with metadata.

    b. Data Retention: The metadata data on the uploaded transactions will be available for 1hour. If the endpoint is called again with the same file after this period, the full metadata initiation process will be re-initiated.

    c. . Updated API Route:

  • Statement Insights

    a. Updated Webhook Response: The webhook event for statement insights ("mono.events.statement_insights") updates will now indicate when metadata is available. It will include details such as the account id and a message confirming that statement insights have been updated with information.

    Note: We no longer include statement insights data in the webhook payload. You have to call the Retrieve Statement Insights Records endpoint for the updated information.

    b. Data Retention: The processed statement records will be available for 1hour. If the endpoint is called again, after this period, the full statement insights process will be re-initiated.

    Note: These updates maintain backward compatibility with existing API versions.

    To learn more about this update, please check our technical documentation.

    Updated API Route:

Product Improvements

Financial Institutions

  1. Opay (Payment Initiation Downtime): This issue has been resolved and the connection fully restored. Your users can now pay with their Opay accounts via the Mono DirectPay widget.

  2. Providus (Payment Authorization Downtime): This issue has been resolved and your users can now make payments to your business with their Providus bank account via the Mono DirectPay widget.

Mono API

We've made updates to our Direct Debit service to provide sandbox support to improve the testing experience while integrating the product. We've also made updates to our Create a mandate API endpoint service enhancing sandbox support.

We're always available to help

Mono Slack Community

Join the discussion, ask questions, and suggest new features in our Slack community

Get support

Email us at support@mono.co

Powered by LaunchNotes