Just noticed that the Screen Recording API returns a 500 Internal Server Error when attempting to attach custom metadata via the POST /api/v2/screenshare/recordings endpoint. This happens specifically when the payload includes a nested JSON object exceeding 2KB. The standard string fields process without issue, but complex objects fail during the ingestion phase.
Our integration handles high-volume screen captures for compliance audits. Is there a documented size limit for the metadata payload, or should we be batching these attributes differently to avoid server-side serialization failures?