Journeys V2

APIs related to Limio JourneysV2

Get Journeys V2

get

Retrieves all the journeysV2 in the Catalog

Authorizations
AuthorizationstringRequired

This authentication method is applicable to specific operations.

To create a publishable API key, see Public Keys (Read-Only API).

Responses
chevron-right
200

OK

application/json
starting_pointstringOptional

The starting point of the journey

Example: /cancel-now/
fallback_tagstringOptional

The fallback tag for the journey

Example: /cancel/
get
/v2/journey

Add Journey V2

post

Adds a new journey in the Catalog

Authorizations
AuthorizationstringRequired

To create a Bearer token, see How to get an OAuth Bearer Token?.

Usage format: Bearer <token>

Body
namestringOptional

The name of the journey

Example: Test
Responses
chevron-right
200

OK

application/json
messagestringOptionalDefault: Journey added successfully
post
/v2/journey

Get Journey V2 by name

get

Get a journey by name

Authorizations
AuthorizationstringRequired

To create a Bearer token, see How to get an OAuth Bearer Token?.

Usage format: Bearer <token>

Path parameters
journeyNamestringRequired

The name of the journey to retrieve

Responses
chevron-right
200

OK

application/json
statusstringOptional

The status of the journey record

Example: active
record_typestringOptional

The type of record

Example: journey
idstringOptional

The unique ID of the journey record

Example: journey-678
servicestringOptional

The service the journey belongs to

Example: limio
createdstring · date-timeOptional

Timestamp when the record was created

Example: 2025-03-06T14:25:01.064Z
updatedstring · date-timeOptional

Timestamp when the record was last updated

Example: 2025-03-06T14:25:01.064Z
modestringOptional

The environment or mode the journey is in

Example: production
process_hashstringOptional

The hash used for processing the journey

Example: journey-678
versionstringOptional

The version hash of the journey

Example: c37254b0e5d43c52ca5da66367261b8c57148d63
get
/v2/journey/{journeyName}

Update or Create Journey V2

put

Updates an existing Journey V2 with the provided data, identified by the journeyName path parameter. If no Journey V2 with the specified journeyName exists, a new one will be created.

Authorizations
AuthorizationstringRequired

To create a Bearer token, see How to get an OAuth Bearer Token?.

Usage format: Bearer <token>

Path parameters
journeyNamestringOptional

The name of the journey to update.

Example: Digital Journey
Body
namestringRequired

Name of the journey.

Example: test001
Responses
chevron-right
200

OK

application/json
namestringRequired

Name of the journey.

Example: test001
put
/v2/journey/{journeyName}

Delete JourneyV2 by name

delete

Delete a journey by name

Authorizations
AuthorizationstringRequired

To create a Bearer token, see How to get an OAuth Bearer Token?.

Usage format: Bearer <token>

Path parameters
journeyNamestringRequired

The name of the journey to delete

Responses
chevron-right
200

Successfully deleted

application/json
messagestringOptionalDefault: Journey deleted successfully
delete
/v2/journey/{journeyName}

Last updated

Was this helpful?