Developer Checklist
Technical requirements to verify before going live with your Fiskil integration
AI Actions
Error Handling
Once you have gone live is an unfortunate time to discover you have not properly written your code to handle every possible error type, including those that should "never" happen. Be certain your code is defensive, handling not just the common errors, but all possibilities.
- Account for different error types that may be thrown by Fiskil APIs and ensure each edge case is handled.
- Implement retry logic or error handling for intermittent outages or connectivity errors at supported institutions. Fiskil API calls may occasionally fail due to issues at data holder institutions.
Storage and Logging
Log Fiskil identifiers and IDs properly to enhance security. When contacting Support about a specific request or webhook, these will be required.
Ensure the following identifiers are securely logged:
| Identifier | Description |
|---|---|
end_user_id | Included in most requests to identify the end user whose data is being accessed. |
consent_id | The consent identifier associated with each data sharing consent. |
session_id | The session identifier associated with every consent created or attempted. |
error_id | Included in all errors returned to uniquely identify the error reported. |
End User Management
- Delete end users that are no longer using the product or receiving a service from your product.
Product-Specific Recommendation: Transaction API
- If fetching historical transaction data, make sure your app implements pagination logic.
- The Transaction API natively supports the categorization of transactions through the
categoriesobject. For a comprehensive understanding of the classification system, download the Categories Taxonomy CSV, which provides detailed information on all category types, subtypes, and their hierarchical relationships supported by Fiskil.
Was this page helpful?