> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/design-considerations-and-frameworks/frameworks/web-services-framework/starting-a-project-using-the-web-services-framework.md).

# Starting a Project Using the Web Services Framework

To set up a new project based on the Web Services Framework, you need to fill out the Project name in the *New Project* screen:

1\. Click the *projects* folder in the *Projects* pane and click the *New Project* icon to add a new project.

2\. Select either the Standard or REST API template from the *Webservices Framework* section, enter a name in the *Project name* field, and click *Create*.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-ca1a40b2cae33d8c9a7efcf127548d73e22af1dd%2Fc5ded8eb-ab4a-4615-b21f-4eea90b0b907.png?alt=media)

Once you click *Create* the system will create your project and your project folder will show up in the *Projects* pane. The blue folder icon next to your project name indicates that the item is a project.

With your project created the project screen in the *Viewer* pane shows some meta data fields and configuration options. The configuration settings at this level are similar to the other framework products and are covered elsewhere.

Once you have created and configured your project you can test the web service. Click *Test* and test the endpoint in this default project, which is called *function\_1*. The web service returns the status code 200 OK and the output message *function\_1 called*.

With your new project created, build the endpoints of the web service application and model the logic of processing any input file to create the output.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://community-test.logicnets.com/release-9/design-considerations-and-frameworks/frameworks/web-services-framework/starting-a-project-using-the-web-services-framework.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.