Search the Community

Showing results for tags 'set-parts'.



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 1 result

  1. 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