API Keys and Public API

DripDrop provides a public API for account-level integrations. Use API keys to authenticate server-side tools, scripts, and integrations that need to work with your DripDrop account.

This page explains how to create and manage API keys. It does not duplicate the endpoint reference.

For endpoint details, schemas, request and response examples, and testing, use the live API docs: https://api.dripdrop.dev/docs/

Before using the public API:

  • You need access to the DripDrop account whose data you want to integrate with.
  • The account must be active.
  • The account must have an active subscription.
  • Public API access may be rejected if the account subscription is missing or lapsed.
  • API usage may be subject to plan-based limits or quotas.

Go to Settings → API Keys.

The API Keys panel lets you create and manage keys for the public API. If no keys exist, create one to start using the public API.

The page may show active and revoked keys separately. Existing keys show limited metadata, such as:

  • Key name
  • Key prefix
  • Creation date
  • Expiry date, if set
  • Revocation status
  1. Go to Settings → API Keys.
  2. Click Create API Key.
  3. Enter a name for the key.
  4. Optionally set an expiry date.
  5. Create the key.
  6. Copy the generated key immediately.

The full key is only shown once after creation. After you close the modal, DripDrop only shows the key prefix.

Treat API keys like passwords.

Do:

  • Store keys in a server-side secret manager or environment variable.
  • Use a separate named key for each integration where possible.
  • Set expiry dates for temporary or vendor-specific access.
  • Rotate keys when staff, vendors, or automation ownership changes.

Do not:

  • Put API keys in client-side code.
  • Commit API keys to a public or private repository.
  • Share keys in screenshots, support tickets, chat messages, or public docs.
  • Reuse one key for every integration if separate keys would be safer.

Use the live API docs for endpoint-level details:

https://api.dripdrop.dev/docs/

The live API docs are generated from the public API schema and are the source of truth for:

  • Available endpoints
  • Required fields
  • Request examples
  • Response schemas
  • Authentication details
  • Error responses

Use your API key with the X-API-Key header.

X-API-Key: ***

Example request pattern:

curl https://api.dripdrop.dev/v1/...   -H "X-API-Key: ***"

Replace the path and request body with the endpoint-specific details shown in the live API docs.

Expired keys stop working. Revoked keys stop working immediately and cannot be restored.

If an integration uses a revoked key, update that integration with a new key.

Public API requests may fail if:

  • The API key is expired.
  • The API key was revoked.
  • The key was copied incorrectly.
  • The account is inactive or suspended.
  • The account does not have an active subscription.
  • The request is missing the X-API-Key header.

Public API activity is attributed to the account associated with the API key.

An API request fails
  1. The key was copied correctly.
  2. The key has not expired.
  3. The key was not revoked.
  4. The account is active.
  5. The account subscription is active.
  6. The request uses the X-API-Key header.
  7. The request is sent to https://api.dripdrop.dev.
  8. The endpoint, method, and payload match the live API docs.