VUMI Documentation
  • Introduction
    • 🎉Welcome!
    • ➡️Quick Start
  • Platform
    • App Overview
      • API Products
      • Connections Overview
      • API Configuration
    • Link Overview
      • Link redirects
      • Link parameters
      • Customization
  • General API Resources
    • Authentication
      • API Login
    • Entities
      • List entities for app
    • Connections
      • Exchange public token
      • Get Connection status
      • List all connections
      • List public tokens
      • Delete Connection
    • Investments
      • List investments
    • Webhook
      • Get verification key
  • Aggregation
    • Accounts
      • List accounts
      • List account transactions
    • Portfolios
      • List portfolios
      • List portfolio transactions
      • List portfolio positions
  • Assets Transfer
    • Assets transfer
  • Developer Resources
    • API and Widget Errors
    • Webhooks and security
      • Webhook verification
    • Pagination
    • Tracing requests
Powered by GitBook
On this page
  1. Developer Resources

Tracing requests

Easier and faster troubleshooting

Troubleshooting is one of our main concerns, and we attempt to solve problems as fast as possible when they happen. For that reason, we have included two HTTP headers in our requests to help with tracing:

  • X-Request-ID: generated by the Vumi API, will be returned in the response headers of every request done. This header will not be accepted when passed in requests. It is a unique UUID that will be helpful to include when reporting API errors.

  • X-Client-Trace-ID: this optional header will be taken from the request and returned as-is in the response. Helpful to trace requests accross your servers and the Finlink API.

Our reccommendation is to always log this headers in your system, so that it can be easily retrieved and reported when informing an error to us. Providing these headers might improve speed significantly when resolving issues.

Last updated 4 months ago