Weekly Challenge

Solve the challenge, share your solution and summit the ranks of our Community!
IDEAS WANTED

We're actively looking for ideas on how to improve Weekly Challenges and would love to hear what you think!

Submit Feedback
We've recently made an accessibility improvement to the community and therefore posts without any content are no longer allowed. Please use the spoiler feature or add a short message in the message body in order to submit your weekly challenge.

Challenge #139: Spooky API Connection

Highlighted
8 - Asteroid

My Effort - took a while. Hat tip to @mbogusz for new api workings

Spoiler
JamesCameron_0-1580228051341.png
Alteryx Partner

This was interesting...It seems the API that was used when this challenge was posted is still active, but not admitting new users (and will phase out at the end of the month) (FYI @JoeM )
I've registered for the API that supersedes this one https://fdc.nal.usda.gov/api-key-signup.html

A quick search suggests the old id's don't seem to exist in the new API/database (web info says you can use ndbid to search, but I've been unable to find those provided in the starting challenge -either using the API or the web searchbox), so I've done two sets of calls: one to search by name, and then get the first result for each;and a second to get the details (i.e. calories). Not surprisingly, the numbers don't quite add up...

 

Spoiler
dsmdavid_0-1584810220113.png

 

 

It should be possible to search using the ndbid, but I get no results

Spoiler
dsmdavid_0-1584811262452.png
but in postman:
dsmdavid_1-1584811362272.png

so I may be doing something wrong..

 

 

Highlighted
8 - Asteroid

All,

 

I had some trouble getting the request for the API as I had to peek at others.

-This is a really good example of an API though.

Spoiler
Capture.PNG

 

Highlighted
8 - Asteroid

First API workflow

Highlighted
12 - Quasar

Might want to re look at the weekly challenge question.

The API link might be changes was getting something like below.

https://developer.nrel.gov/api/alt-fuel-stations/v1/nearest.json?api_key=dMl1hnQlgN2PLQMVDNedM2qQ851...

 

I can see some people have pointed it out too

 

Either ways i took reference of another posted solution to solve the weekly challenge

 

Spoiler
 
atcodedog05_0-1585895590678.png

 

 

On a spree to binge complete weekly challenges
Adrenaline rush

Highlighted
Alteryx Partner
Spoiler
AWC139.PNG

Good API Practice, it's been a while!

Highlighted
Alteryx Certified Partner

Challenge 139 is done!

 

Spoiler
image.png
Highlighted
8 - Asteroid

I get slightly different numbers but I was using a different API (as others mentioned the original one doesn't seem to be working)

 

Spoiler
hanykowska_0-1589658370165.png

 

Highlighted
Alteryx Certified Partner

Here is my solution !

Highlighted
Alteryx Partner

Well, I got an answer anyway.

 

As others have mentioned, the original API is no longer active. I used the following URL:

https://api.nal.usda.gov/fdc/v1/foods?fdcIds=[IDs]&api_key=[Key]

where [IDs] is a comma-separated list of IDs and [Key] is your API key.

 

The candy IDs have also changed. I used the following list:

Snickers 789264
Candy Corn 425594
Tootsie Roll Pop 427751
Sweetarts 570272
Atomic Fireballs 476145
Chewy Sours 789635
Sour Patch Kids 579277

 

My final answer doesn't match the solution. I assume this is due to the changes with the API. Otherwise, I believe my workflow to be logically correct.

 

Spoiler
Capture.PNG