compassInHand

Members
  • Content count

    2
  • Joined

  • Last visited

About compassInHand

  • Rank
    Level 1 Stud
  1. Exactly, from the Swagger docs page. During my testing the other APIs documented via Swagger have worked as expected, and coding against them returns anticipated results. It has only been this one API (again, via Swagger - I have not written any code against it) that returns 404. I did confirm the user and api keys are the same for all Swagger tests. The curl: curl -X POST --header 'Content-Type: application/x-www-form-urlencoded' --header 'Accept: application/json' --header 'Authorization: key ApiKeyHere' -d 'quantity=1&include_spares=false&set_num=65081-1' 'https://rebrickable.com/api/v3/users/UserKeyHere/sets/sync/'
  2. Question: has anyone been able to use the v3 user POST "sync" API on the Swagger page? The API in question (third from the bottom): /api/v3/users/{user_token}/sets/sync/ When I test it with a valid user token, passing valid entries for each field as well as a primary build set number (meaning, someSetNum-1) I get a consistent 404 response code. I have not tried calling into it with actual code, strictly trying to get the Swagger implementation to work first. I do not have any issues with any of the other APIs, no matter the verb. Any help / insight will be appreciated!