Experience Slug Actions

https://api.app.wnology.io/applications/APPLICATION_ID/experience/slugs/EXPERIENCE_SLUG_ID

Below are the various requests that can be performed against the Experience Slug resource, as well as the expected parameters and the potential responses.

Delete

Deletes an experience slug

Method And Url

DELETE https://api.app.wnology.io/applications/APPLICATION_ID/experience/slugs/EXPERIENCE_SLUG_ID

Authentication

A valid API access token is required to access this endpoint. The token must include at least one of the following scopes: all.Application, all.Organization, all.User, experienceSlug.*, or experienceSlug.delete.

Request Path Components

Path Component	Description	Example
APPLICATION_ID	ID associated with the application	575ec8687ae143cd83dc4a97
EXPERIENCE_SLUG_ID	ID associated with the experience slug	575ed78e7ae143cd83dc4aab

Request Headers

Name	Required	Description	Default
Authorization	Y	The token for authenticating the request, prepended with Bearer

Curl Example

curl -H 'Content-Type: application/json' \
    -H 'Accept: application/json' \
    -H 'Authorization: Bearer YOUR_API_ACCESS_TOKEN' \
    -X DELETE \
    https://api.app.wnology.io/applications/APPLICATION_ID/experience/slugs/EXPERIENCE_SLUG_ID

Successful Responses

Code	Type	Description
200	Success	If experience slug was successfully deleted

Error Responses

Code	Type	Description
400	Error	Error if malformed request
404	Error	Error if experience slug was not found

Get

Retrieves information on an experience slug

Method And Url

GET https://api.app.wnology.io/applications/APPLICATION_ID/experience/slugs/EXPERIENCE_SLUG_ID

Authentication

A valid API access token is required to access this endpoint. The token must include at least one of the following scopes: all.Application, all.Application.read, all.Organization, all.Organization.read, all.User, all.User.read, experienceSlug.*, or experienceSlug.get.

Request Path Components

Path Component	Description	Example
APPLICATION_ID	ID associated with the application	575ec8687ae143cd83dc4a97
EXPERIENCE_SLUG_ID	ID associated with the experience slug	575ed78e7ae143cd83dc4aab

Request Headers

Name	Required	Description	Default
Authorization	Y	The token for authenticating the request, prepended with Bearer

Curl Example

curl -H 'Content-Type: application/json' \
    -H 'Accept: application/json' \
    -H 'Authorization: Bearer YOUR_API_ACCESS_TOKEN' \
    -X GET \
    https://api.app.wnology.io/applications/APPLICATION_ID/experience/slugs/EXPERIENCE_SLUG_ID

Successful Responses

Code	Type	Description
200	Experience Slug	Experience slug information

Error Responses

Code	Type	Description
400	Error	Error if malformed request
404	Error	Error if experience slug was not found

Patch

Updates information about an experience slug

Method And Url

PATCH https://api.app.wnology.io/applications/APPLICATION_ID/experience/slugs/EXPERIENCE_SLUG_ID

Authentication

A valid API access token is required to access this endpoint. The token must include at least one of the following scopes: all.Application, all.Organization, all.User, experienceSlug.*, or experienceSlug.patch.

Request Path Components

Path Component	Description	Example
APPLICATION_ID	ID associated with the application	575ec8687ae143cd83dc4a97
EXPERIENCE_SLUG_ID	ID associated with the experience slug	575ed78e7ae143cd83dc4aab

Request Headers

Name	Required	Description	Default
Authorization	Y	The token for authenticating the request, prepended with Bearer

Request Body

The body of the request should be serialized JSON that validates against the Experience Slug Patch schema. For example, the following would be a valid body for this request:

{
  "slug": "my-new-slug",
  "version": null
}

Curl Example

curl -H 'Content-Type: application/json' \
    -H 'Accept: application/json' \
    -H 'Authorization: Bearer YOUR_API_ACCESS_TOKEN' \
    -X PATCH \
    -d '{"slug":"my-new-slug","version":null}' \
    https://api.app.wnology.io/applications/APPLICATION_ID/experience/slugs/EXPERIENCE_SLUG_ID

Successful Responses

Code	Type	Description
200	Experience Slug	Updated experience slug information

Error Responses

Code	Type	Description
400	Error	Error if malformed request
404	Error	Error if experience slug was not found

Schemas

Error

Schema for errors returned by the API

Error Schema

▶
(root){} 3 keys
$schema:"http://json-schema.org/draft-07/schema#"
type:"object"
▶
properties:{} 2 keys
▶
type:{} 1 key
▶
message:{} 1 key

Error Example

▶
(root){} 2 keys
type:"NotFound"
message:"Application was not found"

Experience Slug

Schema for a single Experience Slug

Experience Slug Schema

▶
(root){} 3 keys
$schema:"http://json-schema.org/draft-07/schema#"
type:"object"
▶
properties:{} 7 keys
▶
id:{} 2 keys
▶
experienceSlugId:{} 2 keys
▶
applicationId:{} 2 keys
▶
creationDate:{} 2 keys
▶
lastUpdated:{} 2 keys
▶
slug:{} 4 keys
▶
version:{} 3 keys

Experience Slug Example

▶
(root){} 7 keys
id:"5b995e51ea9994b50d745284"
experienceSlugId:"5b995e51ea9994b50d745284"
applicationId:"575ec8687ae143cd83dc4a97"
creationDate:"2016-06-13T04:00:00.000Z"
lastUpdated:"2016-06-13T04:00:00.000Z"
slug:"my-custom-slug"
version:"develop"

Experience Slug Patch

Schema for the body of an Experience Slug modification request

Experience Slug Patch Schema

▶
(root){} 4 keys
$schema:"http://json-schema.org/draft-07/schema#"
type:"object"
▶
properties:{} 2 keys
▶
version:{} 1 key
▶
slug:{} 4 keys
additionalProperties:false

Experience Slug Patch Example

▶
(root){} 2 keys
slug:"my-new-slug"
version:null

Success

Schema for reporting a successful operation

Success Schema

▶
(root){} 3 keys
$schema:"http://json-schema.org/draft-07/schema#"
type:"object"
▶
properties:{} 1 key
▶
success:{} 2 keys

Success Example

▶
(root){} 1 key
success:true