Search Feedback
Search feedback conversations submitted by your organization.
Conversations are used to track feedback on existing events for example feedback on incorrect attendance or start and end dates for an event. Each piece of feedback submitted by a user is tracked as a conversation and will be returned by this endpoint. You can use this to display a list of event feedback conversations submitted with Loop Links by users in your application.
Request
HTTP Request
Query Parameters
q
string
Full-text search over conversations.
E.g. ?q=event+a+cancelled
link_id
string
Comma separated list of Loop Link IDs through which conversations were created.
E.g ?link_id=m4Dk4g4DRA8Yqbp2PC54
conversation_id
string
Comma separated list of conversation IDs.
E.g ?conversation_id=Eeh4ahnohghah0deeshahda
record_id
string
Comma separated list of Record IDs.
Record IDs can refer to either an Event ID (record type event-public
) or a Loop Submission (record type event-loop
).
E.g ?record_id=5uRg7CqGu7DTtu4Rfk
record_type
string
Comma separated list of record types for which to filter on. Possible values:
event-public
- Event ID available via Events API.event-loop
- Loop Submission ID.
E.g ?record_type=event-public
feedback_type
string
Comma separated list of feedback types. Possible values:
attendance_or_rank
category
dates
general
polygon
venue
E.g ?feedback_type=general
user_id
string
Comma separated list of User IDs.
E.g. ?user_id=hw8Dsmv4Djg
status
string
Comma separated list of feedback status. Possible values:
open
closed
E.g ?status=open
created
string
The date from and/or to the feedback has been created. Must be used with one of more of the suffixes:
lt
lte
gt
gte
E.g. ?created.gt=2023-03-04&created.lte=2023-05-01
updated
string
The date from and/or to the feedback has been updated.
Must be used with one of more of the suffixes:
lt
lte
gt
gte
E.g. ?updated.gt=2023-03-04&updated.lte=2023-05-01
sort
string
Comma-separated list of sort options.
Prefix the field name with -
for reverse order.
Possible values:
created
updated
relevance
Default value is ?sort=relevance,created
E.g. ?sort=-updated
limit
number
The maximum number of results to return.
The default limit is 10
.
E.g. ?limit=10
offset
number
The number of results to skip.
The default is 0
.
E.g. ?offset=20
Response
Response Fields
count
number
Total number of results found.
conversations
array
List of results where each item is a Conversation.
Please refer to the Conversation Response Fields section below for the structure of each record.
Conversation Response Fields
conversation_id
string
The unique identifier of the conversation.
E.g. Eeh4ahnohghah0deeshahda
create_dt
string
The creation date time for the record in ISO 8601 format format.
E.g. 2022-04-26T11:46:24+00:00
update_dt
string
The last update date time for the location in ISO 8601 format format.
E.g. 2022-04-26T11:46:24+00:00
link_id
string
Loop Link ID that was used to submit this feedback.
Will only be available on feedback created with a Loop Link.
E.g. m4Dk4g4DRA8Yqbp2PC54
record_id
string
Record ID this feedback is in reference to.
This could be either an Event ID (record type event-public
) or a Loop Submission (record type event-loop
). The record_type
value defines what type of Record ID this is.
E.g. 5uRg7CqGu7DTtu4Rfk
record_type
string
Record type this feedback is in reference to.
Possible types:
event-public
event-loop
E.g. event-public
feedback
object
Feedback can be provided for different fields.
Possible types:
attendance_or_rank
- Attendance or Rankcategory
- Category might need adjustingdates
- Dates might need adjustingduplicate
- Record might be a duplicategeneral
- Other feedbackpolygon
- Polygon might need adjustingsubmitted
- Feedback about an existing Loop submissionvenue
- Venue might need adjusting
E.g.
log
array
Log of actions taken with the feedback.
E.g.
status
string
Status of the feedback.
Possible values:
open
closed
E.g. open
Examples
Guides
Below are some guides relevant to this API:
Last updated