> For the complete documentation index, see [llms.txt](https://kb.craftformswp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.craftformswp.com/documentation/form-building/create-form/form-settings-post-context/advanced-settings.md).
# Advanced Settings
In this panel you may see the full REST endpoint name used by this form. This is the endpoint where the form data gets submitted:
### Submission Settings
For advanced users: it is possible to define a custom endpoint name. Not the full URL, but the last part that usually is very generic.
Additionally, it is possible to allow external submissions to this endpoint. Normally the form uses same origin policy and WP nonce to authorize submission. However, if you want to use headless WordPress, then you would probably want to allow external submissions, which means no nonce is used and the form can be submitted from other origins (URLs).
#### Form REST Name
CraftForms uses REST API endpoints as form actions, as submissions URLs. Each form has its own URL and this is how we know precisely which form was submitted.
Such endpoints are different only by unique form ID, example:\
`https://sandbox.test/index.php?rest_route=/craftforms/v1/submit/form_69f9bb7029199`
Where `form_69f9bb7029199` is the unique form ID.
Form REST name allows customisation of this endpoint. For instance, if we set it to "contact", then our form submission URL will be:
`https://sandbox.test/index.php?rest_route=/craftforms/v1/submit/contact`
**Important: REST names must be unique for each form!**
#### Allow External Submissions
Upon activation this setting the form will be opened to external submission, which means submissions from another web sites and web apps. This is particularly useful when paired with static sites.
The modal window shows example of `curl` request and summary of request parameters based on actual fields added to the form and their validation configuration.
Practically it means that the form itself must be created and configured, but it will not be rendered on this site. No need to add it to any pages of this particular WordPress installation. Instead, replicate it in your React/Vue/Svelte/static site etc app and submit from there to the endpoint shown in the modal window of your site. **Important: backend validation will be forced on submitted data! This is exactly the idea of this functionality: to provide backend for form submissions, the backend that can be configured easily and well supported!**
#### Custom Submission Url
Use it when you want to use a form created in CraftForms, render it on your site, but set its submission url to your own custom one. It means that you have written PHP form submission handler, you handle sanitization, validation of the submitted data and you created functionality that is being invoked upon the form submission. This is an advanced functionality for experienced developers.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://kb.craftformswp.com/documentation/form-building/create-form/form-settings-post-context/advanced-settings.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.