Solo Creator

The Solo Creator flow is the right integration when each piece of content has exactly one performer and that performer is the uploader. OnlyFans-style creator platforms, clip stores, fan sites, and personal video pages all fit this pattern.

What you get

• A verified-identity record for every creator who uploads explicit content on your platform
• A per-depiction audit trail tying each piece of content to that record (28 CFR 75.2)
• Easy2257 named as the Custodian of Records on every 2257 statement — your platform never stores government IDs
• The same verification covers the creator everywhere they upload — verify once, compliant on every Easy2257 partner platform

When to use this vs. Productions

Use Solo Creator when content involves only the uploader. Use Productions when content involves additional performers and needs per-scene consent collection.

Integration shape

Four endpoints + three webhooks. Full code in the Quickstart.

1. POST /v1/solo-accounts            ─►  status: pending_id_verification
                                          + onboardingUrl

   redirect creator (top-level nav, NOT iframe — needs camera)

2. solo_account.verified webhook     ─►  grant upload access

3. POST /v1/solo-accounts/{id}/content   for every upload
                                          (always send externalContentId)

4. DELETE /v1/solo-accounts/{id}/content/{externalContentId}
   on every takedown                ─►  fires content_log.deleted webhook
                                          for cross-platform mirrors

Three things to get right

1. Always send externalContentId on POST. It's optional in the schema but it's the only way to address the depiction later for takedowns. Without it your content is logged but not removable via the API.
2. Wait for solo_account.verified before allowing uploads. The intermediate subscribed_pending_id status means "paid but not yet ID verified" — do not unlock content there. The webhook fires only after both Stripe payment AND ID verification complete.
3. Treat content_log.deleted as authoritative. When Easy2257 fires it (creator-initiated removal via the public portal, or a request you didn't see), remove the content from your CDN within 48 hours per the TAKE IT DOWN Act, even if you didn't initiate the takedown yourself.

Reference

• Quickstart — copy-paste cURL/Node/Python/PHP
• Solo Accounts API — endpoint reference
• Webhook Events — payload shapes
• Webhook Signatures — verification code