Field API Import

General Discussion
#1

Is there a known issue with the API Field import? I’m having some issues this morning, wanted to make sure it wasn’t anything on my end.

#2

We changed the structure of the feed slightly last week. This will be a permanent change going forward.

1 Like
#3

Okay. Even then, when I bring in the PGA Tour field, it gives me the 2023 Genesis for some reason?

Edit: never mind, it’s working.

1 Like
#4

I see that the ‘pganumber’ field is also gone from the Field import. Curious if that attribute will resurface in any other API endpoint? And is the final state of that endpoint or only a temporary schema :smiley:

#5

“player_num” is the ID for the relevant tour.

#6

On this note, when players withdraw from a tournament, are they immediately removed from the API field? Or do they stay there and are denoted as WD for some time?

#7

If they WD before the tournament has started, they will be removed. Otherwise, they stay in.

#8

Just in case it helps others…

I had a PowerQuery import into Excel, and one of the columns I manipulated in the query was gone. That was easy enough to fix. One minor nit (that could be on my end) is the datagolf ID now comes in as a string instead of a number as it does in other API pulls. Easy enough on my end to brute force (add 0 to the string in the xlookup to make it a number. I have to do that with Fangraphs too.), but still could be the reason somebody else’s breaks.

Just wanted to share.

2 Likes
#9

I think it still coming in as an integer, in the few places we’ve tested it anyways. Maybe your columns shifted and dg_id now sits in a place that used to be a string?

#10

i see- thank you for help here.