T'his article answers some of the most frequently asked questions (FAQs) about Payhawk Developer API.
Which events are available for webhook subscription in the Payhawk Developer API?
You can find detailed information about webhooks and their use in Payhawk Developer API in Nikolay Babev’s blog post, Mastering Webhooks for Efficient Financial Data Integration.
How do I check through the API if an expense has been exported? Which endpoint should I use?
Use Payhawk’s Expense History API.
Is it correct to use taxId for the CIF in the integration between Payhawk and MS Business Central?
“CIF” typically refers to a fiscal identification number. In Payhawk, the equivalent field in Spanish is Número de identificación fiscal, which corresponds to taxId in the platform.
If issues persist, contact Payhawk Support and share the exact payload you are using and a screenshot from Payhawk so you can verify the data mapping.
How can I retrieve invoices into MS Business Central once an expense has been reviewed?
Use the Expenses endpoint and filter by ReviewedAt. The filter must be encoded, and you can test it directly in the Developer Portal.
Alternatively, you can use webhooks for the expense reviewed event to trigger the data retrieval automatically.
Will enabling group settings in Payhawk affect existing API integrations?
No, enabling group settings does not change or disconnect existing API integrations for individual entities. However, customers should generate a new group-level API key and use the Group API for managing master data, while expense and payment data remain managed at the entity level.
How are deletions and merges of expenses handled by Payhawk’s Developer API?
When an expense is deleted, Payhawk triggers an expense.deleted event. When expenses are merged, one of the expenses triggers an expense.deleted event. Currently, there is no separate event for the merge action itself.
Each newly created expense in Payhawk receives a unique expense ID. When an expense is deleted, its ID is never reused for new expenses. This ensures that each ID always corresponds to the same expense and prevents any confusion where the same ID might reference a completely different expense.
For master data deletions and merges (for example, Vendors or Dimensions), see Payhawk’s Developer API or contact Payhawk Support for guidance on handling these scenarios.