--- title: Create REST API access policy description: Create an API access policy and map an authentication profile to restrict the authentication type for a REST API. For example, you can create an API access policy that allows only ID token authentication for a REST API. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/platform-security/authentication/create-api-access-policy.html release: australia product: Authentication classification: authentication topic_type: task last_updated: "2026-03-12" reading_time_minutes: 2 breadcrumb: [REST API access policies, API access policy, Authentication, Access Management] --- # Create REST API access policy Create an API access policy and map an authentication profile to restrict the authentication type for a REST API. For example, you can create an API access policy that allows only ID token authentication for a REST API. ## Before you begin Make sure that an authentication profile is created. For more information, see [Create an authentication profile](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-security/authentication/create-authentication-profile.md). Role required: api\_service\_admin, adaptive\_auth\_policy\_admin ## Procedure 1. Navigate to **All** > **System Web Services** > **REST API Access Policies**. 2. Select **New**. 3. On the form, fill in the mandatory fields and submit. \[Omitted image "rest-api-access-policy.png"\] Alt text: API access policy fields **Note:** You must reopen the submitted form to populate additional fields.
| Field | Description |
|---|---|
| Name | Unique name of the API access policy. |
| Active | Option to make the API access policy active. |
| REST API | The REST API to which the access policy is applied. For example, **Attachment API**. |
| REST API PATH | API path of the REST API. This field is auto-populated based on the selected REST API. For example, **now/attachment**. |
| HTTP Method | Method used for interacting with the API. This field is auto-populated based on the selected REST API. |
| Version | Version of the API. For example, **v1**. This field is auto-populated based on the selected REST API.**Note:** If you want to create an authentication policy for all versions of a REST API, you must create individual policies for each version. |
| Resource | Child resource of the REST API. This field is auto-populated based on the selected REST API. For example, **/now/attachment** |
| Table | The tables to which the API access policy applies. This option only applies to policies for the Table API. |
| Application | Scope of the application. |
| Global | Option to apply the policy to all methods, versions, and resources for the API. |
| Apply to all methods | Option to apply the policy to all the methods, versions, and resources for the API. |
| Apply to all resources | Option to apply the policy to all or the API resources. |
| Apply to all versions | Option to apply the policy to all or the API versions. |
| Apply to all tables | Option to apply the policy to all tables. This option only applies to policies for the Table API. |
| [Advertise all auth schemes](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-security/authentication/create-authentication-profile.md) | Determines whether the `WWW-Authenticate` header includes all configured authentication schemes. When set to `false` \(default\), the header includes only the most recently configured authentication profile in the policy. When set to `true`, the header lists all configured authentication schemes. |