---
sourceDocument: Australia API Reference
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/api-reference

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia API Reference

ft:clusterId :

    - crapiref

bundleId :

    - crapiref

workflow :

    - Creator


---

# Add a path-based ACL for a scripted REST API

# Add a path-based ACL for a scripted REST API {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Path-based Access Control Levels (ACLs) enable you to define access control rules for scripted REST API endpoints using their resource path. This can be done independently of the ACL references on the operation record.
Path-based ACLs enable more flexible security configurations, especially for read-only APIs and guest user experiences.

## Before you begin

Role required: security_admin or admin

Additional requirement: the full resource path from the API's SysWS operation record (found in the "Resource path" field)

## About this task

Path-based ACLs are defined in the sys_security_acl table with the type "REST Endpoint" and apply to specific REST API resource paths. Unlike operation-referenced ACLs (which only apply when "Requires authentication" is
checked), path-based ACLs are evaluated for every request to matching resource paths.

**When to use Path-Based ACLs:**

* You must add security to a read-only API that you can't modify
* You want to enable guest access to public APIs with controlled authorization
* You must grant access based on custom roles not defined in the original API
* You want to add security layers without modifying the original API record

{#add-a-path-based-acl-for-a-scripted-rest-api__ul_f4w_nyh_b3c}

**Important:** Path-based ACLs work alongside operation-referenced ACLs, not in place of them. All applicable ACLs must pass for access to be granted.

## Procedure

1. Navigate to Allsys_security_acl.list.
2. Select New.
3. Select REST Endpoint in the Type field.
4. Select the necessary HTTP method for the ACL in the Operation field.
   * GET
   * POST
   * PUT
   * DELETE
   * PATCH
   * Or other HTTP methods as needed.
   {#add-a-path-based-acl-for-a-scripted-rest-api__choices_udh_3zh_b3c}
5. Enter the fill API resource oath in the Resource Path field.  
   Example: /api/sn_pa_designer/usage_monitoring/resource  
   Tip:  
   Copy this value from the "Resource path" field on the SysWS operation record to help ensure accuracy.
6. Configure the ACL script or condition to define your access rules.
7. Select submit.
{#add-a-path-based-acl-for-a-scripted-rest-api__steps_hnw_g23_b3c}

## Result

The path-based ACL is active and will be evaluated for any requests to this resource path.
**Related tasks**   

* [Configure a scripted REST API resource to require an ACL](https://servicenow-prod.fluidtopics.net/A1cmPARMRnXw5VgRDXs3hA "By default, API resources/endpoints inherit security settings from the parent API. Define custom Access Control Levels (ACLs) for a specific resource/endpoint to override the inherited settings.")
* [View path-based ACLs](https://servicenow-prod.fluidtopics.net/32kr3lyttsPyZ7RkgjKc4Q "Path-based Access Control Levels (ACLs) enable you to define access control rules for scripted REST API endpoints using their resource path. This can be done independently of the ACL references on the operation record. Path-based ACLs enable more flexible security configurations, especially for read-only APIs and guest user experiences.")
* [View path-based ACLs from REST API Explorer](https://servicenow-prod.fluidtopics.net/3NXhSTSHtp4OXVliJ4bn2w "Path-based Access Control Levels (ACLs) enable you to define access control rules for scripted REST API endpoints using their resource path. This can be done independently of the ACL references on the operation record. Path-based ACLs enable more flexible security configurations, especially for read-only APIs and guest user experiences.")

*[\>]: and then