July 2026
Segment rewrites
Transcript corrections gain a structural primitive:segment_rewrite on POST /v1/videos/{video_id}/corrections replaces any run of segments with new ones. Merge mangled ASR lines, split them, or delete the range with an empty replacements array. Timestamps repair automatically; pin start/end per replacement where the exact time matters. Anchored like line edits, free like every correction, withdrawable via DELETE /v1/corrections/segment-rewrites/{id}.Read the Transcripts coding agent reference →Numeric-seconds timestamps on evidence rows
Mention and recommendation timestamps are now numeric. All changes are additive; nothing was removed or renamed.- New fields: mention rows, recommendation rows, and
details=fullenrichment items carrystart_seconds/end_seconds(integer seconds;0means the full episode, no specific moment; null when the source string is null). Webhook alert payloads gainappearance.timestampSeconds. - Sentiment consistency: recommendation rows gain
sentiment_score, the same raw[-1, 1]number mention rows already expose. - Deprecations: the
start_timestamp/end_timestampMM:SSstrings and the recommendationsentimentnumber are deprecated in the OpenAPI spec. They keep working until a dated removal is announced here, per the versioning and deprecation policy. Migrate reads to the seconds fields andsentiment_score.
Webhook secret lifecycle on v1
Pure-API consumers can now verify webhook signatures end to end, with zero-downtime secret rotation.- One-time secret return: monitor create/PATCH responses include
monitor.webhookSecretexactly once, when the response newly enables webhook signing. Reads exposewebhookSecretSetandwebhookSecretHintonly. - Rotation with overlap:
POST /v1/monitors/{id}/webhook-secret/rotatereturns a fresh secret once withpreviousSecretExpiresAt. For 24 hours, deliveries carry bothX-Arcmira-Signature(new) andX-Arcmira-Signature-Previous(old). - Explicit re-enable: rotation never re-enables an auto-disabled webhook;
PATCH { "notifyWebhook": true }is the deliberate re-enable step and clears the failure counter.
Community Review across every surface
Every result-bearing surface now accepts typed feedback, and submissions are readable back.- 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), andsearch(single-result resolutions, withobserved_rank). - Readback:
GET /v1/feedback/{feedback_id}returns your submission with per-correction review status, frompending_reviewthroughappliedandreverted. - Typed
suggested_change: documented as a union perissue_typein the OpenAPI spec; existing loose submissions continue to validate. - Alert public IDs: alert history rows carry
mention_id(men_*) andentity_id(ent_*), joining directly against mention rows and entity reads.
Monitors API rename
The API resource is now Monitors:/v1/monitors endpoints, scope monitors:write, and payload fields monitorId, monitor_id, and monitor_name. Prior resource names for this surface are retired; rows minted before the rename keep resolving.Read the Monitors guide →Transcripts and Transcriptions (v1.2.0)
Premium transcripts arrived: diarized, speaker-identified, entity-annotated, and community-correctable.- Read:
GET /v1/transcripts/{video_id}with permanent per-video unlocks (?unlock=true), priced in rows per 15-minute block. - Generate:
POST /v1/transcriptionssubmits any public YouTube video; poll withRetry-After,etaSeconds, andnextPollSeconds. - Correct: unified
POST /v1/videos/{video_id}/correctionscovers line edits, speaker edits, speaker identifications, and entity tags, with idempotent replay, per-video sequence numbers (412withexpectedSeq), and anchor validation (409withcurrentRevision). - Transcript surfaces are premium-only: videos without a premium analysis return a preliminary scan with detected entity counts instead of segments.
Community Review
Structured feedback became the documented path for correcting the index.POST /v1/feedbackaccepts 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)
The commercial evidence layer went live for Pro+ plans.- Recommendations API:
GET /v1/recommendationsandGET /v1/entities/{id}/recommendations, filtered bymention_class(ad_read/endorsement/mention/all),channel_id,min_confidence, dates, andinclude_disputed. Public IDs use thecom_*scheme. - Channel sponsors:
GET /v1/channels/{channel_id}/sponsorswithmin_ad_reads(default 3) andstatusfilters, built on the recurring-sponsor rules behind Arcmira’s internal advertiser dashboards. - Entity discovery:
GET /v1/entities/search, fuzzy, ranked, free, withhas_recommendations_data. - Mention enrichment:
GET /v1/mentions?details=fullattaches matching commercial rows (verbatim quotes, promo codes, offers, confidence). - Summaries and teasers:
recommendations_summaryon entity reads;sponsor_countvisible to every caller on channel reads. - Gating: new
recommendations:readscope,recommendations_api_enabledon/v1/me, and error codesrecommendations_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/lookupresolves a name (and optionaltype) to a canonicalent_<id>, following merge chains;merged_from_idmarks aliases.GET /v1/entities/{id},GET /v1/entities/{id}/mentions, andGET /v1/mentionswith entity, channel, sentiment, appearance, date, and free-text filters.- Non-person appearance routes return
400 appearances_person_only; only/v1/people/{slug}/appearancesis documented. X-Request-Id,X-Arcmira-Version, andRateLimit-*headers stable across all v1 responses.
Initial public API surface (v1.0.0)
The first public release of the Arcmira API.- Search and entity reads; person appearances and per-entity related lists.
- Monitors and trackers CRUD with idempotency, plus
/alertsrecent delivery history. - Cursor pagination (
data/has_more/next_cursor), a stable error envelope, andX-Request-Idcorrelation. - Scoped API keys:
read,monitors:write,trackers:write.