Stirling PDF icon

Stirling PDF

Merged API: Stirling PDF - Processing API + Stirling PDF - Management API + Stirling PDF - System API

Actions260

User → Update Api Key

AI-generated

Summary

Updates (regenerates) the API key for the current user through the Stirling PDF API. The source pack shows only a class stub, so the exact endpoint and response shape are not confirmed.

Inputs

  • Request Options > Batching — Splits input items into batches to throttle requests. Items per Batch defaults to 50 (-1 disables batching, 0 is treated as 1). Batch Interval (ms) defaults to 1000 (0 disables the wait).
  • Request Options > Ignore SSL Issues (Insecure) — If enabled, accepts responses even when SSL certificate validation fails. Defaults to false.
  • Request Options > Proxy — HTTP proxy URL, optionally with credentials, e.g. http://username:password@myproxy:3128.
  • Request Options > Timeout — Milliseconds to wait for response headers before aborting the request. Defaults to 10000.

Output shape

Most likely the API response from the Stirling PDF server, probably a new API key, returned as n8n item data. This is not confirmed by the source.

The source pack has no implementation body. The operation declares no operation-specific parameters, only request options. Authentication comes from the node's credentials. Because this changes the user's key, any existing key stops working if the server replaces it.

Examples

Example 1: Rotate a Stirling PDF API key on a schedule

Use a Schedule trigger, then Stirling PDF with Resource User and Operation Update Api Key. Leave the request options at their defaults. Store the returned key in a secrets store.

Example 2: Call a Stirling PDF server behind a corporate proxy

Set Request Options > Proxy to http://myproxy:3128 and raise Timeout to 30000.

Links

Discussion