Hi Team,
I hope you’re doing well. I’m working on an internal automation project that needs to generate share/review links programmatically for live Frame.io projects. According to the documentation, the public API endpoint for creating share links is still in the v2 “Review Links” API (POST /v2/assets/{asset_id}/review_links). I’ve set up a Personal Access Token (PAT) to hit the v2 endpoints, and I can list teams/projects that exist in the classic environment.
My issue: the project I need to share lives in the newer (Next) interface—its URL is:
lua
https://next.frame.io/project/0331963b-9c93-4a8f-a15a-d48a021a8b8e
When I call GET /v2/projects/0331963b-9c93-4a8f-a15a-d48a021a8b8e with my PAT, I get a 404 response, even though the project is visible and active in Next. That prevents me from retrieving root_asset_id and creating the review link. It seems this project (and others launched in Next) aren’t mirrored into the v2 API for our account yet, so the legacy endpoints don’t see them.
Could you help with any of the following?
-
Enable or expose that project (and future Next projects) through the classic/v2 API so we can create review links programmatically today.
-
Let me know if there is a newer/v4 API path for creating share links that we can use instead.
-
Provide any guidance on the supported approach for automating share link creation in the Next environment.
We’d love to keep the workflow inside Frame.io so our operators can send customer links automatically once a project is uploaded. Any direction or API access you can grant would be incredibly helpful.
Thanks so much for your time and support! I’m happy to provide additional details or test token IDs privately if needed.
Best regards,
Sam
