Update Meeting Extraction Settings
PUT /org/settings/docs/meetings
Replace the meeting extraction settings.
Declared BEFORE PUT /org/settings/docs/{scope}: the other way round the
parameter route matches first, binds scope to “meetings”, and the Literal
rejects it - a 422 on a route that exists.
Every block defaults to EMPTY, so omitting one is not the same as leaving it alone. Read the current settings, change what you need, send the whole object back.
Authorizations
Parameters
Header Parameters
Request Body required
Mirrors campaign_builder.schemas.settings.UpdateMeetingExtractionSettingsRequest.
Every field defaults to an EMPTY block, and the app treats the request as the new state for each scope it receives - so omitting a scope is not the same as sending it empty. Send the whole object you read back.
The nested blocks are the app’s own models; see the module docstring.
object
Meetings with an existing customer.
object
Org-defined custom fields to extract
Org-defined field to extract from meeting transcripts.
object
Output type expected from the extractor
Instruction describing what to extract
Stable key for the extracted field
Display label shown in admin and downstream UI
Vocabulary terms, acronyms, and product names to recognize
Vocabulary term or acronym with optional meaning/explanation.
object
Optional explanation of what the term means or why it matters
A term, acronym, or phrase the extractor should recognize
Structured outputs that should always be extracted
Signals and topics the extractor should prioritize
Internal meetings - every attendee is on an internal domain.
object
Org-defined custom fields to extract
Org-defined field to extract from meeting transcripts.
object
Output type expected from the extractor
Instruction describing what to extract
Stable key for the extracted field
Display label shown in admin and downstream UI
Vocabulary terms, acronyms, and product names to recognize
Vocabulary term or acronym with optional meaning/explanation.
object
Optional explanation of what the term means or why it matters
A term, acronym, or phrase the extractor should recognize
Structured outputs that should always be extracted
Signals and topics the extractor should prioritize
Company identity the extractor grounds on: canonical name, internal domains, aliases.
object
Known brand, alias, or product names that resolve to canonical entities
Alias, brand, or product name that should resolve to a canonical entity.
object
Brand, alias, or product term as it may appear in transcripts
Canonical company or product name this alias resolves to
Optional explanation of the relationship or how this alias should be interpreted
Canonical internal company name that should be used in summaries and task interpretation
Email domains that identify internal attendees
Rules that explain how participant and domain evidence should be interpreted
Meetings with a prospect.
object
Org-defined custom fields to extract
Org-defined field to extract from meeting transcripts.
object
Output type expected from the extractor
Instruction describing what to extract
Stable key for the extracted field
Display label shown in admin and downstream UI
Vocabulary terms, acronyms, and product names to recognize
Vocabulary term or acronym with optional meaning/explanation.
object
Optional explanation of what the term means or why it matters
A term, acronym, or phrase the extractor should recognize
Structured outputs that should always be extracted
Signals and topics the extractor should prioritize
Applied to every meeting, on top of the per-scope block.
object
Org-defined custom fields to extract
Org-defined field to extract from meeting transcripts.
object
Output type expected from the extractor
Instruction describing what to extract
Stable key for the extracted field
Display label shown in admin and downstream UI
Vocabulary terms, acronyms, and product names to recognize
Vocabulary term or acronym with optional meaning/explanation.
object
Optional explanation of what the term means or why it matters
A term, acronym, or phrase the extractor should recognize
Structured outputs that should always be extracted
Signals and topics the extractor should prioritize
Responses
200
Successful Response
object
An open envelope for one settings block, document or brand artefact.
OPEN on purpose. These surfaces are configuration and generated content, and both grow: a new toggle on a settings block or a new field on a generated document must reach a caller on the day it ships, not on the day somebody remembers to widen a mirror. A closed response model here would silently DROP the new key, which reads to the caller as “the product does not have that setting”.
The request side is the opposite and is mirrored exactly - see the module docstring for why the asymmetry is deliberate.
object
422
Validation Error