Get started
Connect an approved community to Genesis Forums with consent-based account linking and attributed comment ingestion.
What you can build
Genesis supports three integration capabilities, enabled separately per partner:
- Account linking sends a member from your platform to Genesis, shows them exactly what will be linked, and records their consent.
- Comment ingestion imports comments, including threaded replies, into the canonical Forum discussion for a novel. Comments retain your platform's source label and can later resolve to the member's Genesis profile.
- Novel ingestion creates partner-sourced novels with their cover, author, synopsis, and reading metadata, and keeps that metadata up to date.
Every request uses the base URL https://forum.genesistudio.com. There is no separate sandbox host; you test with a Genesis-issued test integration against the same host. See Test and go live.
Get access
Email info@genesistudio.com with your platform name, public website, technical contact, the capabilities you need, expected volume, and how your users consent to sharing their identity and comments. Integrations are reviewed rather than self-service.
After approval, Genesis creates an integration with a stable slug, display name, capabilities, and rate limit, and issues an API key beginning with gfi_. The raw key is delivered once to your technical contact; store it immediately in your server-side secret store, since it cannot be read back later.
| 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 | POST /api/integrations/novels and automatic novel creation during post ingestion |
Email the same address before changing traffic volume, signing keys, or the way you collect data.
Authentication
Send the key in the Authorization header on every API request:
Authorization: Bearer gfi_your_secret_key
Content-Type: application/json
API keys belong only in a trusted backend. Do not embed them in browser JavaScript, mobile applications, URLs, analytics, or client-visible error messages. A missing or invalid key returns 401; a disabled integration or capability returns 403. Neither should be retried automatically.
Rotating a key immediately invalidates the previous one, so deploy replacements as one coordinated change. If a key may have leaked, rotate first and investigate second.
Idempotency
Every mutation also requires an Idempotency-Key header. It must contain 8–200 characters from A-Z, a-z, 0-9, ., _, :, or -.
Use a stable event identifier, such as comment:987654:v1. Retry a timed-out request with the same key. Use a new key only for a genuinely new operation. Reusing a key with different input is rejected rather than silently changing the original operation.