Home › Forums › Welcome! › Pre-Sales Questions › All Event Data in REST API?
- This topic has 6 replies, 3 voices, and was last updated 9 years, 6 months ago by
Support Droid.
-
AuthorPosts
-
October 8, 2016 at 9:46 am #1174100
Michael
ParticipantWanted to follow up on this post from a while ago, https://theeventscalendar.com/support/forums/topic/wp-rest-api-v2-endpoints-for-all-event-data/, to see where things are at. Is this possible yet?
We’re looking at this again in a bit more detail now so hoping that this is now possible?
If not, any ideas on rough timelines for when this is going to be available?
Regards,
MichaelOctober 8, 2016 at 7:34 pm #1174187George
ParticipantHey Michael,
Thanks for reaching out!
As Brian noted in that original forum thread, we are not supporting the REST API until the rest of the endpoints are merged into core. At this time, the REST API is still not fully integrated into core—to much controversy and community agita, I’m afraid. 🙁
REST API integration will be a priority once it is available within core, but until that time, it is unfortunately not possible nor do we have a definitive timeline for the release of full API integration.
Sorry to disappoint here, Michael. Please let me know if there’s anything else I can try to help out with.
Sincerely,
GeorgeOctober 9, 2016 at 11:13 am #1174288Michael
ParticipantIs it this we’re waiting for, https://make.wordpress.org/core/2016/10/08/rest-api-merge-proposal-part-2-content-api/ ?
Regards,
MichaelOctober 9, 2016 at 4:23 pm #1174340George
ParticipantIf that proposal ends up being a reality, and the REST API arrives in WordPress Core, then yes, after it arrives in Core we will start the process of integration with the REST API. Though the integration process itself will take some considerable time.
Just to set your expectations, Michael, we’re talking a timeline of several months to a year here, if all goes to plan and arrives on time and such.
Again: sorry to disappoint! I hope this information is clear and helps you proceed nonetheless.
Sincerely,
GeorgeOctober 10, 2016 at 1:15 am #1174400Michael
ParticipantThanks George, that makes sense. Good to know rough timelines so we can plan for this accordingly with the project we have this in mind for. I know its not a small job to do this at your end and it makes sense to wait for the WP core updates first to avoid duplicating work.
We’re currently using the WP REST API as a backbone to drive the content in an iOS App and an Android App, so the next step is to upgrade this to allow people to book on events via the app too and hence this requirement. With the timelines still likely being another 12 months, we may have to look at opening up the protected meta fields to the API as Brian mentioned in the older thread for the time being then tweak this a bit once the full end solution is here.
Thanks for the help. Will have a discussion internally and see which route we end up going down.
Regards,
MichaelOctober 10, 2016 at 12:32 pm #1174610George
ParticipantSounds good, Michael. I appreciate your patience here despite the disappointing news; it’s indeed a big project, and who knows—maybe we’ll be able to have REST API integration before 12 months, maybe beyond 12 months…but I just wanted to convey the timeline is a long line, whatever it ends up being in actuality.
Your project sounds interesting and I’m sorry there isn’t enough REST API support from our plugins or WP core at this time to buttress it!
I’ll close this thread for now; open a new one any time if other questions or issues arise.
Best of luck with your project!
Sincerely,
GeorgeNovember 1, 2016 at 9:35 am #1185860Support Droid
KeymasterHey there! This thread has been pretty quiet for the last three weeks, so we’re going to go ahead and close it to avoid confusion with other topics. If you’re still looking for help with this, please do open a new thread, reference this one and we’d be more than happy to continue the conversation over there.
Thanks so much!
The Events Calendar Support Team -
AuthorPosts
- The topic ‘All Event Data in REST API?’ is closed to new replies.
