JoggAI icon

JoggAI

Interact with the JoggAI API to create and manage AI videos
Join our community

Actions22

Overview

The node interacts with the JoggAI API to retrieve a list of library voices filtered by specific criteria. It is useful for scenarios where you want to programmatically obtain voice options available in the JoggAI voice library, such as when building AI-powered applications that require text-to-speech capabilities or voice selection based on user preferences.

Practical examples include:

  • Fetching voices filtered by language and gender to present users with relevant voice choices.
  • Paginating through a large set of voices to display manageable chunks in an application UI.
  • Automating voice selection workflows in content creation pipelines.

Properties

Name Meaning
Filters Filter the list of voices by specific criteria:
- Age: No Select, Young, Middle Aged, Old
- Gender: No Select, Male, Female
- Language: No Select, English, Filipino, French, German, Hindi, Indonesian, Italian, Japanese, Korean, Malay, Portuguese, Russian, Spanish, Thai, Vietnamese, Arabic, Greek, Turkish, Slovenian, Croatian, Romanian, Simplified Chinese, Bengali, Urdu, Hungarian, Traditional Chinese, Polish, Cantonese, Danish, Malayalam, Tamil, Telugu, Czech, Hebrew, Zulu, Swedish, Lithuanian, Dutch, Flemish, Norwegian, Finnish, Bulgarian, Latvian, Ukrainian, Mongolian, Persian, Odia, Assamese, Kannada, Tagalog, Amharic, Serbian, Slovak, Swahili
Pagination Set the page and number of results to return:
- Page: The page number to retrieve (minimum 1)
- Page Size: The number of results to return per page (minimum 1)

Output

The output is a JSON array where each item represents a voice from the JoggAI library matching the specified filters and pagination settings. Each voice object typically contains details such as voice ID, name, language, gender, age group, and other metadata describing the voice characteristics.

The node does not output binary data.

Dependencies

  • Requires an API key credential for authenticating with the JoggAI API.
  • The node depends on the JoggAI service being accessible and the API key having permissions to query the voice library.
  • No additional environment variables are explicitly required beyond the API key configuration.

Troubleshooting

  • Common issues:

    • Invalid or missing API key will cause authentication failures.
    • Requesting pages beyond the available range may return empty results.
    • Using unsupported filter values might result in no voices returned.

  • Error messages:

    • Errors related to network connectivity or API unavailability.
    • "Request failed" errors indicating issues with the API call.

  • Resolutions:

    • Verify the API key is correctly configured and active.
    • Check filter values against supported options.
    • Adjust pagination parameters to valid ranges.
    • Ensure stable internet connection and API endpoint accessibility.

Links and References

Discussion