HangryDave

Members
  • Content Count

    4
  • Joined

  • Last visited

  1. I forgot about it at the time of the posting, but I did in fact test with other sets, and I have the same problem.
  2. Hello, I use the Rebrickable API for an app that downloads a set inventory(using/api/v3/lego/sets/{set_num}/parts/) and it seems that recently it either has been reading the JSON wrongly(unlikely, I tested in several ways) or hasn't been receiving the full JSON file. I tested it on the API documentation where it lets you try it out, and it didn't work there either. To make sure it wasn't new code that was breaking, I tested an old version that I knew worked, and it had the same problem. Here's the file that I receive for set 7965-1: https://pastebin.com/xVwwJWcQ (I would have included a linted version, but that takes up too much room, sorry.) I checked against the same inventory downloaded a few months ago to test, and the old one was indeed longer: https://pastebin.com/zvDxWrVr I'm not sure what the problem is. Does anyone have any ideas or is anyone able to confirm the issue? Thanks!
  3. Hello, I'm getting started with the Rebrickable API, and am a bit confused on how it works. I ran the command: curl -X GET --header 'Accept: application/json' --header 'Authorization: key *****' 'https://rebrickable.com/api/v3/lego/sets/7965/' ***** stands for my key. When I run this command, it gives me {"detail":"Not found."}. Can anyone help me as to why it is not working? (I'm probably doing something stupid) Also, how would I go about hooking this API into something like an Android application?