Management API & Content Seeding

# The two API surfaces in Optimizely SaaS CMS
#
# ┌─────────────────────────────────────────────────────────┐
# │  Optimizely Graph (GraphQL read API)                    │
# │  Endpoint: https://cg.optimizely.com/content/v2        │
# │  Auth:     epi-single <GRAPH_SINGLE_KEY>               │
# │  Caching:  CDN-cached, ISR-friendly                    │
# │  Purpose:  Content delivery - what your visitors see   │
# └─────────────────────────────────────────────────────────┘
#
# ┌─────────────────────────────────────────────────────────┐
# │  Management API (REST write API)                        │
# │  Endpoint: https://<your-cms>.cms.optimizely.com       │
# │            /preview3/experimental/content              │
# │  Auth:     OAuth2 Bearer token (client_credentials)   │
# │  Caching:  None - always authoritative                 │
# │  Purpose:  Content creation, update, publish, delete   │
# └─────────────────────────────────────────────────────────┘
#
# Graph = read. Management API = write.
# They talk to the same CMS data - Graph reflects what the Management API creates.
# After writing via the Management API, wait for Graph to sync (usually <10s).

// src/lib/optimizely/auth.ts
//
// getManagementToken() obtains an OAuth2 client_credentials token
// and caches it in memory until 30s before it expires.
//
// Required env vars:
//   OPTIMIZELY_CMS_CLIENT_ID     - from CMS Settings > API Clients
//   OPTIMIZELY_CMS_CLIENT_SECRET - from CMS Settings > API Clients

const token = await getManagementToken();

// Use it as a Bearer token in fetch calls to the Management API:
const res = await fetch(`${CONTENT_ENDPOINT}/my-key`, {
  method: "GET",
  headers: {
    Authorization: `Bearer ${token}`,
    "Content-Type": "application/json",
  },
  cache: "no-store",
});

// CONTENT_ENDPOINT:
const CONTENT_ENDPOINT =
  `${process.env.OPTIMIZELY_CMS_URL}/preview3/experimental/content`;

// Create or update a content type via the Management API.
// PUT is idempotent - safe to re-run in CI/CD pipelines.
//
// After this call, the type is available in Visual Builder and in Graph.

const token = await getManagementToken();

await fetch(`${CMS_URL}/api/content/v3/types`, {
  method: "PUT",
  headers: {
    Authorization: `Bearer ${token}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    key:         "QuoteBlock",
    displayName: "Quote Block",
    baseType:    "component",     // or "_page", "_experience", etc.
    properties: {
      quote:      { type: "string",  displayName: "Quote text" },
      authorName: { type: "string",  displayName: "Author name" },
      authorRole: { type: "string",  displayName: "Author role" },
    },
  }),
});

// Equivalent to using contentType() + opti:push, but runs at runtime -
// useful when types are generated dynamically from an external schema.

// Bulk import via NdJSON - POST /api/content/v2/data
// Each line is one JSON object. No trailing commas, no arrays, no pretty-printing.
//
// This is the Content Source API format - used for external data (quotes, products, etc.)
// NOT the Management API for CMS pages. Two different endpoints.

// Build the NdJSON payload:
const items = [
  { locale: "en", key: "quote-1", properties: { quote: "Great rates.", authorName: "Alice" } },
  { locale: "en", key: "quote-2", properties: { quote: "Easy setup.",  authorName: "Bob"   } },
];

const ndjson = items.map((i) => JSON.stringify(i)).join("\n");  // ← never pretty-print

await fetch(`https://cg.optimizely.com/api/content/v2/data`, {
  method: "POST",
  headers: {
    Authorization:  `Basic ${btoa(`${GRAPH_APP_KEY}:`)}`,   // note trailing colon
    "Content-Type": "application/x-ndjson",
  },
  body: ndjson,
  cache: "no-store",
});

// ✓ After sync (~5s), items appear in Graph:
// { QuoteBlock { items { quote authorName } } }