We ship a small web server you can run. We suggest this if not using Lambda. You just run the executable and it hosts a web server with an API. You’ll find this in the SigParserEmailUtilsWebAPI-{platform}.zip file.

Create an environment variable called SigParserLicenseKey and the value should be your license key.

Download a .skm file from Cryptolens if you need a machine locked key. You can get your machine key from the Swagger page when you run the web application and visit the URL in your browser.

Run the SigParserEmailUtilsWebAPI executable which will start the web server.

On Windows you’d run a command like

On Linux you’d run a command like

There is a docker file included in the zip file. You can use this to generate a container. You might need to modify the file to fit your needs.

If you go to the site you’ll see a swagger page detailing the API. You’ll also see your machine key.

RAM: 3GB Minimum

CPU: 2 core minimum

If you expect to send emails in parallel to the web endpoint for processing we suggest 1GB per and 1 core per request.

For example, if you expect to need to handle 10 concurrent requests you need 10 cores and 10GB of RAM.

The easiest way to configure which port the web server listens on it so pass it via a command line argument via --urls or use the environment variable ASPNETCORE_URLS.

We use Kestrel ASP.NET Core web server. You can read more about configuring it.

The easiest way to setup the webserver is to use the Task Scheduler to start the web server every time the server starts up.