Journeys

getJourneyRevision

Changed on

Returns one revision with its full configuration, in the shape the builder holds a journey in, so it can be loaded straight into the editor as unsaved changes. Reading a revision changes nothing; a client persists it, if at all, by posting it back to POST .../revisions.

Only available for organizations with journey versioning enabled; returns 404 otherwise.

get/v1/journey/configuration/{id}/revisions/{revision_id}

Request

  • Base URL
    https://journey-config.sls.epilot.io
  • URL
    https://journey-config.sls.epilot.io/v1/journey/configuration/{id}/revisions/{revision_id}
  • Auth
    HTTP bearer

Path parameters

idstring uuid required
Example:509cdffe-424f-457a-95c2-9708c304ce77

Journey ID

revision_idstring required
Example:42

Revision ID, as returned in a revision summary

Response

The revision with its configuration

revision_idstring required

Opaque identifier of the revision. Moves on every save.

created_atstring date-time required
created_bystring

User id of the author. Absent for revisions recorded from writes without a user, e.g. blueprint installs.

namestring

Set at publish time only, so present if and only if this revision has been published at least once.

descriptionstring
published_atstring date-time

The last time this revision was published. Not the same question as is_published: a revision that was the published version yesterday still carries a published_at.

is_publishedboolean required

Whether this revision is the published version right now.

mapping_config_versionnumber

Version of the entity-mapping config stored alongside this revision.

Example response

{
  "revision_id": "42",
  "name": "Summer campaign",
  "mapping_config_version": 12,
  "configuration": {
    "journey_type": "Sales template (Premium)",
    "settings": {
      "embedOptions": {
        "lang": "de"
      },
      "offline": {
        "packTtlHours": 24
      }
    },
    "validationRules": {
      "block1": "rule123",
      "block2": [
        "rule456",
        "rule789"
      ],
      "block3": {
        "field1": "rule101",
        "field2": [
          "rule102",
          "rule103"
        ]
      }
    },
    "_manifest": [
      "123e4567-e89b-12d3-a456-426614174000"
    ]
  }
}

Changes

    • info

      added the optional property //////////// to the response with the status

    • info

      added the optional property /////////// to the response with the status

    • info

      added the optional property ////////// to the response with the status