Snipe-it: API Endpoint for License seats

[marcquark]

Server (please complete the following information):

• Snipe-IT Version not relevant to the discussion
• OS: [e.g. Ubuntu, CentOS] not relevant to the discussion
• Web Server: [e.g. Apache, IIS] not relevant to the discussion
• PHP Version not relevant to the discussion

Is your feature request related to a problem? Please describe.
I'd like to be able to update license seats using the API, for example updating the assigned user/asset

Describe the solution you'd like
An endpoint, for example /license_seats. My must have requirement would be to be able to PATCH any seat by providing an ID and updated parameters in the request body.

Describe alternatives you've considered
Working directly with the database, i think that's a dangerous practice. Especially when updates are rolled out it might break the whole system.

Additional context
Add any other context or screenshots about the feature request here.

[sambernet]

First time looking into the API docs today because I was checking if we could use this to automatically assign seats to devices when running our automated provisioning process for new (or returned) devices.

Turns out that exact use-case we have is one of the few gaps in that otherwise quite cool API 😢

Agreed the "update DB directly" alternative is a very bad idea, unless you'd take down the system while doing that (which I suppose is not an option). In our case, being paid/hosted customers, that's obviously ruled out anyway 🙂

[snipe]

@sambernet It's on the list, I promise :)

[marcquark]

hey @snipe is there any way to get my hands on the demo dataset? i'd like to implement this but i need some data to work with

[stale[bot]]

Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!

[JeremyLee]

Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!

Yes, Mr stale bot, this is still relevant. :)

[stale[bot]]

Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know!

[sambernet]

Indeed it is, Mr stale bot!

[stale[bot]]

Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!

[iainhallam]

Still relevant.

[stale[bot]]

Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know!

[stale[bot]]

Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!

[JeremyLee]

Yes

[stale[bot]]

Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know!

[stale[bot]]

Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!

[iainhallam]

Yeesh!

[stale[bot]]

Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know!

[stale[bot]]

Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!

[JeremyLee]

of course it is

[stale[bot]]

Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know!

[BenRomberg]

We'd simply be interested to find out which users are assigned to a license using the REST API. Doesn't look like it's possible at the moment and might be another requirement that would make this feature request more valuable.

[JakobTewes]

+1 as we´d also love to see this feature implemented :-)

[simon-kerckhof]

+1

[whitelobster]

This'd be a huge help for me. I'm developing some custom reports that pull data from users, hardware, and licenses. Not being able to match license seats with users is a big roadblock for me.

[jkour]

+100 for this one

[stale[bot]]

Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!

[JakobTewes]

pleeeease

[stale[bot]]

Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know!

[MrMontesa]

One more +1 from my end.
We have planned for an automation that assigns licenses based on Active Directory groups. So we need to know who currently owns a license. As this info is available on the seats tab of the license view, I was expecting to have this in the API as well.
Would love to use this feature!
Thanks

[snipe]

We won't be able to address this until after V5, which we hope to have released in a few weeks. (RC will hopefully be out by the end of the week.)

[snipe]

(Also I have no idea why stalebot keeps closing this - "ready for dev" and "feature request" are configured as skipped tags, so it shouldn't have been closing this the whole time.)