> For the complete documentation index, see [llms.txt](https://docs.feedbackly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.feedbackly.com/master/responses/notes.md).
# Notes
## Question types
This table clarifies the different outputs per question type
| Question type | Description | Field | Example | |
| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------ | ---------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Button | Smileys / Satisfaction
The values are in the scale of 0-1.
5 buttons: 0, 0.25, 0.5, 0.75, 1
4 buttons: 0, 0.33, 0.66, 1
| valueNum: number
answer: number
| valueNum: 0.5
answer: 0.5
| |
| NPS | NPS question
Numbers 0-10
| valueNum: number
answer: number
| valueNum: 4
answer: 4
| |
| Word | Category / Selection / Multiselect
Answer will either be a string value if the
question is single select or an array of strings
if the question is a multi-select.
valueArray will contain the unique id's of the
choice(s) selected while answer contains the
string representations of the choice in the language chosen
| valueArray: string\[]
answer: string | string\[]
| Multiselect:
valueArray: \['sdfs3, 'asdas1]
answer: \['Apples', 'Oranges']
Single select:
valueArray: \['533rf']
answer: 'Pears'
|
| Image | Category / Selection by image
Same as above
| Same as above | Same as above, outputs image labels | |
| Slider | Slider question. These questions contain multiple responses depending on the field responded to. In order to connect these answers together, you look at the responseChainId and the questionId
Each field contains a fieldId and a fieldName to distinguish the responses apart.
The scale is 0-10.
| valueNum: number
answer: number
| valueNum: 4
answer: 4
| |
| Contact | Contact form question. Like Slider question, this question might have multiple responses per question. | valueString: string
answer: string
| valueString: ""
answer:
""
| |
| Text | Open-ended field. | valueString: string
answer: string
| valueString: "I was happy"
answer: "I was happy"
| |
### Pagination
For endpoints that returns multiple objects, pagination is done by providing the URL's to get the next objects (if more are available)
| Field | Example |
| -------- | -------------------------------------------------- |
| next | |
| previous | |
---
# 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.feedbackly.com/master/responses/notes.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.