HappyOyster-Directing-Rewind Travel API Reference

​

Scope

• 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 first enter the paused state; it cannot be rewound directly while running. Confirm via Query Travel Status.
• Caller: Either your server or your client can call it.

​

HTTP request

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

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

​

Prerequisite states and call notes

• The Travel must first enter paused; it cannot be rewound directly while running.
• Pause Travel has an asynchronous confirmation barrier of about 3 seconds. After receiving the pause response, you should still poll Query Travel Status and confirm the externally visible status is already paused before calling this endpoint.
• The script is organized in 4-second Blocks; a multiple of 4 such as 4, 8, or 12 is recommended for rewindToSec (for example, 6 → 8).
• The actual landing point is determined by resumedAtSec / actualRewindToSec.

​

Error codes

​

Next steps

• Query Travel Status: confirm the running status.
• Standard mode: Send Process Instruction.
• Pause Travel: pause again for the next rewind.
• End Travel: end the session and process the artifacts.