Skip to content
NewProduct Q&A: shoppers ask on your product page and get your answers.See how it works
IdukkiIdukki
Rights API

Rights-as-a-service · in private beta

The rights layer every UGC stack is missing.

A read-only API for UGC clearance status and decision history, for ad networks, DSPs and agencies. In private beta, onboarding design partners now. Pricing is not set.

Apply for the beta See the API platform roadmap
Rights API

Rights-as-a-service

Public-comment + consent-form request flow

  • Public-comment + consent-form

    Public-platform-comment request

  • Audit trail and

    Full request,

  • What compliance covers

    GDPR +

Audit trail and signed evidencelive
  • Private beta
    Onboarding design partners now
  • 2
    Request channels live: platform comment + consent form
  • 5
    Outbound webhook events, signed
  • Read-only
    External API with per-partner keys
  • 01

    Public-comment + consent-form request flow

    We ask for rights the way the platforms actually allow it today: a public comment on the original post, plus a public consent form the creator can fill in. No DM automation exists — we’re not claiming it does.

    • Public-platform-comment request
    • Public consent-form capture
    • Manual admin review for edge cases
  • 02

    Audit trail and signed evidence

    Every request, approval and rejection is logged. The dashboard exports a signed evidence record per clearance, as PDF or CSV (beta). Its SHA-256 hash and Idukki signature can be checked later.

    • Full request, approve and reject history
    • Signed evidence PDF or CSV per clearance (beta)
    • History rows are not hash-chained
  • 03

    What compliance covers today

    The audit trail keeps the records GDPR and CCPA requests ask for. There are no regional legal templates and no automated right-to-be-forgotten SLA.

    • GDPR + CCPA + DSA-aligned event logging
    • Region-specific legal templates: not built
    • Automated takedown SLA: not built
  • 04

    External, authenticated API access

    Partners call read-only endpoints with a per-partner API key that Idukki issues. Each key reads one business’s clearance status and decision history.

    • Per-partner API keys, issued by Idukki
    • Clearance status by post, or as a list
    • Paginated audit history
  • 05

    Outbound webhooks

    A merchant can send signed events to an https endpoint: ugc.created, ugc.approved, rights.granted, rights.revoked and order.attributed. Each POST carries an X-Idukki-Signature header.

    • rights.granted and rights.revoked live
    • HMAC-SHA256 signature on every POST
    • rights.expired is not a webhook event yet
  • 06

    Human review for edge cases

    The comment and consent-form flow misses some cases, like disputed ownership or a silent creator. Those are decided by hand and logged.

    • Manual approve or reject, with who decided
    • Logged with the rest of the history
    • No automated fallback
  1. Research
  2. Building
  3. Beta
  4. Live
Get a sandbox key as a design partner

Get a sandbox key as a design partner

Private beta is onboarding ad networks, DSPs, agencies and platform teams that move UGC at scale. Tell us what you need. It shapes the build order.

  • Direct input into the API contract
  • A sandbox key for the read-only API
  • Pricing is not set yet

Cloudflare bot-protection

No spam. We never sell your data. Privacy policy

We read every message and reply by email. If it fits, we suggest a call.