HappyOyster-Acting-Resume Travel API Reference - Alibaba Cloud Model Studio

Resume a paused Acting Travel so that it re-enters the running state.

Scope

Resume a paused Acting Travel so that it re-enters the running state. Before calling, confirm the following:

Authentication: The primary API Key is not required; either the primary or a temporary API Key can call it. For how to obtain them, see Obtain authentication credentials.
Prerequisites: The Travel must be confirmed as paused via Query Travel Status.
Caller: Either your server or your client can call it.

HTTP request

Singapore

POST https://{WorkspaceId}.ap-southeast-1.maas.aliyuncs.com/api/v2/apps/happyoyster-1.0-acting/openapi/v1/travels/resume

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/resume

Replace {WorkspaceId} with your actual Workspace ID.

Request parameters

Resume Travel

curl --location 'https://{WorkspaceId}.ap-southeast-1.maas.aliyuncs.com/api/v2/apps/happyoyster-1.0-acting/openapi/v1/travels/resume' \
    -H "Authorization: Bearer $DASHSCOPE_API_KEY" \
    -H 'Content-Type: application/json' \
    -d '{
    "encryptedTravelId": "{encryptedTravelId}",
    "userAgent": "HappyOyster-Web/1.2.0"
}'

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.

Primary API Key: starts with sk-, e.g. sk-xxx.
Temporary API Key: starts with st-, e.g. st-xxx.

Request Body

encryptedTravelId string (Required)

The Acting encrypted Travel ID to resume. Returned by Enter Travel.

userAgent string (Optional)

SDK or client version identifier. A non-empty string; takes precedence over the HTTP User-Agent, used for SDK version and platform statistics.

Response parameters

Resume succeeded

{
    "code": 0,
    "message": null,
    "data": {
        "encryptedTravelId": "trvl_a1b2****",
        "status": "running"
    }
}

code integer

Return code. 0 means success; non-zero is an error code.

message string

Error message. null on success.

data object

Response data. null on failure.

Properties

encryptedTravelId string

The encrypted Travel ID.

status string

The status after resuming; returns running.

Prerequisite states and call notes

The Travel must be confirmed as paused via Query Travel Status.
The version in the enter-room response must be actingV2.
A Travel that has already ended or failed cannot be resumed.
After resuming, you can continue to send text process instructions; the client should converge its local running state based on the status query result.
Resuming does not change the aspectRatio returned when entering the room.

Error codes

If the model call fails and returns an error, see HappyOyster Error Codes to resolve it.

Next steps

After resuming, you can:

Query Travel Status: confirm the Travel is back to running.
Send Process Instruction: continue to drive the role-play.
End Travel: end the session and process artifacts.