Skip to content
Benchmark

Refresh enriched posts

Posts
post /v1/posts/enriched/refresh

Starts an asynchronous Enriched post collection only when the canonical post has no completed analysis. An already-analyzed post returns 409 CONFLICT before collection creation or refresh credit reservation. Use the stored Enriched read for existing analysis or Basic refresh for fresh source data.

Authentication

  • ApiKey bearer token

    Send the current Benchmark API key only in the Authorization header.

Request body

  • target EntityTarget required

    A Benchmark entity UUID, platform-native ID, handle, or public URL. Platform can be omitted when the URL identifies it. Link targets require a public HTTPS URL or an existing Benchmark link UUID; HTTP, credentials, local/internal hosts, and non-443 ports are rejected.

Responses

  • 202

    The collection was accepted.

  • 400

    The request failed validation.

  • 401

    The bearer credential is missing or invalid.

  • 402

    The organization needs plan or purchased-credit entitlement, has reached its separate monthly spend cap, or cannot cover the operation within the entitled grace floor.

  • 403

    The key cannot perform this operation.

  • 409

    The request conflicts with current state.

  • 422

    The requested operation is not supported for this entity.

  • 429

    The Cloudflare rate limiter rejected the request.

  • 500

    The request failed without exposing internal diagnostics.

  • 503

    A required service is unavailable.