Need
In the "Needs" section, endpoints for managing questions posed to users during registration to assess their intended use of the application are described.
Below is an example of what questions and answers might look like.
Question | Answer |
---|---|
What do you plan to build | Web site or content site |
What is the maturity level? | Product |
What do you like most? | Low price |
Retrieve user
GET
{{BASE_URL}}/api/needs
Retrieve the user's responses to the questions posed during registration, which provide insights into their intended use of the application.
Headers
Name | Type | Description |
---|---|---|
Authorization* | String | Bearer Token |
Record user
POST
{{BASE_URL}}/api/needs
Record the user's responses to the questions posed during registration, allowing the application to capture and store their usage intentions for future reference.
Headers
Name | Type | Description |
---|---|---|
Authorization* | String | Bearer Token |
Update user
PATCH
{{BASE_URL}}/api/needs
Update the user's responses to the questions posed during registration. This functionality enables users to modify or refine their usage goals for the application as their needs evolve.
Query Parameters
Name | Type | Description |
---|---|---|
question* | String | What do you like most? |
Headers
Name | Type | Description |
---|---|---|
Authorization* | String | Bearer Token |
Request Body
Name | Type | Description |
---|---|---|
answer | String | Low price |
Last updated