> For the complete documentation index, see [llms.txt](https://docs.enate.net/enate-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enate.net/enate-help/integrations/enate-integrations/api-sample-webform-front-end-to-post-tickets.md).

# Create a Webform that turns requests into Tickets with Enate's APIs

Check out this explainer for how to create a simple web front end which you could drop onto an intranet / public site to create Tickets in Enate using Enate's standard APIs.

{% embed url="<https://enate.cdn.spotlightr.com/watch/MTM5ODAzMA==>" %}

You can even download the source code for this from Enate's GitHub page to get you up & running quickly with this:

{% embed url="<https://github.com/EnateLtd/Webform>" %}

Check out our APIs section for more information about Enate's APIs and how to use them:

{% content-ref url="/pages/-MWitGruK-\_yfZirn2ke" %}
[APIs](/enate-help/integrations/enate-integrations/apis.md)
{% endcontent-ref %}


---

# 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://docs.enate.net/enate-help/integrations/enate-integrations/api-sample-webform-front-end-to-post-tickets.md?ask=<question>&goal=<endgoal>
```

`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.