Developers: add generative video to an existing product in one sprint
A developer can add Genuin to a web or mobile product in one sprint: loader, placements, auto login, events, and a webhook, with staging on the sandbox key and production on the live key.
Sprint plan
Non-functional checklist
- Reserve the card footprint to avoid layout shift (see Player card sizes and IAB footprint spec).
- Lazy rendering is on by default; set
data-genuin-lazy="false"only above the fold (see Embed configuration reference). - Consent:
consent: autoreads your CMP; testdeniedrenders without personalization (see Privacy and VPPA: the two-channel data flow). - Keys live in environment variables; rotate under Settings → Developers (see REST API: authentication and keys).
How it runs
This playbook runs as a sequence of proposals, one per step, ordered for your company type; you confirm each one and the 30-day outcome is reported against the plan.
Support. Help is available 24/7 from Brand Control Center and from every page of these docs. Ask in plain language; when a person is needed, an account manager, developer, or Ops engineer joins the same thread and stays on it until it is resolved. Every Business Account owner has this on every plan (see 24/7 Octo-enabled support: how Octo brings in account managers, developers, and Ops).
API & SDK
Access: the calls in the table are the proposed Business Account API (see Business Account API: provisioning, OAuth, and the resource map), authenticated with a key scoped to the account and a role or an OAuth client acting for it; every confirmation in this article becomes a proposal you can approve by API (POST /proposals/{proposalId}:approve). Live today, the server API under /api/thirdparty authenticates with a gn-access-token (see Generate an access token), and Live API today and the Business Account API roadmap maps what is live to what is proposed.
| Call | Purpose |
|---|---|
| POST /accounts/{accountId}/keys | Issue a key with a role scope (sandbox or live) |
| GET /sdk/config | Runtime configuration the Web and mobile SDKs fetch on init (placements, experiences, kit) |
| GET /placements/{placementId}/embed | Embed snippet for the placement (Web SDK attributes pre-filled) |
| POST /sessions | Auto login token exchange: your signed user token for a Genuin session |
| POST /accounts/{accountId}/webhooks | Subscribe to events (proposal.created, placement.published, member.subscribed, revenue.posted, moderation.flagged, …) |
// proposed server SDK (Business Account API)
import { Genuin } from '@genuin/sdk';
const genuin = new Genuin({ apiKey: process.env.GENUIN_KEY });
await genuin.keys.create(accountId, { env: 'live', role: 'developer' });
await genuin.placements.embed(placementId);Live today: Generate an access token · Environments, credentials, and test data · Embed the Genuin Web SDK on your website · Integrate the Genuin iOS SDK.
SDKs: Web SDK 2.0.6 (see Embed the Genuin Web SDK on your website), iOS SDK 2.1.5 (see Integrate the Genuin iOS SDK), Android SDK 2.1.5 (see Integrate the Genuin Android SDK), React Native 3.0.3 (see Integrate the Genuin SDK with React Native apps), and Flutter (see Integrate the Genuin SDK with Flutter apps) render Genuin and sign members in; the Node (@genuin/sdk) and Python (genuin) server SDKs are proposed with Business Account API: provisioning, OAuth, and the resource map.
