PingOne Platform APIs

Propagation Revisions

Identity propagation configuration revision instances are snapshots of the state of the plan, store, rule, and mapping entities of a configuration taken at a point in time. A new configuration revision can be created at any time, capturing the current state of those resources.

To reflect propagation API changes in the PingOne Admin Console, you must create a new propagation revision after performing any propagation operations.

The examples that follow show common actions to find and manage identity propagation and configuration revision resources. You need the Environment Admin role to perform operations on identity propagation and configuration revision resources.

Identity propagation revision data model

Property Type Required Mutable Description

createdAt

DateTime

N/A

Read-only

Date and time the propagation revision was created

createdBy

String

N/A

Read-only

Unique identifier (UUID) of the actor who created the propagation revision

environment.id

String

N/A

Read-only

Unique identifier (UUID) of the PingOne environment associated with this propagation revision

id

String

N/A

Read-only

Unique identifier (UUID) of the propagation revision

previousRevision.id

String

N/A

Read-only

Unique identifier (UUID) of the previous configuration revision snapshot

Response codes

Code Message

200

Successful operation.

201

Successfully created.

400

The request could not be completed.

401

You do not have access to this resource.

404

The requested resource was not found.

Propagation revision errors

In addition to the general error codes, propagation revision operations can return the following errors:

HTTP status Top‑level code Detail code When it happens and what the response contains

400

REQUEST_FAILED

None

Message: Could not create a revision. Please check that a plan and rule exists for your environment.

When and details

When: A POST request cannot create a revision because the environment has no plan and rule configured

Details: None.

403

ACCESS_FAILED

None

Message: The actor attempting to perform the request is not authorized.

When and details

When: The actor lacks the osmosis:create:revision permission (the POST operation) or the osmosis:get:revision permission (the GET operations)

Details: None.

404

NOT_FOUND

None

Message: Resource not found: {environmentId=<envID>, id=<revisionID>} or Resource not found: latest revision

When and details

When: A GET /environments/{envID}/propagation/revisions/{revisionID} request references a revision ID that does not exist in the environment or is not a time‑based UUID, or a GET /environments/{envID}/propagation/revisions/id:latest request runs in an environment that has no revision yet

Details: None.