{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":1264,"path":"api-reference/web-services/impl-scripted-ext-pts-base-code.md","title":"Creating and adding a scripted extension point","bundle":null,"doc_type":null,"release":"australia","body":"\n# Creating and adding a scripted extension point\n\nWhen developing an application, create scripted extension points and add them to the script includes in the application code. Use a scripted extension point to designate the specific location where data or objects can be sent to a registered custom script include and where returned results are processed.\n\n**Note:** For an example of a scripted extension point, see [Using extension points to extend application functionality](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/api-reference/web-services/extension-points.md).\n\n-   **[Create a scripted extension point](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/api-reference/web-services/create-scripted-ext-pt.md)**  \nCreate a scripted extension point that can be placed in a script include in the base application code. By placing the scripted 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-   **[Add a scripted extension point in the base application code](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/api-reference/web-services/add-scripted-ext-pt-base-script-include.md)**  \nAdd the scripted extension point into a script include in the base application code. To add the extension point, include an API call that identifies the location at which registered custom artifacts execute.\n\n**Parent Topic:**[Using scripted extension points in server-side scripts](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/api-reference/web-services/scripted-extension-points.md)\n\n"}}