There are two create options. You can configure a policy decision endpoint to reference a specific policy version. Or, you can configure a policy decision endpoint that is always up-to-date.

In cases where a specific policy version is defined in the request, the policy decision service fetches the policy configuration at that version from the policy editor service and stores it locally. When no policy version is defined (always up-to-date), the decision endpoint is recorded in the local database with no policy configuration. Access to the policy editor service is not required in this case.

The following sample shows the POST /environments/{{envID}}/decisionEndpoints operation to create a new policy decision endpoint resource associated with the environment specified in the request URL. The request body specifies the name, description, authorizationVersion (the policy version), and recentDecisionsEnabled attributes.