Enterprise B2B API: embed activation after pilot proof

Who you are and what you normally do

You run platform engineering at an MCN, affiliate enabler, creative automation product, or brand with internal tooling. Your operators already have affiliates and a sample constraint: they need an activation lane, not another generic AI video button.

Pilot first: prove sample-constrained activation with a no-integration Hosted/Collab pilot before embedding. Then ship the API as an embedded activation layer inside your creator portal or CRM, with forward-deployed engineering, not “headless logistics” in isolation.

The pain at scale

Building on a UI-first product breaks down when you need headless scale:

• Manual Digital Sample setup does not map to your job orchestration or multi-tenant architecture.
• Generic AI-generated integration code invents fields, skips credit checks, or uploads seeds in the wrong order.
• Email-based status updates do not fit server-driven pipelines; you need webhooks and idempotent job IDs.
• Compliance and partner diligence slow down if API docs are scattered or informal.

Impact: quarters lost on brittle scrapers, failed renders in production, and engineering time spent reverse-engineering instead of shipping features.

How YPH fixes it for your workflow

YPH exposes a stateless Public API (https://api.yourproducthere.ai/v1) documented for humans and machines. Current /v1 supports the Actor Replacement workflow (approved product video → creator-specific executions). Generative API resources and a technical Campaign entity are not part of the current contract:

AI-ready docs: Full API guides, Enterprise installation & asset quality (beta), OpenAPI reference, and llms.txt skills context are built for Cursor, Claude, and other assistants. Paste or attach llms.txt so the model follows real validation limits (video length, FPS, render width) and the canonical sample → seed → actor → swap flow.

Out of scope today (app-only): Collab invites and Proof-of-Post. Plan a hybrid: API for render logistics; app or future endpoints for affiliate distribution when you need them.

Step-by-step tutorial

1. Request API activation for your organization (partner intake or company credentials).
2. Sign in, open Developer in the app sidebar, and generate an API key (yph_sk_live_…). Store it in your secrets manager; the full secret is shown once.
3. Health check: GET /health (no auth) against https://api.yourproducthere.ai/v1.
4. Verify account: GET /account with Authorization: Bearer YOUR_API_KEY. Confirm apiAccessEnabled and credit balance.
5. Create a Digital Sample: POST /digital-samples with title and optional render prompts.
6. Upload seed video: presigned POST …/seed/upload-url → PUT file → POST …/seed/register, or PATCH with a public seedVideoUrl for HTTPS ingest.
7. Create an Actor: POST /actors with HTTPS URLs for face, body, and voice assets (YPH ingests into private storage).
8. Queue Insta Swap: POST /digital-samples/{id}/insta-swaps with actorId; credits charge on queue.
9. Complete the loop: poll swap status or register POST /webhooks for insta_swap.completed / insta_swap.failed.

Build faster with AI: In Cursor or Claude, add @llms.txt or link https://docs.yourproducthere.ai/llms.txt to your project rules, then ask for a client in your stack (Node, Python, Go). Cross-check generated calls against the workflow guide and the enterprise installation guide for beta asset constraints.

Next step for diligence: Company credentials · API documentation · Enterprise installation guide