API keys, scopes and test mode

4 min read · Updated 2026-11-15

Short answer

On Pro and Team, create API keys under Dashboard > Domain & API. Each key has a scope (Read only, Read and write or Full access) and a mode: live keys (pf_live_) work for real, test keys (pf_test_) never email anyone and their transfers expire after 24 hours.

The Pandafile API lets your own apps, scripts and servers send files, collect uploads and request signatures. It is included with Pro and Team and follows the same limits as the website. Everything starts with an API key.

Create a key

  1. Sign in and open Dashboard > Domain & API.
  2. Under API keys, give the key a name, for example Website uploads.
  3. Choose the key mode, Live or Test, and the key access: Full access, Read and write, or Read only.
  4. Press Create key and copy the key straight away. For your security we show it only once.
  5. Send it with every request in the header Authorization: Bearer followed by the key.

You can have up to 10 active keys. Live keys start with pf_live_ and test keys with pf_test_. The developer guide is at pandafile.co/developers and the API reference at pandafile.co/developers/api.

Scopes: what a key may do

  • Read only: GET requests only. The key can look things up but change nothing.
  • Read and write: everything in Read only, plus creating, changing and deleting transfers, file requests, signature requests and webhook subscriptions.
  • Full access: everything, including account settings such as branding and team invites.

Test mode

  • Transfers made with a pf_test_ key are test data. Nobody is ever emailed, not even recipients you add.
  • Test transfers always expire 24 hours after they were created and can't be extended.
  • They count toward no limit, storage or usage, and they don't show in your normal transfer lists.
  • Webhook events about them have livemode set to false, and they never go to Slack, Microsoft Teams or Discord.
  • A few actions work only with a live key. With a test key the API then answers with the error test_mode_unsupported.

Keep keys safe

  • Anyone with a key can send files from your account. Keep keys on your server, never in the public code of a website or app.
  • Revoke a key in Dashboard > Domain & API if it may have leaked. Apps using it stop working at once, and webhook subscriptions made with it, for example by Zapier or Make, stop too.
  • Each key has its own rate limit. Every response shows where you stand in the RateLimit headers.
  • In a team, API keys are personal: each member creates their own.
Ready to send?

Up to 50 GB free per transfer, no account needed.

Send files