VN Template Metadata API
Budget: ₹600 – ₹1,500 INR
I’m looking for a Python-based service that, when given a vn template UUID, returns all key metadata for that video template in clean JSON. The response must include (at minimum) the template’s author, usage count, name, total duration, individual footages, cover-image URL, video preview URL, like count and any other native fields that come with the source data.
Every endpoint has to be authenticated, so please wire in a simple token or JWT flow that I can later swap out for my production identity provider. The API will speak JSON exclusively for both requests and responses.
I’m flexible on the exact Python framework—as long as the code is readable and well-documented—but FastAPI or Flask would keep things straightforward.
Deliverables
• Fully working Python codebase with the endpoint(s) that accept a UUID and return the metadata described above
• Authentication layer applied to all routes
• JSON-formatted OpenAPI/Swagger documentation so I can explore and test the calls immediately
• A short README explaining setup, environment variables and how to run a quick local test
Once the core endpoint is stable, there will likely be follow-on tasks for additional analytics fields and batch look-ups, so clean structure and clear naming are important from the start.
Every endpoint has to be authenticated, so please wire in a simple token or JWT flow that I can later swap out for my production identity provider. The API will speak JSON exclusively for both requests and responses.
I’m flexible on the exact Python framework—as long as the code is readable and well-documented—but FastAPI or Flask would keep things straightforward.
Deliverables
• Fully working Python codebase with the endpoint(s) that accept a UUID and return the metadata described above
• Authentication layer applied to all routes
• JSON-formatted OpenAPI/Swagger documentation so I can explore and test the calls immediately
• A short README explaining setup, environment variables and how to run a quick local test
Once the core endpoint is stable, there will likely be follow-on tasks for additional analytics fields and batch look-ups, so clean structure and clear naming are important from the start.