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

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu API Reference

ft:clusterId :

    - crapiref

bundleId :

    - crapiref

workflow :

    - Creator


---

# Create a client extension point

# Create a client extension point {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Create a client extension point that you can place in the UI scripts in the
application code. By placing the client extension point, you designate the specific location
in the application code where data or objects can be sent to a customization, and where data
is returned.

## Before you begin

Role required: admin or the specific role for the developer or administrator of the application  
Note:  
To learn about application-specific administrator roles and delegated development, see [Access control rules in
application administration apps](https://www.servicenow.com/docs/access?context=ACL-access-checks&version=xanadu&pubname=xanadu-application-development&ft:locale=en-US) and [Delegated development and
deployment](https://www.servicenow.com/docs/access?context=c_DelegatedDevelopment&version=xanadu&pubname=xanadu-application-development&ft:locale=en-US).

## About this task

Define the content and structure for an extension point. This definition should describe how a customization should be structured, how it interacts with the application code, and how the data that is returned by a customization at the extension point is processed.

By creating a good definition, you provide a structure for your extension
points.

## Procedure

1. Navigate to AllSystem Extension PointsClient Extension Points.
2. Click New.
3. On the form, fill in the fields.  
   {#create-client-ext-pt__table_tqn_cfv_s1b__entry__2}

   | Field | Description |
   |-|-|
   | Name | Unique name for the extension point. The name can be up to 100 alphanumeric characters, including special characters. |
   | API Name | Name of the extension point API that is pre-pended with the application scope to which it applies. This is a system-assigned name and cannot be changed. |
   | Application | Application scope against which the extension point is assigned. This is system-assigned and cannot be changed. For more information about the protections that are offered by the use of scoping, see [Application scope](https://www.servicenow.com/docs/access?context=c_ApplicationScope&version=xanadu&pubname=xanadu-application-development&ft:locale=en-US). |
   | Restrict to this scope | Option for restricting the extension point to the application scope only. |
   | Allow access over AJAX/REST | Option for enabling access to the client extension point over AJAX or REST. To learn more about these development architectures and techniques, see [AJAX](https://servicenow-prod.fluidtopics.net/cdtoLVychgPQghQyCrKyDw#p_AJAX "AJAX (asynchronous JavaScript and XML) is a group of interrelated, client-side development techniques used to create asynchronous Web applications.") and [REST APIs](https://servicenow-prod.fluidtopics.net/2vuQj3~2s_niNXyXhrbRZA "REST (REpresentational State Transfer) is a simple stateless architecture that provides standards between computer systems on the web, making it easier for them to communicate with each other."). |
   | Description | Requirements for the custom UI script, such as how the UI script should be structured and how it should operate with the application code. |
   | Example | Example of how a custom UI script that interacts with this extension point should be structured so it operates with the application code. |
   [Table 1. Client Extension Point form]

   {#create-client-ext-pt__table_tqn_cfv_s1b}
4. Click Submit.
{#create-client-ext-pt__steps_mfs_mgn_pdb}

*[\>]: and then