Partner approval
What Genesis needs before it can approve and provision an external Forum integration.
Request access
Email director@genesistudio.com. Integrations are reviewed rather than enabled through public self-service.
Include:
- Your platform name, public website, and technical contact
- The capabilities you need: link generation, partner-signed links, comment ingestion, or creating missing novels
- Expected daily and peak request volume
- How users consent to sharing data on your platform
- How submitted comments are moderated and removed
- The domains and backend systems that will make requests
What Genesis provides
After approval, Genesis creates an integration record with a stable integration slug, display name, status, capabilities, and rate limit. If you use an HTTP endpoint, Genesis also issues an API key beginning with gfi_.
The raw API key is displayed only when it is created or rotated. Copy it immediately to your server-side secret store. The Admin dashboard retains only enough information to identify and verify it; it cannot reveal the original value later.
Capability controls
| Capability | Allows |
|---|---|
| Generate links | POST /api/integrations/link |
| Signed links | Verification of partner-generated JWT/JWE links |
| Post ingestion | POST /api/integrations/posts |
| Create novels | Creating a pending partner-sourced novel when no match exists |
A valid API key does not override a disabled capability. A disabled integration cannot create links or posts.
Requesting changes
Contact Genesis before changing domains, traffic volume, signing keys, or the way you collect data. Genesis may rotate an API key, register a replacement public signing key, change limits, or disable a capability without deleting existing Genesis accounts.