- Update the metadata of the journey bundle
Update the editable journey bundle information. The following fields are editable with this API.
- name
- description
- latestJourneyId To update the latest journey, the following validation checks the validity of the operation.
- The journey must exist and belong to this journey bundle
- The journey must be launched The case when launching new journey as the latest is treated by the POST journey endpoint with the journeyBundleId.
- https://api-cdp.treasuredata.comhttps://api-cdp.treasuredata.com/entities/journey_bundles/{journeyBundleId}
- https://api-cdp.treasuredata.co.jphttps://api-cdp.treasuredata.co.jp/entities/journey_bundles/{journeyBundleId}
- https://api-cdp.eu01.treasuredata.comhttps://api-cdp.eu01.treasuredata.com/entities/journey_bundles/{journeyBundleId}
- https://api-cdp.ap02.treasuredata.comhttps://api-cdp.ap02.treasuredata.com/entities/journey_bundles/{journeyBundleId}
- https://api-cdp.ap03.treasuredata.comhttps://api-cdp.ap03.treasuredata.com/entities/journey_bundles/{journeyBundleId}
curl -i -X PATCH \
'https://api-cdp.treasuredata.com/entities/journey_bundles/{journeyBundleId}' \
-H 'Authorization: YOUR_API_KEY_HERE' \
-H 'Content-Type: application/json' \
-d '{
"id": "string",
"type": "journeyBundle",
"attributes": {
"name": "string",
"description": "string",
"latestJourneyId": "string"
},
"relationships": {
"parentFolder": {
"data": {
"id": "string",
"type": "folder-segment"
}
}
}
}'Returns the list of the journeys
The version number of the most recently created journey. If no journey has been created, this will be 0.
The most recent execution of the latest journey. If no executions have been created, this will be null.
The most recent execution of the latest journey. If no executions have been created, this will be null.
Whether the latest journey version may be triggered on demand. Clients must not recompute this from state, paused, latestJourneyId or priority-group membership. It is a necessary but not sufficient condition: true means none of the four conditions in onDemandIneligibilityReason apply, but POST /entities/journeys/{journeyId}/run may still reject the request with 409, so callers must handle that response rather than treating the button as guaranteed to succeed. Present only when checkOnDemandEligibility is true.
null if and only if isEligibleForOnDemand is true. When several conditions fail, the first in the order listed is returned; that order is part of the contract and follows the 422 guard order of POST /entities/journeys/{journeyId}/run. That run endpoint has two further guards this field deliberately does not evaluate, because each costs a workflow-engine round-trip and this is a GET: PARENT_SEGMENT_RUNNING and JOURNEY_WORKFLOW_RUNNING, both returned as 409. Neither value ever appears here. A journey bundle with no journey yet reports JOURNEY_NOT_ACTIVE rather than a dedicated code, so that "null if and only if eligible" holds; latestJourneyId is null in that case if you need to tell the two apart. Treat an unrecognised value as "ineligible, reason unknown" and render generic copy. Present only when checkOnDemandEligibility is true.
The parent segment's (audience's) matrix_updated_at formatted as ISO8601, or null if it has never been refreshed. Present only when checkOnDemandEligibility is true.
{ "name": "string", "description": "string", "latestJourneyId": null, "lastVersionNumber": 0, "journeys": [ { … } ], "latestExecution": { "workflowId": "string", "workflowSessionId": "string", "createdAt": "2019-08-24T14:15:22Z", "finishedAt": "2019-08-24T14:15:22Z", "status": "success", "workflowAttemptId": "string" }, "parentSegmentLatestExecution": { "workflowId": "string", "workflowSessionId": "string", "createdAt": "2019-08-24T14:15:22Z", "finishedAt": "2019-08-24T14:15:22Z", "status": "success", "workflowAttemptId": "string", "audienceId": "string" }, "isEligibleForOnDemand": true, "onDemandIneligibilityReason": "JOURNEY_NOT_ACTIVE", "parentSegmentLastRefreshedAt": "string", "included": [ { … } ] }