I asked myself, why for example there is no API for…
I think these are some missing one, which should be available 
What do YOU think?
You know further missing ones, which would be great to have? Lets talk about it 
You have other suggestions? → Let’s talk about it.
You have another (further) point of view? → Let’s talk about it…
Dude, bring me that cancelled plan API ASAP. This manual cancellation is painful. I would like a good clean up of collections, etc on a cancelled plan. I see it is under development but… so is Time Travel :-).
Would like to also be able to tell when a membership plan is still on the trial period as so far have not found a way. I would like to offer a “crippled” version during trial for example.
Great post BTW!
Yeah, i just have seen another little issue with pricing plans…to be found here…
It was about redirection also connected to pricing plans-APP.
Nice… what we seem to be seeing here from experience working with software and SAAS platform companies is a rush to get the feature to market, but then a slowness to build on the offering as there are other shiny toys that need to be released. What I see with the likes of the login and membership signups etc is the need to do custom work (considerable). The thing a platform like wix should aid partners in is allowing them to get a product to market quickly, i.e. a WIX site and the more time we spend faffing around on custom work, the less monies WIX makes on a new site popping up. The likes of paid plans, memberships and a few other things should be almost plug and play and five minutes they are done. Confirmation emails on sign up are another bug bear (unless I have missed that one).
And for my own purposes → i need the → Contact-deblock-API-command.
I ask myself, why it is not included? Is there a reason for it?
Seems there is/are some workaround(s) for this, but all that just to deblock a user?
-You can block a USER! → But NOT deblock again by CODE?
Ok, now i have the opertynity to go the -->“CURL-Way” → suggested by CCG , or a more simple solution what i thought of, was to delete the blocked user completely and recreate the account again (but here i have a problem of perhaps loosing some already existing user-data) → complicated? → YES !
Conclusion? → Time for a little bit more of useful APIs. 
Seems like anybody ecxept me and & Kyle are missing any APIs. Ok!
How ever, on my opinion there is still a lot of work to do, related to the given APIs.
Wix/Velo need an example? → No problem here it comes.
At moment, i am working with almost all Wix-CRM and Wix-Users-Backend-APIs, so it was just a question of time until i would find INCONSISTENT or even not existing APIs (which would be great to have them).
I already mentioned one of them in my opening-posts here.
However! → Investigating and testing the current given API a little bit more in DETAIL → i found my ERROR 
(sorry Wix/Velo), but i do it just to make Wix/Velo a little bit better 
, not to annoy you. 
Ok, what i am talking about???
I am talking about… the new getContact-API (not the depricated one!).
There is something missing!!! Follow the given SCREENSHOTS and you will understand what i mean!
What is missing, when you compare the given options from the CODE-AUTOCOMPLETION and the given RESULTS from BACKEND ???
Here one more time to be more precise…
Could someone update the CODE-AUTOCOMPLETION ? THANKS !!!
Since i am not a total beginner anymore, for me, perhaps it makes less problems to see such errors poping up in front of my eyes (althoug!!! sometimes such errors irritate me a lot, too), but for those who is beginner, he will surely loose a lot of time to solve the problem at this point, or even will totaly give up!!!
Thanks for hearing my voice! (I am sure Velo-Officer M.M. will have read this post soon 
).
Let me know, when this little issue (which surely can be fixed in few minutes) has been fixed.
Also, the ability to get site at a given point in time. Im not as experience, but have not found anything. So, summary:
Also, the ability to get site at a given point in time
What do you mean exactly? Can you describe this situation a little bit more?
Ok, another one…
Wouldn’t it be great to have the —> “roleID” INSIDE ???
I am sure, that i have mentioned this already earlier, but can’t find the related post anymore
Or even get all role-IDs at once, would also be great, wouldn’t it?
EDIT:
Found the right post…
@russian-dima Number of active sessions connected to the site - the volume of activity from those who don’t log in - typical web stats, etc. Maybe an API that gets the total sessions for that day. Maybe there’s something already in existence. I’m pretty new to WIX.
Yes, this is surely an interessting stuff!
Already took a look here…?
https://www.wix.com/velo/reference/wix-router
Perhaps there is something you can use for your purposes → NOT SURE! (never worked with wix-routers, yet), but will inspect them surely in the future.
@russian-dima Will have a squizz… cheers!
Possible RESULTS of an API, which collects all DATA of Single/All-Users/Contacts…
Surely there is even more possible.
Thanks for all your feedback here, but please submit feature & API requests to the Velo Wishlist so other users can vote for the requests. Requests that collect the most votes are most likely to be developed, and we also monitor the wishlist to get use cases for new features on the roadmap.
When submitting a request, please provide a descriptive use case to help our product managers easily understand what it is you’re trying to build. Thanks!
@marlowe-shaeffer
Hello Miss Marlowe, i knew you will find this post
The last time i tried to use the Velo-Wishlist, i figured out → that the VELO-WISHLIST is not TRANSPARENT. Comments are hidden as i can remember. There was something, that kept me from submit it to the VELO-Wishlist.
So i will try it again, if in the past time something has changeg, regarded the VELO-WISHLIST.
I will follow your suggestion and will add it to the wishlist.
https://www.wix.com/velo/wishlist
BTW: Now i know again → why i did not use the VELO-WISHLIST.
Every new created WISH, is even not shown on the wishlist.
Instead the new ones —> should be on first place, or at least there should be a possibility to find the —> NEWEST-WISHES in the SEARCH.
So one of my mentioned missing APIs is now in the wishlist, can you find it?
@russian-dima Hi Dima! Requests and comments are subject to an approval process, so there’s a chance an item either wasn’t reviewed yet or was rejected. We’ve recently set up rejection messages so that users know why their request was rejected—usually it’s because they submitted a Wix feature request (not Velo-related), or the request already exists in the Velo Wishlist.
I monitor the Wishlist submissions, so I’ll keep an eye out for any requests coming in from you. Thanks!
@marlowe-shaeffer Ok! There will be more ones in the wishlist, created by me soon.
But what would/could be a good option …
An OPTION for —> Newest-Wishes, so anybody has to search for them.
And also everybody would see, that this wish is already in the wishlist.
Just on my own example → I know roughly, which wishes already are existing in the list, but can’t see the new ones which were last added (can i???).
And this causes the problem, that i accidently can request for a wish, which is perhaps already included inside the wishlist.
Short conclusion → A better SEARCH-OPTIONS or better Overview of the current WISHES, could solve the little issue.
But thanks anyway for your suggestions and useful informations, i like them.
@russian-dima Most Recent means the same as Newest, and choosing that sorting option will show the latest items added to the Wishlist, as shown here:
@marlowe-shaeffer
Ok, i understand now. But anyway → the wishlist has been changed.
When you have added a new Wish to the wishlist in the past (as i can remember) the wish was immediately inside the list.
How do i know this? Well, about a YEAR ago, i already sugested for example this one…
But thats not really the only one and main reason, why avoiding the wishlist.
Regarding onto the WISHLIST, i can surely do the statement, that perhaps just 10% of all VELO-USERS uses the wishlist → as for doing a submission for a new wish well as voting for one of the existing ones.
Conclusion: (Almost) anybody uses as frequently the wishlist, as it perhaps should be used. Especially the VOTINGS are very rare.
Open a post related to the wishlist-topic —> is like to make some 
. Then also the VELO-USERS awake to a new life.
Perhaps, after reading this post → There will be more potential VOTES for existing WISHES .
I know the wix-velo-team is surely working already on new APIs, but perhaps it could happen a little bit more frequent & fast enough.
When you take a look, into the —> PRO-DISSKUSSION → you will find a post, created by the well known “Code-Queeny”. She asked a question, which is a GOOD one!
