For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
GuidesAPI ReferenceChangelog
GuidesAPI ReferenceChangelog
  • Introduction
    • Overview
    • Quickstart
    • Authentication
  • Core Guides
    • Document Extraction
    • Workflow Runs
    • Event Subscriptions
On this page
  • Get an API key
  • API key header
  • Request context
  • Usage guidelines
  • Key rotation
  • Next steps
Introduction

Authentication

Was this page helpful?
Previous

Document Extraction

Next
Built with

Authenticate requests to the Plextera Public API with an API key issued for your client integration.

Get an API key

API keys are managed in Plextera account settings.

Plextera -> Account settings -> API -> API keys
1

Open account settings

Sign in to Plextera, open your user or workspace menu, and select Account settings.

2

Open the API tab

In Account settings, open the API tab. This is where API access for your workspace is managed.

3

Copy the key

Copy the API key for the integration you are building. Store it in a secrets manager or environment variable before using it in requests.

If you do not see the API tab or cannot copy a key, ask a workspace administrator or your Plextera account team to enable API access.

API key header

Pass your API key in the Authorization header using the api-key prefix:

$Authorization: api-key YOUR_API_KEY

For example:

$curl https://api.plextera.com/api/public/v1/files \
>  -H "Authorization: api-key sk_live_abc123..."

The header value must include the api-key prefix followed by a space and the key. Sending the key alone without the prefix will result in a 401.

Request context

Each API key gives access to one Plextera workspace. You do not pass a workspace identifier in requests.

Usage guidelines

  • Use one API key per integration (e.g., one key per environment: staging, production).
  • The same key is valid across all API surfaces: Files, Document Insights, Workflows, and Event Subscriptions.
  • Store keys in environment variables or a secrets manager. Do not commit them to source control.

Key rotation

To rotate a key, issue a new one and update your integration before deactivating the old key. There is no grace period once a key is deactivated.

Next steps

  • API Reference - full authenticated endpoint reference
  • Event Subscriptions - configure webhook push notifications