Reeve.Community

What it does

• The community feature isn't turned on automatically, even for fully released apps—the app owner has to specifically request it. Once approved, the app must use a secure private key to access community features, and access can still be blocked if the app or organization has opted out.

Getting started

1. Have the app owner request the community capability for your host app. It is not on by default, even for GA apps, and stays blocked if the app or organization has opted out.
2. Once approved, authenticate with your secret Reeve host key (X-Reeve-Host-Key) to call the Reeve.Community surface.
3. Make your first request and check the response, then wire it into your app.

Limits & notes

• Usage is metered against your Reeve credit balance via community_active_member_month, community_post; see the pricing page for current rates.
• Requests authorize on your organization; a valid host key scoped to this capability is required.

FAQ

What does Reeve.Community do?

The community feature isn't turned on automatically, even for fully released apps—the app owner has to specifically request it. Once approved, the app must use a secure private key to access community features, and access can still be blocked if the app or organization has opted out.

How is Reeve.Community billed?

Usage is metered against your Reeve credit balance; see the pricing page for rates.

Sources

2 of 9 claims on this page are grounded in the Reeve.Knowledge product corpus. The rest are product/catalog reference copy with no Knowledge card behind them, listed as uncited below.

• does.0 — [source]
• faqs.0.a — [source]
• overview — uncited (reference copy)
• how_to.0 — uncited (reference copy)
• how_to.1 — uncited (reference copy)
• how_to.2 — uncited (reference copy)
• limits.0 — uncited (reference copy)
• limits.1 — uncited (reference copy)
• faqs.1.a — uncited (reference copy)