Hi @Jici thanks for the input.
Unfortunately, that doesn’t seem to be the issue. The file that comes back is the proper PDF, no error. I can open it and it is the actual PDF file. The issue seems to be that with the API initialize call the ending of the file name is overridden somehow by Bubble to equal: api_initialize_file.
When running the API in the workflow the file name is always equal to convert.ashx. This then means it also stores and opens it as an .ashx file.
The action settings below (as well as screenshot of the file in the database).
I am using the exact same action steps for some other PDF creation APIs that I am testing and they all work well as they don’t have that .ashx ending.
