Collections

Collections let you group related content, monitor performance, and run narrative analysis. Use them to organize intelligence workstreams, power dashboards, or feed downstream automation.

Core endpoints

• GET /collections — list collections you can access.
• POST /collections — create a new collection with optional seed content.
• GET /collections/{collectionId} — retrieve metadata and configuration.
• GET /collections/{collectionId}/content — fetch all items in a collection.
• GET /collections/{collectionId}/aggregate-engagement — aggregate engagement metrics.
• GET /collections/{collectionId}/daily-engagement — time-series engagement.
• GET /collections/{collectionId}/authors — top authors and contributors.
• POST /emergent-collections — discover automatically generated narratives.
• GET /emergent-collections/{collectionId} — inspect a specific emergent collection.

List collections

$
curl --request GET "https://app.outtake.ai/api/v1/collections" \
>
  --header "Authorization: Bearer YOUR_API_KEY"

Pagination parameters in the response help you iterate through long lists. Store collectionId values so you can fetch detailed analytics later.

Create and seed a collection

$
curl --request POST "https://app.outtake.ai/api/v1/collections" \
>
  --header "Authorization: Bearer YOUR_API_KEY" \
>
  --header "Content-Type: application/json" \
>
  --data '{
>
    "description": "Artificial Intelligence Scams",
>
    "contentIds": ["9ac8149c-5e1a-4f61-bfd0-16ca8f4bb1a0"]
>
  }'

Outtake automatically enriches new collections by pulling in similar items. You can add more content IDs over time or curate the set directly in the dashboard.

Monitor engagement

$
# Aggregate engagement totals
>
curl --request GET "https://app.outtake.ai/api/v1/collections/123e4567-e89b-12d3-a456-426614174000/aggregate-engagement" \
>
  --header "Authorization: Bearer YOUR_API_KEY"
>
>
# Daily trends
>
curl --request GET "https://app.outtake.ai/api/v1/collections/123e4567-e89b-12d3-a456-426614174000/daily-engagement" \
>
  --header "Authorization: Bearer YOUR_API_KEY"
>
>
# Leading authors
>
curl --request GET "https://app.outtake.ai/api/v1/collections/123e4567-e89b-12d3-a456-426614174000/authors" \
>
  --header "Authorization: Bearer YOUR_API_KEY"

Use these endpoints to feed dashboards or alerting systems. For example, compare daily engagement against the prior week to highlight accelerating narratives.

Retrieve collection content

$
curl --request GET "https://app.outtake.ai/api/v1/collections/123e4567-e89b-12d3-a456-426614174000/content" \
>
  --header "Authorization: Bearer YOUR_API_KEY"

Store the returned content IDs when you need to fetch raw assets or annotate items in downstream tooling.

Emergent narratives

$
# Yesterday's emergent narratives
>
curl --request POST "https://app.outtake.ai/api/v1/emergent-collections" \
>
  --header "Authorization: Bearer YOUR_API_KEY" \
>
  --header "Content-Type: application/json" \
>
  --data '{"createdAt": { "type": "option", "option": "yesterday" }}'
>
>
# Last 7 days
>
curl --request POST "https://app.outtake.ai/api/v1/emergent-collections" \
>
  --header "Authorization: Bearer YOUR_API_KEY" \
>
  --header "Content-Type: application/json" \
>
  --data '{"createdAt": { "type": "option", "option": "lastWeek" }}'

Follow up with GET /emergent-collections/{collectionId} once you identify a trend you want to monitor closely.

Best practices

• Keep collection descriptions action-oriented so collaborators understand why the set exists.
• Use collection IDs as foreign keys in your analytics stack to join engagement, author, and content tables.
• Schedule periodic pulls of aggregate and daily engagement, then store snapshots to measure growth over time.
• Combine Collections with the Search and Takedown Analytics guides to build a unified narrative intelligence workflow.

See the API reference for field-level schemas, pagination rules, and error formats.