The client uses the ticket to create an actual Travel and obtain the RTC join configuration and the Adventure capability version. maxExperienceTimeSec takes effect only in the Adventure model.
Scope
The client uses the ticket to create an actual Travel and obtain the RTC join configuration. maxExperienceTimeSec takes effect only in the Adventure model. 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
- China (Beijing)
- US (Virginia)
POST https://{WorkspaceId}.ap-southeast-1.maas.aliyuncs.com/api/v2/apps/happyoyster-1.0-adventure/openapi/v1/travels/enter-travelReplace {WorkspaceId} with your actual Workspace ID.Request parameters |
|
Content-Typestring(Required)Request content type. This parameter must be set to application/json. | |
Authorization string (Required)API Key authentication. The primary API Key is not required; either the primary or a temporary API Key can call it.
| |
Request Body | |
ticket string (Required)An unexpired, unused single-use credential obtained from Get Travel Credential. Reusing the same ticket returns 401011. | |
maxExperienceTimeSec integer (Optional)Maximum experience duration, in seconds, must be a JSON integer. Defaults to 60. Allowed values:
"60" is not valid); an invalid tier returns 400000. The server automatically ends the Travel once this duration is reached. |
Response parameters |
|
code integerReturn code. 0 means success; non-zero is an error code. | |
message stringError message. null on success. | |
data objectResponse data. null on failure.
Properties encryptedTravelId stringThe newly created encrypted Travel ID. Used for subsequent Query Travel Status, end, and artifacts queries.encryptedWorldId stringThe encrypted World ID that this Travel corresponds to.mode integerAlways 1 for Adventure.creationModel stringAlways simple for Adventure.playUrl nullNot available yet; fixed to null.firstFrame stringWorld first-frame URL.rtcConfig objectRTC join configuration; null when there is no available streaming channel, in which case the client cannot start playback based on it.
stringThe Adventure enter-room version, fixed to wanderV2. Control data must be sent via the SDK sendCommand according to this version.aspectRatio nullFixed to null for Adventure; the player aspect ratio is not read from this field and follows the first-frame image ratio.noStreamAutoEndTimeoutSec integerNo-stream auto-end timeout in seconds, defaults to 30; the actual response prevails. If rtcStatus does not enter the streaming state within this time after entering the room, call End Travel with failCode=TRAVEL_NO_STREAM_AUTO_END.maxExperienceTimeSec integerThe experience duration actually adopted by the server; it can only be 60 / 90 / 120. The server automatically ends the Travel once this duration is reached. |
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. versionmust be handled aswanderV2; do not send control data using another model's interaction protocol.- The server ends the experience once
maxExperienceTimeSecis reached; the client should handle the terminal state that arrives afterward. - Adventure's direction, viewpoint, and action controls are not server-side HTTP Open APIs; the client must use the corresponding platform SDK's
sendCommand, which the SDK sends over the RTC DataChannel. 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 to read the available action pool.
- After the Travel becomes
running, the client sends direction, viewpoint, and action controls via the SDKsendCommand. - End Travel: end the session and handle the artifacts.