PARTNER DEVELOPER PORTAL · API v1.3

Connect your platform to independent publishers.

The ContentDividend Partner API lets approved organizations authenticate securely, search safe publisher discovery metadata, and submit structured licensing opportunities into ContentDividend. Publisher content rights remain separate from API access.

Start Integration OpenAPI JSON Machine Manifest

1 · DISCOVER

Search publisher records

Find publishers by category, page count, licensing signals, verification, and RAG metadata.

2 · REQUEST

Submit licensing opportunities

Send a structured request into the publisher's normal ContentDividend licensing workflow.

3 · STAY IN BOUNDS

Rights remain controlled

Partner credentials do not grant article bodies, agreements, licenses, payments, or protected-content access.

QUICK START

Four steps to your first Partner API request

ContentDividend issues Partner API credentials only to approved organizations. The secret is shown once and should be stored in your server-side secret manager.

1Receive a partner account and API key from ContentDividend.

2Call GET /v1/partner/status to verify authentication and see your enabled scopes.

3If catalog:read is enabled, search the Publisher Catalog.

4If licensing:intake is enabled, submit a licensing request using an Idempotency-Key.

AUTHENTICATION

Use your Partner API key on the server.

Never expose your Partner API key in browser JavaScript, public GitHub repositories, HTML, mobile app bundles, or customer-visible logs.

GET/v1/partner/status

Verify the key and inspect the scopes ContentDividend has granted your organization.

curl https://app.contentdividend.com/v1/partner/status \
  -H "Authorization: Bearer cdpartner_live_YOUR_SECRET_KEY"

Alternative header: X-ContentDividend-Partner-Key: cdpartner_live_...

SCOPES

Every capability is explicitly granted.

partner:statusAuthenticate and inspect the partner connection.

catalog:readSearch approved Marketplace publisher discovery metadata and publisher detail records.

licensing:intakeSubmit and inspect licensing opportunities created by your own partner organization.

A Partner API key can only use scopes that ContentDividend has granted to its partner organization. Possessing a key does not automatically enable every endpoint.

PUBLISHER CATALOG

Search publishers without exposing protected content.

GET/v1/partner/catalog/search

Filters include q, category, preferred_use, min_registered_pages, verified, content_format, audience, technical_depth, rag_suitability, limit, and offset.

curl "https://app.contentdividend.com/v1/partner/catalog/search?category=Home%20Improvement&verified=1&rag_suitability=high&limit=25" \
  -H "Authorization: Bearer cdpartner_live_YOUR_SECRET_KEY"

GET/v1/partner/catalog/categories

Retrieve the current Marketplace category directory.

GET/v1/partner/catalog/publishers/{site_id}

Retrieve one approved publisher's safe discovery and licensing metadata.

Catalog rule: results describe publishers and licensing availability. They do not contain protected article bodies and do not grant permission to use the content.

LICENSING INTAKE

Turn discovery into a real publisher opportunity.

Use the licensing-intake endpoint after your system has identified a publisher and a buyer wants to request rights. The request enters ContentDividend's existing publisher-controlled workflow.

POST/v1/partner/licensing/requests

curl https://app.contentdividend.com/v1/partner/licensing/requests \
  -X POST \
  -H "Authorization: Bearer cdpartner_live_YOUR_SECRET_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: buyer-opportunity-2026-000123" \
  -d '{
    "site_id": "SITE_ID_FROM_CATALOG",
    "buyer_name": "Alex Morgan",
    "buyer_email": "alex@example.com",
    "buyer_company": "Example AI Company",
    "intended_use": "RAG retrieval",
    "requested_scope": "Selected technical guide pages",
    "budget_range": "$5,000-$10,000",
    "requested_timeline": "30 days",
    "message": "We would like to discuss a one-year content license.",
    "currency": "USD",
    "proposed_budget_cents": 750000,
    "term_months": 12
  }'

GET/v1/partner/licensing/requests

List licensing opportunities submitted by your own partner organization.

GET/v1/partner/licensing/requests/{request_id}

Read the safe status of one request your partner submitted.

IDEMPOTENCY

Safe retries without duplicate opportunities.

Every licensing-intake POST requires an Idempotency-Key. If the exact same request is retried with the same key, ContentDividend returns the original request. Reusing the same key with a different request body returns a conflict.

Recommended: generate one stable idempotency key per buyer opportunity in your own system and retain it alongside the ContentDividend request ID.

ERROR HANDLING

Use standard HTTP status codes.

StatusMeaningWhat your integration should do

400Malformed requestFix the request or missing Idempotency-Key.

401Invalid API keyCheck your server-side credential.

403Scope/key/partner not permittedDo not retry blindly; confirm partner scope or status.

404Publisher/request not foundRefresh catalog data or verify the identifier.

409ConflictUsually an Idempotency-Key reused with a different request body.

422Validation failedCorrect the submitted fields.

429Rate limitBack off and retry later.

RIGHTS & SECURITY BOUNDARY

API access is not a content license.

Partner API authentication only proves the identity and permitted API capabilities of an approved partner.

Catalog access does not grant article rights. Licensing intake creates a request, not an agreement. A separate ContentDividend workflow controls negotiation, agreement approval, payment, publisher license activation, and protected-content access.