Custom PDF Not Being Returned via Download URL

Hi Jotform Support,

I'm trying to programmatically download a specific PDF layout from my form, but I keep receiving the default submission-style PDF instead.

Here are the details:

• Form ID: 251182104910142
• Custom PDF Name: FiveStarLOR
• Download URL being used:

arduino



Copy code

https://www.jotform.com/server.php?action=getSubmissionPDF&sid=SUBMISSION_ID&formID=251182104910142&pdfName=FiveStarLOR.pdf

• (Where SUBMISSION_ID is dynamically replaced)

I've confirmed the following:

• The custom PDF is correctly named FiveStarLOR (case-matched exactly).
• There are no other PDFs active like “New Document 1” — they have been deleted.
• I’ve tested the link manually with valid submission IDs, but it still returns the wrong layout.

Could you please verify if the correct PDF is being generated on your end or if there's a caching or system-side issue?

Thanks so much in advance for your help!

Hi Grecia,

Thanks for reaching out to Jotform Support. Can you try using this API endpoint instead and make sure to fill in the needed information when you test it as well? Here is the code:

https://api.jotform.com/pdf-converter/{formId}/fill-pdf?download=1&submissionId={submissionId}&apikey={apiKey}

Replace the following information before testing it:

• {formId} - the unique series of numbers at the end of the Form URL.
• {submissionId} - the unique number assigned to each submission.
• {apiKey} - allow you to authenticate your information and connect your form data. You can create it using this guide.

Give it a try and let us know how it goes.

Getting an authorization failed result even though the key is a full access key. And I did it both possible ways.

Hi Grecia,

The authorization failed error even with a full access API key usually indicates an issue with the API key permissions or how the key is being used in the request. Can you try to regenerate the API key or review your account's API settings?

Make sure that the API key you are using has Full Access permissions under your Account API settings. Also, make sure the API key is included properly in the request URL or headers as required by the API endpoint and double-check for any typos or formatting issues.

Give it a try and let us know how it goes.