Skip to content

Add Perso AI dubbing/translation API docs (Python & JavaScript)#143

Open
mingyun-jeong wants to merge 1 commit intoandrewyng:mainfrom
mingyun-jeong:add-pero-api-docs
Open

Add Perso AI dubbing/translation API docs (Python & JavaScript)#143
mingyun-jeong wants to merge 1 commit intoandrewyng:mainfrom
mingyun-jeong:add-pero-api-docs

Conversation

@mingyun-jeong
Copy link

@mingyun-jeong mingyun-jeong commented Mar 18, 2026

What

Add Perso AI video/audio dubbing and translation REST API documentation for Python and JavaScript/TypeScript.

Includes two DOC.md files under content/perso/docs/perso-api/:

  • python/DOC.md — Python guide using requests
  • javascript/DOC.md — JavaScript/TypeScript guide using fetch
  • references/endpoints-detail.md — Detailed endpoint reference table
  • references/error-codes.md — Error code reference

Why

Perso AI provides a REST API for AI-powered video/audio dubbing and translation (upload, translate, lip-sync, download). There is currently no community-contributed documentation for this API in context-hub. These docs cover the full workflow (file upload via Azure SAS tokens, translation, progress polling, download) along with editing, lip sync, usage/quota, and community spotlight endpoints.

Testing

  • npm test passes
  • chub build sample-content/ --validate-only succeeds
  • Manual testing done — verified DOC.md frontmatter follows the required schema (name, description, metadata with languages, versions, revision, updated-on, source, tags)

Notes

  • Both docs share identical API structure and endpoint coverage; they differ only in language-specific syntax (Python requests vs JavaScript fetch).
  • File paths in API responses are relative — docs include guidance to prepend https://perso.ai (Service Domain) rather than the API base URL.
  • Two endpoints (PUT /file/api/upload/video/external, POST /file/api/v1/video-translator/external/metadata) use snake_case request bodies; this is explicitly called out in the docs.

@mingyun-jeong
Copy link
Author

mingyun-jeong commented Mar 23, 2026

@rohitprasad15 Hello! Just a quick follow-up on this PR.
I’m very interested in getting this merged and would be happy to make any necessary adjustments based on your feedback.
Looking forward to hearing from you when you have a moment!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant