Hi all,
We’ve built a production integration on the V4 API (Adobe IMS OAuth, SPA/PKCE credential) that uploads renders from Premiere Pro, manages version stacks and shares, and syncs comments back into the editor as timeline markers. All of that works great.
The one thing we can’t do is read or write custom metadata fields. Our reviewers set a custom field (“Review Status”: Editing / Needs Review / Needs Revision / Approved / Rejected) in the Frame.io web app, and we want our integration to read it so editors see the reviewer’s decision without leaving Premiere.
What we’re hitting:
GET /v4/accounts/{account_id}/metadata/field_definitionsreturns 403 — “Please migrate your account to account level metadata”- The project- and workspace-scoped field-definition routes all return 404
GET /v4/accounts/{account_id}/files/{file_id}/metadata(with theapi-version: experimentalheader) returns only system fields — custom fields never appear, so there’s no way to obtain field or option IDs
So the field is fully functional in the web UI, but invisible to the API for our account.
We contacted support and were told account-level metadata is rolling out in phases and can’t be switched on per-account on request. We understand there’s a priority list for the migration — we’d like to formally request that our account be added to it. This is the single blocker for a feature our clients would use daily, and we’re happy to provide any account details, act as an early tester, or report back on the migration experience if that helps.
Two follow-up questions:
- What’s the right channel to get on the priority list if this forum isn’t it — and is there anything you need from us beyond the account ID?
- In the meantime, is there any supported way to read custom field values on files for a non-migrated account (experimental header, older endpoint, anything)?
Email attached to account is team@maximizehq.com