Accessing Your First Translated Story Results
Let’s examine how to retrieve your completed translation using Python:Integrating Translation Results into Your Workflow
Once you’ve retrieved your translation results, you can integrate them into your content pipeline in numerous ways:Best Practices for Optimal Results
To maximize the effectiveness of your translated story assets, consider these professional recommendations:- Content Deployment Strategy: Plan how you’ll use both the complete story audio and the separated dialogue audio in your applications. The separate dialogue track enables more sophisticated audio mixing and dynamic content presentation.
- Transcript Processing: When working with the transcript data, consider extracting specific dialogue segments for interactive applications or for creating synchronized subtitles for media players.
- Asset Archiving: Implement a structured archiving system for your translated assets that preserves the relationships between audio files and transcript data across multiple languages.
- Quality Assessment: Review a sample of the translated content against the original to ensure the translation maintains the intended tone and meaning of your story.
- Error Handling: Implement robust error handling in your integration code to gracefully manage situations where certain assets might be temporarily unavailable.
Authorizations
The x-api-key
is a custom header required for authenticating requests to our API. Include this header in your request with the appropriate API key value to securely access our endpoints. You can find your API key(s) in the 'API' section of our studio website.
Path Parameters
The unique identifier for the run, which was generated during the creation process and returned upon task completion.
1
, 2
, 3
, 4
, 5
, 6
, 7
, 8
, 9
, 10
, 11
, 12
, 13
, 14
, 15
, 16
, 17
, 18
, 19
, 20
, 21
, 22
, 23
, 24
, 25
, 26
, 27
, 28
, 29
, 30
, 31
, 32
, 33
, 34
, 35
, 36
, 37
, 38
, 39
, 40
, 41
, 42
, 43
, 44
, 45
, 46
, 47
, 48
, 49
, 50
, 51
, 52
, 53
, 54
, 55
, 56
, 57
, 58
, 59
, 60
, 61
, 62
, 63
, 64
, 65
, 66
, 67
, 68
, 69
, 70
, 71
, 72
, 73
, 74
, 75
, 76
, 77
, 78
, 79
, 80
, 81
, 82
, 83
, 84
, 85
, 86
, 87
, 88
, 89
, 90
, 91
, 92
, 93
, 94
, 95
, 96
, 97
, 98
, 99
, 100
, 101
, 102
, 103
, 104
, 105
, 106
, 107
, 108
, 109
, 110
, 111
, 112
, 113
, 114
, 115
, 116
, 117
, 118
, 119
, 120
, 121
, 122
, 123
, 124
, 125
, 126
, 127
, 128
, 129
, 130
, 131
, 132
, 133
, 134
, 135
, 136
, 139
, 140
, 141
, 142
, 143
, 144
, 145
, 146
, 147
, 148
, 149
, 150
Query Parameters
The optional include_transcript
query parameter determines whether the detailed transcript data should be included in the response.
Response
Successful Response