Posting data into a record for an attendee

30 views
Skip to first unread message

Frank Bresz

unread,
Apr 24, 2025, 6:58:31 AM4/24/25
to motorsportreg-api-developers
Hi everyone,

I have a program that pulls data about our events and creates spreadsheets for our team.

One thing it does is add numbers for people.  Is there a way I can write that number back into the MSR database somehow, as a field on a personal record?

I have admin rights, so I can create a new variable to hold it, if needed.

- Frank Bresz

Ryan Kovick

unread,
Apr 24, 2025, 8:06:55 AM4/24/25
to motorsportreg-api-developers
Hi Frank,
Are the numbers event-specific? If one club member can have a persistent number you can add a club question that stores their number.

You could call the following API as a PUT request to update that question:
PUT/DELETE /rest/members/{member_id}
Update or delete a member - allowed fields are memberId, memberEnd and status
Pass in an array of types to modify the member types
Pass in an array of questions to update the club/profile question answers (file/image uploads excluded)


We do allow PUT requests on /events/{uidEvent}/attendees/{uidAttendee}. The only parameters allowed are updates to the status, notes, and metadata. I don't recommend storing that data in the metadata field since its not easily accessible or visible in MSR when viewing the attendee.

Frank Bresz

unread,
Apr 24, 2025, 12:22:51 PM4/24/25
to motorsportreg-...@googlegroups.com, motorsportreg-api-developers
Hi Ryan

Yes the numbers will be event specific. 

We have the reserved thing worked out where people can reserve a number on cup cars and other competition cars. 

This is so we can assign a number - really just alphabetical - that we hand to the participants for their windshield and back corners. This works for corner workers and black flag. I could overload the field and us the same “number” field because we have a “do you want a number” as a 0/1 I can make 2 be “assigned by registrar” or similar. 

Just not sure how to “write back” a field. 

Any pointers would be great. 

- Frank P. Bresz }*{
- sent from phone

On Apr 24, 2025, at 08:07, Ryan Kovick <ry...@motorsportreg.com> wrote:

Hi Frank,
--
You received this message because you are subscribed to a topic in the Google Groups "motorsportreg-api-developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/motorsportreg-api-developers/lxtEDbGBjM0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to motorsportreg-api-de...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/motorsportreg-api-developers/64e06f2f-afba-4a03-8bc9-435525a730f3n%40googlegroups.com.

Ryan Kovick

unread,
Apr 24, 2025, 4:35:52 PM4/24/25
to motorsportreg-api-developers
Got it - since we don't have an attendee-level PUT API for this kind of data, I recommend making a single profile question for the entire org, then overriding it for each event. Once you have the question created you can call the PUT request on the members API to save the value into that question each time.

To see the data structure for a member, call the GET /rest/members/{member_id} API with the ?fields=questions parameter and look at the data coming back.
When you're ready to update the question, you'll send back a slimmed down member object in the PUT request data with a 'questions' object containing one question: the question UUID in 'id' and the value in 'answer'.

For the member ID in the URL, you easily can get that from the URL in the People screen when you click on a specific member (good for testing on a specific member like yourself). You also get back the member ID when you call the attendees API as part of the 'profileuri' field.
Reply all
Reply to author
Forward
0 new messages