Scenarios

Creates a copy of the scenario in the target team, applying dependency replacements from the body. The response body contains the new scenario ID; the Location header points to the new resource.

Rules

  • Same team: existing connections may be reused; you can omit replacements for them.
  • Different team: connections cannot be reused; provide replacements for each required connection.
  • If the source scenario uses a hook, provide an unused hook in the replacements.
  • For data stores, data structures, and keys: if you supply IDs in the request, those are used; otherwise they are duplicated in the target team.
post/api/v3/scenarios/{scenarioId}/clone

Request

  • Base URL: https://fusion.adobe.io
  • URL: https://fusion.adobe.io/api/v3/scenarios/{scenarioId}/clone
  • Auth: HTTP bearer and API key in header x-organization-id and API key in header x-api-key and API key in header x-gw-region

Path parameters

scenarioIdnumber required
Example:123

Source scenario ID to clone

Request body

teamIdnumber

Team ID where the cloned scenario will be created. If omitted, the clone is created in the source scenario team.

folderIdnumber

Folder ID where the cloned scenario will be created

namestring

Name for the cloned scenario

continueFromLastProcessedboolean

When true, the clone continues right after the last record the original processed. When false (default), the clone starts fresh and processes all records from the beginning.

Example request

{
  "teamId": 88,
  "folderId": 88,
  "name": "My copied scenario",
  "replacements": [
    {
      "sourceId": 100,
      "targetId": 200
    }
  ]
}

Response

New scenario created; response body contains its ID. Location header is set to the new scenario URL.

idnumber required

ID of the newly created (cloned) scenario

Example response

{
  "id": 456
}

Changes

    • info

      added the new scenario enum value to the request property //

    • info

      added the new optional request property

    • info

      the request property became optional