{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":1248,"path":"api-reference/web-services/create-client-ext-pt.md","title":"Create a client extension point","bundle":null,"doc_type":null,"release":"australia","body":"\n# Create a client extension point\n\nCreate 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.\n\n## Before you begin\n\nRole required: admin or the specific role for the developer or administrator of the application\n\n**Note:** To learn about application-specific administrator roles and delegated development, see [Access control rules in application administration apps](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/ACL-access-checks.md) and [Delegated development and deployment](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/c_DelegatedDevelopment.md).\n\n## About this task\n\nDefine 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.\n\nBy creating a good definition, you provide a structure for your extension points.\n\n## Procedure\n\n1.  Navigate to **All** &gt; **System Extension Points** &gt; **Client Extension Points**.\n\n2.  Click **New**.\n\n3.  On the form, fill in the fields.\n\n<table id=\"table_tqn_cfv_s1b\"><thead><tr><th>\n\nField\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td>\n\nName\n\n</td><td>\n\nUnique name for the extension point. The name can be up to 100 alphanumeric characters, including special characters.\n\n</td></tr><tr><td>\n\nAPI Name\n\n</td><td>\n\nName 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.\n\n</td></tr><tr><td>\n\nApplication\n\n</td><td>\n\nApplication 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://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/c_ApplicationScope.md).\n\n</td></tr><tr><td>\n\nRestrict to this scope\n\n</td><td>\n\nOption for restricting the extension point to the application scope only.\n\n</td></tr><tr><td>\n\nAllow access over AJAX/REST\n\n</td><td>\n\nOption for enabling access to the client extension point over AJAX or REST. To learn more about these development architectures and techniques, see [AJAX](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/api-reference/scripts/p_AJAX.md) and [REST APIs](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/api-reference/rest-api-explorer/c_RESTAPI.md).\n\n</td></tr><tr><td>\n\nDescription\n\n</td><td>\n\nRequirements for the custom UI script, such as how the UI script should be structured and how it should operate with the application code.\n\n</td></tr><tr><td>\n\nExample\n\n</td><td>\n\nExample of how a custom UI script that interacts with this extension point should be structured so it operates with the application code.\n\n</td></tr></tbody>\n</table>4.  Click **Submit**.\n\n\n**Parent Topic:**[Creating and adding a client extension point](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/api-reference/web-services/impl-client-ext-pts-base-code.md)\n\n"}}