Unpublish an experience
POST/experiences/:experienceResourceId/unpublish
Takes the experience off its published URL, leaving the work-in-progress copy untouched so it can be published again later. Unlike publishing, this is synchronous: a 204 means the experience is no longer live. Only Flex experiences can be unpublished through this endpoint. Responds 400 when the experience is not a Flex one, and 404 when it does not exist or the caller cannot unpublish it — existence is not leaked on permission failure. Unpublishing an experience that is already unpublished succeeds. API key callers are limited to 10 requests per minute per account, after which the endpoint responds 429 with a Retry-After header.
Request
Responses
- 204
- 400
- 401
- 403
- 404
- 429