Changelog

​

Community Review across every surface

• New feedback types on POST /v1/feedback: monitor_alert (dispute a fired alert by row ID), appearances (person_not_present, wrong_person, wrong_appearance_role), and search (single-result resolutions, with observed_rank).
• Readback: GET /v1/feedback/{feedback_id} returns your submission with per-correction review status, from pending_review through applied and reverted.
• Typed suggested_change: documented as a union per issue_type in the OpenAPI spec; existing loose submissions continue to validate.
• Alert public IDs: alert history rows carry mention_id (men_*) and entity_id (ent_*), joining directly against mention rows and entity reads.

​

Transcripts and Transcriptions (v1.2.0)

• Read: GET /v1/transcripts/{video_id} with permanent per-video unlocks (?unlock=true), priced in rows per 15-minute block.
• Generate: POST /v1/transcriptions submits any public YouTube video; poll with Retry-After, etaSeconds, and nextPollSeconds.
• Correct: unified POST /v1/videos/{video_id}/corrections covers line edits, speaker edits, speaker identifications, and entity tags, with idempotent replay, per-video sequence numbers (412 with expectedSeq), and anchor validation (409 with currentRevision).
• Transcript surfaces are premium-only: videos without a premium analysis return a preliminary scan with detected entity counts instead of segments.

​

Community Review

• POST /v1/feedback accepts notes, corrections, merge suggestions, and classification review requests against the exact query you ran.
• Public submissions create review items only; accepted changes are applied by reviewers, and submitter reputation accrues to the account and API key over time.
• Commercial submissions use the same access as the data being reviewed: Pro+ plus recommendations:read.

​

Commercial intelligence (v1.1.0)

• Recommendations API: GET /v1/recommendations and GET /v1/entities/{id}/recommendations, filtered by mention_class (ad_read / endorsement / mention / all), channel_id, min_confidence, dates, and include_disputed. Public IDs use the com_* scheme.
• Channel sponsors: GET /v1/channels/{channel_id}/sponsors with min_ad_reads (default 3) and status filters, built on the recurring-sponsor rules behind Arcmira’s internal advertiser dashboards.
• Entity discovery: GET /v1/entities/search, fuzzy, ranked, free, with has_recommendations_data.
• Mention enrichment: GET /v1/mentions?details=full attaches matching commercial rows (verbatim quotes, promo codes, offers, confidence).
• Summaries and teasers: recommendations_summary on entity reads; sponsor_count visible to every caller on channel reads.
• Gating: new recommendations:read scope, recommendations_api_enabled on /v1/me, and error codes recommendations_not_enabled, invalid_feedback_request, channel_not_found, recommendation_not_found. Commercial rows bill at a premium per-row rate.

​

Entity and mentions surface (v1.0.1)

• GET /v1/entities/lookup resolves a name (and optional type) to a canonical ent_<id>, following merge chains; merged_from_id marks aliases.
• GET /v1/entities/{id}, GET /v1/entities/{id}/mentions, and GET /v1/mentions with entity, channel, sentiment, appearance, date, and free-text filters.
• Non-person appearance routes return 400 appearances_person_only; only /v1/people/{slug}/appearances is documented.
• X-Request-Id, X-Arcmira-Version, and RateLimit-* headers stable across all v1 responses.

​

Initial public API surface (v1.0.0)

• Search and entity reads; person appearances and per-entity related lists.
• Monitors and trackers CRUD with idempotency, plus /alerts recent delivery history.
• Cursor pagination (data / has_more / next_cursor), a stable error envelope, and X-Request-Id correlation.
• Scoped API keys: read, monitors:write, trackers:write.