In this guide, you’ll find best practices for monitoring your application’s usage of Finch to identify patterns and potential issues.
/introspect
endpoint is an extremely important tool when using Finch, allowing you to read account information associated with an access_token such as the connection status.
finch-request-id
for every response, whether successful or unsuccessful. The finch-request-id
can be found in every HTTP response Header. The finch-request-id
is required by the Finch Support team for debugging request issues.
access_token
is associated with a static Finch connection_id
. You can find the id using the /introspect
endpoint. Save this in your data store alongside the access token and use it when contacting Finch Support about an issue.