One powerful tool to help you debug potential issues or see the paper trail is Meld's Activity Log. The activity log registers all activities performed by you or performed by Meld on behalf of you and presents them in an easy to trace manner. It is an easily searchable logging tool you can use to follow a trail of activity and investigate an issue.

Some of the major types of activities captured by the activity log are:

1. API calls from you to Meld (including changes made in the Meld dashboard).
2. API calls Meld makes to a service provider on your behalf.
3. Webhooks that the provider sends Meld.
4. Webhooks that Meld sends you.

How to Use the Activity Log

1. First, start by hitting Meld's Activity Log endpoint with whatever search parameters you would like. The date params (start and end) are required but all other params are optional. The activities are ordered chronologically with the most recent at the top, and every activity has a timestamp.

Examples of actions you can filter by are:

• INBOUND_REQUEST: An API call you made to Meld
• OUTBOUND_REQUEST_SERVICE_PROVIDER: An API call that Meld made to a service provider on your behalf
• INBOUND_REQUEST_WEBHOOK: A webhook sent from the service provider to Meld
• OUTBOUND_REQUEST_WEBHOOK: A webhook that Meld sent to you

2. Once you find a particular activity that you would like more information about, grab the key of the activity and head to Meld's Activity Log Details endpoint. Pass in the key as a query param and you will now see all the details for that particular activity. These details include the request and response headers, the request and response body, the response code, and more. You can also see the raw response Meld received from a particular service provider here. This can help debug if for example data that looks suspicious is due to Meld's transformation or is the exact data that Meld received from the provider.

Bank Linking

The recommended way of using the activity log for bank linking is the following:

1. Find the activities related to a particular connection by passing in the connectionId, the customerId, or the externalCustomerId. By default 10 activities are returned but you can use the limit param to return more.
2. Find the exact activity that you are looking for by following the trail or filtering more specifically. For example, if you are looking for all webhooks, you can pass in the action param with the value OUTBOUND_REQUEST_WEBHOOK, and if you are looking for a particular webhook, you can pass in the webhook name in the eventType query param field. See here for a list of of eventTypes you can filter by for bank linking.
3. Once you locate the activity or activities you are looking for, grab the key and use the activity log details endpoint to see the details of the activity.

Crypto

The recommended way of using the activity log for crypto is the following:

1. Find the activities related to a particular transaction by passing in the transactionId, the customerId, or the externalCustomerId. By default 10 activities are returned but you can use the limit param to return more.
2. Find the exact activity that you are looking for by following the trail or filtering more specifically. For example, if you are looking for all webhooks, you can pass in the action param with the value OUTBOUND_REQUEST_WEBHOOK, and if you are looking for a particular webhook, you can pass in the webhook name in the eventType query param field. See here for a list of of eventTypes you can filter by for bank linking.
3. Once you locate the activity or activities you are looking for, grab the key and use the activity log details endpoint to see the details of the activity.

Use Cases

Here are some potential use cases of the activity log:

1. Seeing what webhooks were sent for a particular connection or transaction if you suspect you may have missed 1 or more on your end.
2. Seeing the raw data the provider sent Meld to evaluate if there's an issue with a particular connection or transaction.
3. Seeing which user performed a particular dashboard activity - for example which user added a new integration to your account and when.

The activity log is a very powerful tool, please make your requests as specific as possible by leveraging the query params or else there may be too much data to return or to be of use.