Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.campground.fyi/llms.txt

Use this file to discover all available pages before exploring further.

API keys let external tools read from and write to your Campground organization programmatically. You can use them to connect automation platforms like Zapier or Make.com, sync data with other systems, or build custom integrations with the Campground REST API. Each key is scoped to specific actions so you can grant only the access a given integration needs.
Treat API keys like passwords. Anyone who has a key can access your organization’s data up to the key’s permitted scopes. Never share keys in public repositories, client-side code, or chat messages. If a key is exposed, revoke it immediately and create a new one.

​
Creating an API key

1

Open Settings > API Keys

In your admin panel, navigate to Settings > API Keys.
2

Click Create API key

Click Create API key to open the key creation dialog.
3

Give the key a name

Enter a descriptive name so you can identify the key later — for example, “Zapier sync” or “Custom CRM integration”. This name is for your reference only.
4

Select scopes

Choose the scopes the key should have. Grant only the scopes your integration actually requires.
ScopeWhat it allows
read:profilesRead member profile data
write:profilesCreate and update member profiles
read:teamsRead team data
read:applicationsRead application data
5

Copy the key immediately

After you click Create, Campground displays the full API key once. Copy it to a secure location now — you will not be able to view it again. Only the first eight characters are stored for display purposes.

​
Using your API key

Pass the key as a bearer token in the Authorization header of every request: 
Authorization: Bearer YOUR_API_KEY
All requests go to the base URL: 
https://api.campground.fyi/public
For the full list of available endpoints, request and response formats, rate limits, and integration examples, see the API reference.

​
Common use cases

  • Zapier — trigger Zaps when new members are accepted, or push new contacts from a form into Campground profiles
  • Make.com — build multi-step automations that read application data and update records in other tools
  • Custom integrations — pull member or team data into your own dashboards, reporting tools, or internal systems

​
Revoking a key

To revoke a key, go to Settings > API Keys, find the key by its name or prefix, and click Revoke. The key becomes invalid immediately. Any integrations using that key will stop working until you update them with a new key.
If you need to rotate a key — for example, after a security incident or a scheduled rotation — create the new key first, update all integrations to use it, and then revoke the old key. This avoids downtime.