Modify HACPEE interaction with 3rd party PDF Generator

In HACPEE v2.1, it permits interacting with 3rd party SW tools to generate PDF files in the following way:
-HACPEE is able to identify the LU3 printer name that has been passed through URL.
-Whenever a given LU3 receives data, HACPEE generate the SPL text file in a folder that is unique for each LU3name. This means that if there are 1000 different LU3names, there will be 1000 different folders.
-The 3rd party PDF generator can then scan the folder and notice the SPL file, and generate the PDF file including whatever logos and forms of the company.
-The 3rd party PDF generator can then place the PDF file in the very same folder where the SPL file was found, i.e. on the folder for that specific LU3name.
-Then HACPEE will notice the PDF file placed in the folder, and will show the PDF in the 'Printer session' screen on HACPEE web session for the specific user that owns that LU3name.

This procedure is mostly acceptable for the client, however, the 3rd party PDF generator does not seem to be capable of scanning/monitoring thousands of folders; instead, it would ideally monitor only one input folder.
The client requires any of these two different options to improve this way of interface between HACPEE 2.1 and the 3rd party PDF generator. Option 2 is the preferred for the client, but option 1 would also be acceptable:

1- One input SPL folder, many output PDF folders:
-HACPEE should place the SPL text files of all incoming users in a unique folder. This means that SPL files comming from all thousands different LU3names should go to the same input folder (ie. I120690B -> /docpath/data1; I11128BE -> /docpath/data1 , etc).
-HACPEE should include the specific LU3name of that user inside the SPL file, specifically at the begining of the first line of the SPL file. The pdf generator expects a specific jobline sintax where the LU3Name is mandatory, syntax would be @#LU3NAME (e.g. if the LU3 is I177782F the first line of the SPL file would be @#I177782F) . The purpose of this is that the 3rd party PDF generator is able to know what the target LU3name is.
-The 3rd party PDF generator will then scan that unique folder, generate each new PDF file, and indentify the target LU3name.
-Then the PDF generator will then place the PDF file in the specific folder for each LU3name. This means there will be one folder for each LU3name (thousands of LU3names and folders).
-Then HACPEE should notice the new PDF file, and be able to display it in the 'Printer session' screen of HACPEE web session for the specific user that owns that LU3name.

2-HACPEE should be able to interact with REST API interface of the 3rd party PDF generator:
-HACPEE should be able to issue a REST API call to the PDF generator, passing SPL text file and the LU3name. The pdf generator expects a specific jobline sintax where the LU3Name is mandatory, syntax would be @#LU3NAME (e.g. if the LU3 is I177782F the first line of the SPL file would be @#I177782F) .
-The 3rd party PDF generator would receive the REST API call, then generate the PDF, and return the file to HACPEE with the PDF file
-Then HACPEE should be able to show the PDF file in the ‘Printer Session’ screen on the HACPEE web session for the specific user that owns that LU3name.
This will require deeper discussion about the possible details of the implementation and needs from client, so client is willing to discuss.