Create Meeting
Create a meeting, idempotent within the OAuth client by external_id.
Authentication
Revero-owned OAuth 2.0 Client Credentials. Obtain tokens only from a backend; never place the client secret in browser code.
Request
Your own identifier for this meeting. Creation is idempotent on it: re-sending an identical request returns the same meeting with 200 instead of 201. Re-using it for a DIFFERENT request (other documents, another language) is a 409 external_id_conflict.
Which documents this meeting should produce, by stable profile key. Each becomes one output resource you fetch separately. The profile VERSION is pinned now: publishing a new version later never changes what this meeting produces. Defaults to the transcript alone.
Your authoritative facts about this meeting — a case number, participants, a date. Stored encrypted, returned as its own field, and never rewritten by generation: your system stays authoritative for legal and business facts. Captured ONCE, on the request that creates the meeting, so a later call with the same external_id cannot restate it under documents already generated from it. At most 16384 bytes serialized.
Response
Idempotent replay — a meeting with this external_id already existed and the request matches it. The same resource is returned; nothing was created.
Exactly the facts you supplied at creation. Returned beside the generated documents rather than inside them, and never derived from one — a model cannot promote its own guess into this field.