Search the Community

Showing results for tags 'v3'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Rebrickable
    • News
    • Suggestions
    • Help!
    • Bugs
    • API
    • Mobile App - Rebrickable LEGO Shopper
  • Inventories and Data
    • Set Inventories
    • MOC Discussions
    • Other Data
  • Other Stuff
    • LEGO News, Events, Community
    • Non LEGO
  • Projects

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Bricksafe URL


Location


Interests


Favourite Set(s)

Found 20 results

  1. Hi all, When I retrieve a lost part it seems that the image url included in the result points to an image with a different color than the part involved. https://rebrickable.com/api/v3/users/<token>/partlists/27086/parts/3297/4/ { "list_id": 27086, "quantity": 80, "part": { "part_num": "3297", "name": "Slope 33° 3 x 4", "part_cat_id": 3, "part_url": "https://rebrickable.com/parts/3297/slope-33-3-x-4/", "part_img_url": "https://m.rebrickable.com/media/parts/elements/329726.jpg", "external_ids": { "BrickOwl": [ "431571" ] } }, "color": { "id": 4, "name": "Red", "rgb": "C91A09", "is_trans": false, "external_ids": { "LEGO": { "ext_descrs": [ [ "Bright red", "BR.RED" ], ..... The color for this lost part is Red but when you use the url to pick up the image its black. I also noticed this with other parts and other colors for lost parts. Is this by design? should I retrieve the image in a different way if I want the corresponding image? Regards Peter
  2. Dragma

    Sets in set call.

    Just wondering, is there a reason why the set objects in the:/api/v3/lego/sets/{set_num}/sets/ dose not return the same info as the /api/v3/lego/sets/{set_num}/? for example: looking up K3731-1 in the first returns: "results": [ { "id": 2010, "set_num": "3731-1", "set_name": "Pumpkin Pack", "quantity": 2, "set_img_url": "https://m.rebrickable.com/media/sets/3731-1.jpg" } While 3731-1 in the latter returns: { "set_num": "3731-1", "name": "Pumpkin Pack", "year": 2000, "theme_id": 230, "num_parts": 87, "set_img_url": "https://m.rebrickable.com/media/sets/3731-1.jpg", "set_url": "https://rebrickable.com/sets/3731-1/pumpkin-pack/", "last_modified_dt": "2011-09-05T14:00:00Z" } Basically if you want to get all the info about a set that is contained within a set you need multiple calls. why not have them both return the same object with the single one setting a quantity of 1?
  3. dkurok

    throttle in API

    Is there a way to get rid of the throttle in API-calls (Status code 429) or get it significantly higher. Actually there is a limit of 2 calls / second. I'm working on a (private; non-commercial) inventory-solution in C#/WPF and I have a database with ~50.000 parts for which I want to update part-information by using RB-API (I also write back my infomration into my RB-account). With a limit of 2 calls/second and handling the 429-status it will take ~7 hours. I think without throttle I could do it in ~2 hours. In the API-documentation it is stated: What is the meaning of "normal user"? How can I become a non-normal user? Best regards Dietmar
  4. Hello, I'm struggling with the API-function /api/v3/lego/sets/{set_num}/sets/ The explanation for this function in the API-documentation / Swagger is: "Get a list of all Inventory Sets in this Set." But what are "Inventory Sets" for a given Set? Can someone give me an example set-number which returns a non-empty result? MAybe I understand by that... Many thanks for help
  5. The API-function /api/v3/users/{user_token}/parts/ has a query-parameter named "search". Has someone investigated how this parameter can be used ? Does it understand wildcards? For what kind of search (and on which fields) is it used? Same parameter also exists for /api/v3/users/{user_token}/sets/ How does it work there / can it be used there? Many thanks!
  6. Hi all, When I retrieve a lost part it seems that the image url included in the result points to an image with a different color than the part involved. https://rebrickable.com/api/v3/users/<token>/partlists/27086/parts/3297/4/ { "list_id": 27086, "quantity": 80, "part": { "part_num": "3297", "name": "Slope 33° 3 x 4", "part_cat_id": 3, "part_url": "https://rebrickable.com/parts/3297/slope-33-3-x-4/", "part_img_url": "https://m.rebrickable.com/media/parts/elements/329726.jpg", "external_ids": { "BrickOwl": [ "431571" ] } }, "color": { "id": 4, "name": "Red", "rgb": "C91A09", "is_trans": false, "external_ids": { "LEGO": { "ext_descrs": [ [ "Bright red", "BR.RED" ], ..... The color for this lost part is Red but when you use the url to pick up the image its black. I also noticed this with other parts and other colors for lost parts. Is this by design? should I retrieve the image in a different way if I want the corresponding image? Regards Peter
  7. Hi there, what is the proper API v3 way to add multiple lost parts in one API call? The documentation for v3 lost_parts does not seem to be complete - or in other words, I cannot get it to work as described. And the v2 function set_user_set_lost_parts does not work with multiple parts anymore.
  8. Hello, I try to build a web application using Ember framework and your v3 API. Really good API work ! But I have some difficulties to get right API responses. Not on the same API domain, a preflighted OPTIONS request is sent. It's OK. But this request is not accepted (401) by your API because there is no 'key' query or no 'Authorization' header defined in this OPTIONS request. This header (or key) is not required for a preflighted request?.. Thanks for your help, ps: something else, by default, Ember does not add trailing '/' to the url (use https://rebrickable.com/api/v3/lego/colors?key=... instead of https://rebrickable.com/api/v3/lego/colors/?key=...) so API replies with 301 redirect, considered like an error by preflighted OPTIONS request. So the CORS request fails.
  9. Am I the only one who thinks that the colors of the new LDraw renders look weird? For example, "Blue" and "Dark Blue" look like Medium and Dark Azure. Lego's Dark Blue: Lego's Blue: LDraw's "Dark Blue": LDraw's "Blue": Lego's Dark Azure: Lego's Medium Azure:
  10. Hello, I've just started playing with the API. Wonderful, thanks! Found a small bug - if I look for a certain element ID, it always gives the URL of the black version of the same design. Example: Element ID 6093527 (Bar 3L, LBG) gives the link to the black Bar 3L: "part_img_url":"https://m.rebrickable.com/media/parts/elements/4566275.jpg" Best, Matija
  11. Not all of the related parts are shown on part pages and part popups. For example, part 15573 is not shown as an alternate to 3794a: Also part pairs are not shown. E.g. part 43723 is not shown as a pair of 43722. Another issue:
  12. The API-functions: GET /api/v3/lego/mocs/{set_num}/parts/ GET /api/v3/lego/sets/{set_num}/parts GET /api/v3/lego/sets/{set_num}/sets/ GET /api/v3/users/{user_token}/partlists/ GET /api/v3/users/{user_token}/setlists don't have the query-parameter "ordering" even though paging (paramter page and result with next and previous) are implemented. Is this by design? On the other hand I see that the API-function GET /api/v3/users/{user_token}/profile has a page-parameter (no ordering), but the result doesn't have the typical paging structure (count, next, previous) (Which I think makes sense when looking on what the function returns there is no paging needed). Regards Dietmar
  13. Hello, can someone please explain what exactly the API-function GET /api/v3/lego/elements/{id}/ is used for? In detail: - What ID is the parameter in (Lego-Element-ID, LEGO-design-ID,....)? - What is the result? The part_id seems not to be a Renrickable Part-Number Try for example 18862 for the {id} . It returns: { "part_id": 11548, "color_id": 70, "element_id": "6031144", "design_id": "88585" } So this seems to be LEG-Element-IDs and Design-ID for the queried ID. But the part_id is not a valid Rebrickable-ID/part_num... To be honest, I'm not so familar with the way especially LEGO is numbering their parts;so maybe someone can explain here or guide me to some ressource to understand... Best regards Dietmar
  14. So i'm often in the case where i'm evaluating the use of a part X in a MOC and i want to know how many i have in my whole collection. Is there an API for that? The closests thing looks like this one: /api/v3/users/{user_token}/parts/ But it appears to only look into Part Lists and not into Sets. Is there a way to search the whole collection? (other than retrieving inventory of each and every set? )
  15. Hello, I think the GET /api/v3/lego/parts/{part_num}/colors/ API-function should not have paging. There are only 133 colors over all and I guess there is no part which is available in all colors. Because the page-size itself cannot be set in the API and defaults to 100, this function should always return all colors the requested part is available in. This keeps away the overhead from the consumer to handle the rare case there are more than 100 colors available for a part (are there any?) and in worst case (133 colors for a part) puts 1/3 more to the answer (instead of maybe handling an addtional call for page 2, which normally is more costly on both side (client and server)) - maximum 33 * ~200 bytes = ~7kB more instead of a asecond call. Regards Dietmar
  16. Small bug; when you're on the API information page, all the top-level navbar links except for Build and Forum, link to the API page.
  17. Recently I bought a used 8466 on ebay. So I went and added the set to my collection on Rebrickable; when I then looked at 8466's inventory, the spare parts at the bottom are all outlined in red and when I hover over them it says "You do not have this part/colour in your buildable parts collection", even thought in my parts collection I have plenty of parts to cover the spares. e.g. I have 220 of the black 2780 pins in loose stock that should cover the 4 spares from 8466... Unless I'm misunderstanding how that works? Just as a note, I have since unchecked the "I still have the spare parts option" because the set I bought didn't have them, but the problem persisted BEFORE I did that.
  18. Hello! Lots of great changes on V3 but I'm going to focus on some of the less than great ones! We typically print out the list of parts to complete sets and are no longer able to do this. All of the html code is being picked up - both when you just choose print screen or if you highlight area to be printed. We have resorted to highlighting parts, copying into Word, and formatting into columns. Not a great solution though as the rows vary in height between columns and it's hard to use this way. thanks!
  19. Please restore the notes on mold variations of treasure chests here and here. Currently they are completely broken. Although these parts cannot be used in inventories, the notes may still be useful.
  20. Editing of comments for parts results in their duplication: https://rebrickable.com/parts/25692/sticker-sheet-for-42052-1/#comments