API access

API access lets an approved community admin create scoped tokens for one community.

Community-bound keys

Every API token belongs to exactly one community. A token created from one community cannot be used against another community's API routes, even if the same admin has access to both.

Use the base URL shown in Admin Center for the selected community:

https://api.zeeker.com/api/admin/communities/{communityId}/api

Requests must include the token as a bearer token:

curl -H "Authorization: Bearer zk_live_xxx" \
  https://api.zeeker.com/api/admin/communities/{communityId}/api/stats

Privacy limits

Community API responses do not expose member emails, member names, direct identifiers, or private profile data. Use these endpoints for aggregate metrics and operational integrations, not member exports.

Flow in Admin Center

1. Open Admin Center -> API Access for the community.
2. Create a key with a label, scopes, rate limit, and maximum date range.
3. Copy the secret immediately. The full token is only shown once.
4. Use the base URL shown for the active community.
5. Pick an endpoint from the endpoint list at the bottom of the page.

Scopes

Scope	Allows
stats:read	Read aggregate community stats.
posts:read	Read post-level operational data without private member fields.
members:read	Read safe member activity counts only.

Limits and rotation

Use the smallest scope set that works for the integration. Set an expiration date for temporary integrations, rotate long-lived keys regularly, and revoke inactive keys from the same page.

Endpoint reference

The API Access page keeps endpoint paths at the bottom so the setup flow stays clear.

Endpoint	Purpose
GET /stats	Aggregate activity and moderation-safe stats.
GET /posts	Community post data without private member fields.
GET /moderation	Moderation-oriented operational data for the selected community.