Using cookies to convert HTML documents to PDF in Node with Axios

In this comprehensive guide, we will demonstrate the step-by-step process of incorporating custom Cookies into your URL request for PDF conversion using PDFShift's API. By leveraging this functionality, you can maintain an active session, enabling authentication as a specific user before generating the PDF document.

To do so, we'll use the cookies parameter when sending a request to PDFShift. It expects a list of dictionnary that contains the name and the value of the cookies (more details after):

const axios = require('axios');
const fs = require('fs');

// You can get an API key at https://pdfshift.io
api_key = 'sk_xxxxxxxxxxxx'

params = {
    source: 'https://www.example.com',
    // The "cookies" parameter expects a list of dictionnary that contains the name and the value of the cookies
    cookies: [
        { name: 'PHPSESSID', value: 'el4ukv0kqbvoirg7nkp4dncpk3' }
    ]
}

const response = await axios.post('https://api.pdfshift.io/v3/convert/pdf', params, {
    auth: {
        username: 'api',
        password: api_key
    }
});

// Handle errors:
if (response.status >= 400) {
    throw new Error(`Request failed with status code ${response.status}: ${response.data}`);
}

fs.writeFileSync('result.pdf', response.data);

console.log('The PDF document was generated and saved to result.pdf');

The cookies parameter accept the following parameters:

• name : The name of the cookie.
• value: The value of the cookie.
• secure: A boolean (defaults to false) that will tell the browser to only send the cookie if the request is being sent over HTTPS.
• http_only: A boolean (defaults to false) that will tell the browser to not expose it to client-side scripts.

Like in our guide to send custom HTTP headers or to access secured pages, this allows you to protect your documents from any visitors while allowing PDFShift to access the page and convert it to PDF.