I had to re-implement the entire invoice in my own PDF. I used FPDF, but there are quite a few others out there that you can use.
They intentionally also make it very difficult to try and programmatically get the PDF of the invoice. If you are logged into the UI, you can batch download them with a script, but not with the API. If you try (as many have) to use the public link in the API response and try to detect the “Download PDF” link, it will require the script to be able to handle javascript context like a browser would. It also changes the URL link for the invoice every time you reload the page..
Im having a really hard time understanding why they don’t allow this, allowing this in the API is rather trivial because it’s already implemented in the app and the web ui. There must be a business reason for it.
I had investigated moving straight to quickbooks for invoicing and accounting and its very feasible, but haven’t taken the time to get it done.
Ive been building automation and integrations for 20+ years and its not the first time a company introduces friction to customers who are trying to get the best out of a product.
– Chris