Connector Improvement: Navan connector: Transactions table
Answered
The Navan connector is using an older endpoint to pull the transactions table. This endpoint needs to be changed to a newer version that Navan has moved to for continued support of the transactions table.
This is extremely urgent because we have a customer who needs this data, we had promised that this is possible based on Fivetran documentation.
Old endpoint: /v1/liquid/paginatedReports
New endpoint: /v1/expense/transactions
-
Official comment
Hi Praneeth,
Thank you for reaching out regarding the Navan connector.
Could you please share more details on the issue you are currently facing in the TRANSACTION table?
- What specific problem or limitation are you observing?
- What is your primary use case for this data?
- Are there any specific fields or data points you expect that are currently missing?
To better align on this, could you also please share the latest API documentation for the updated endpoint (
/v1/expense/transactions)? I wasn’t able to locate the relevant documentation on my end.We’ll review this on priority once we have these details.
Best regards,
Sahu
Please sign in to leave a comment.
Comments
1 comment