--- title: Define a CORS rule description: You can define a CORS rule to control which domains can access REST API endpoints and other web resources. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/api-reference/rest-api-explorer/t\_DefineACORSRule.html release: australia product: REST API Explorer classification: rest-api-explorer topic_type: task last_updated: "2026-03-12" reading_time_minutes: 2 breadcrumb: [REST APIs, Web services, API implementation, API implementation and reference] --- # Define a CORS rule You can define a CORS rule to control which domains can access REST API endpoints and other web resources. ## Before you begin Role required: cors\_rule\_admin, web\_service\_admin, or admin ## Procedure 1. Navigate to **All** > **System Web Services** > **REST** > **CORS Rules**. 2. Select **New**. 3. On the form, fill in the fields.
| Field | Description |
|---|---|
| Name | Enter a unique name for the rule. |
| Use Resource Path | Select this option to specify a path to a web resource. For REST APIs, leave this option cleared. |
| REST API | Select the REST API for the domain to access, such as the Table API. |
| Web Resource Path | If you selected **Use Resource Path**, enter a path to the web resource for the domain to access. |
| Domain | Enter the domain to access the specified REST API or web resource. This CORS rule is evaluated against requests from the specified domain.You can specify a domain pattern or an IP address. When using a domain pattern, you can use the wildcard character \(`*`\) to match incoming origin headers. |
| Max age | Enter the number of seconds to cache the client session. After an initial CORS request, further requests from the same client within the specified time don’t require a preflight message.If you don’t specify a value, the default value of 0 indicates that all requests require a preflight message. |
| For Embeddables | Reserved for future use. |
| Active | Select this option turn on the CORS rule. |