HappyOyster-Acting-Enter Travel API Reference
The client uses the ticket to create an actual Travel and obtain the RTC join configuration, the Acting capability version, and the player aspect ratio. A successful call creates the Travel.
Scope
The client uses the ticket to create an actual Travel and obtain the RTC join configuration, the Acting capability version, and the player aspect ratio. Before calling, confirm the following:
- Authentication: The primary API Key is not required; the
ticketcompletes the enter-room validation. For how to obtain it, see Obtain authentication credentials. - Prerequisites: The
ticketis obtained from Get Travel Credential, unexpired and unused, and its World status isready. - Caller: Called by your client.
HTTP request
Singapore
POST https://{WorkspaceId}.ap-southeast-1.maas.aliyuncs.com/api/v2/apps/happyoyster-1.0-acting/openapi/v1/travels/enter-travel
Replace {WorkspaceId} with your actual Workspace ID.
US (Virginia)
POST https://{WorkspaceId}.us-east-1.maas.aliyuncs.com/api/v2/apps/happyoyster-1.0-acting/openapi/v1/travels/enter-travel
Replace {WorkspaceId} with your actual Workspace ID.
Request parameters | Enter travel (client) |
Content-Type Request content type. This parameter must be set to | |
Authorization API Key authentication. The primary API Key is not required; either the primary or a temporary API Key can call it.
| |
Request Body | |
ticket An unexpired, unused single-use credential obtained from Get Travel Credential. Reusing the same |
NoteActing does not consume maxExperienceTimeSec; do not pass it. If an invalid tier is still passed, 400000 is returned before model routing.
Response parameters | Entered successfully |
code Return code. | |
message Error message. | |
data Response data. |
Prerequisite states and call notes
- The World corresponding to the
ticketmust beready, and the ticket must be unexpired and unused. - A successful call creates the Travel; reusing the same
ticketreturns401011. - When the Acting feature or specification is not enabled,
403007is returned, and no Travel is created. versionmust be handled asactingV2; do not call control interfaces according to another capability version.- The client should read
aspectRatiobefore establishing the stream pull or the rendering container: use a portrait container for9:16and a landscape container for16:9. - Do not pass
maxExperienceTimeSec. Acting does not auto-end by this field, and the client must not use it to implement a countdown. rtcConfig=nullmeans there is currently no available streaming channel, and the client cannot start playback based on it.
Error codes
If the model call fails and returns an error, see HappyOyster Error Codes to resolve it.
Next steps
After entering the room successfully:
- Query Travel Status: poll every 2–5 seconds; you can send instructions when the Travel is
runningorpaused. - Send Process Instruction: drive the subsequent role-play performance.
- Pause Travel / Resume Travel: control the running pace as needed.
- End Travel: on ending, it enters
completedand artifact processing begins.