09-02-2017, 12:52 PM
I've had a few requests over the years for a UserSpice API. I haven't really known what to say when it comes to something like that because it's such a broad term and I can't think of one particular use case that everyone needs and you absolutely do not want an open API where people are hammering on your db if you don't know what you're doing.
Thoughts?
I've thought about showing people how to just write their own. My primary use case for mine is connecting my separate products together. I have a point of sale system based on UserSpice. I also have a camp registration system based on UserSpice. I need my point of sale to reach out to the camp registration system, see if the camper whose RFID wristband was scanned has enough money in their account to complete the purchase and if they do, subtract the money, record the transaction, and make the purchase.
Again...that's a super custom use case. Some people may want their users to have a limited number of API requests. Some might be server to server like mine. I'm just not finding that common scenario that I can build a generic API around.
My only thought was to add a table of tables in the db and if the table is in that list, it can be queried by the API. Maybe a second table of excluded fields like users->password. That's about all I can think of.
Thoughts?
I've thought about showing people how to just write their own. My primary use case for mine is connecting my separate products together. I have a point of sale system based on UserSpice. I also have a camp registration system based on UserSpice. I need my point of sale to reach out to the camp registration system, see if the camper whose RFID wristband was scanned has enough money in their account to complete the purchase and if they do, subtract the money, record the transaction, and make the purchase.
Again...that's a super custom use case. Some people may want their users to have a limited number of API requests. Some might be server to server like mine. I'm just not finding that common scenario that I can build a generic API around.
My only thought was to add a table of tables in the db and if the table is in that list, it can be queried by the API. Maybe a second table of excluded fields like users->password. That's about all I can think of.