Authentication

How authentication works on the marketplace model — API keys are issued and billed by the marketplace, not by ANNÁVE TECH directly.

InvoicePDF is sold through API marketplaces. A marketplace subscription is the only way to get access at launch.

API keys are issued by the marketplace, not by ANNÁVE TECH. There is no separate InvoicePDF account, dashboard, or sign-up — subscribing on the marketplace is the entire onboarding step.

How a request is authenticated

A request never reaches the InvoicePDF server directly. It is routed through the marketplace's proxy, which:

  1. Validates the caller's marketplace API key
  2. Confirms the caller is within their subscribed plan
  3. Forwards the request to the origin server with a proxy secret and a plan header attached

The origin server checks the proxy secret to confirm the request genuinely came through the marketplace, then reads the plan header to resolve the tier (free, Starter, Pro, Business) for that request. Calling the origin server directly, without a valid proxy secret, is rejected.

How you authenticate

Send the marketplace API key using the header name and format required by that marketplace. This convention is set by the marketplace, not by InvoicePDF, and does not change between InvoicePDF endpoints — consult the marketplace listing for the exact header name and format.

Tier resolution

The marketplace meters and bills usage against your subscribed plan. InvoicePDF trusts that decision and does not double-count — it only maps your plan to a rendering behavior: the free plan gets a watermarked PDF, paid plans get a clean one.

Quota errors (INVOICE_ERR_QUOTA_EXCEEDED) originate from the marketplace enforcing your plan limit, not from a separate InvoicePDF-side counter, when accessing through a marketplace.

Unauthorized requests

A request with a missing or invalid key returns 401 INVOICE_ERR_UNAUTHORIZED. See Error Codes for the full envelope shape.