Experience Slugs Actions

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

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

Get

Returns the experience slugs for an application

Method And Url

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

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.cli, all.Application.read, all.Organization, all.Organization.read, all.User, all.User.cli, all.User.read, experienceSlugs.*, or experienceSlugs.get.

Request Path Components

Path Component Description Example
APPLICATION_ID ID associated with the application 575ec8687ae143cd83dc4a97

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

Successful Responses

Code Type Description
200 Experience Slugs Collection of experience slugs

Error Responses

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

Post

Create a new experience slug for an application

Method And Url

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

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, experienceSlugs.*, or experienceSlugs.post.

Request Path Components

Path Component Description Example
APPLICATION_ID ID associated with the application 575ec8687ae143cd83dc4a97

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 Post schema. For example, the following would be a valid body for this request:

{
  "slug": "my-custom-slug",
  "version": "develop"
}

Curl Example 

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

Successful Responses

Code Type Description
201 Experience Slug Successfully created experience slug

Error Responses

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

Was this page helpful?

Still looking for help? You can also search the WEGnology Forums or submit your question there.