Choosing WordPress REST API - ios

I'm developing an iOS client for a WordPress blog. Currently I am in the process of figuring out which REST API to interface with. It seems that these are the two main options:
https://developer.wordpress.com/docs/api/
http://v2.wp-api.org/
Has anyone who's built a WordPress client before have any insight on this?

Don't be confused, wordpress.org and wordpress.com are completely different organizations.
wordpress.com offers its own version of WordPress with custom features and API.
So if you host your site on wordpress.com, use their API. If your site is a self-hosted site, use WP REST API plugin.

The REST API has been added to the core in Wordpress 4.7, so if you update WP to the latest version, you don't need to install the WP REST API plugin.
The documentation can be found here now: https://developer.wordpress.org/rest-api/

Related

Integrating with QB Desktop products

I wrote a QB integration a few years ago that uses the Web Connector to read and write data to and from QB desktop products. It works well but I am not in love with the Web Connector.
I am tasked with setting up another QB integration. I was hoping to avoid using the Web Connector this time. There are a few reasons why I am trying to avoid the Web Connector but the main reason is I would like to make this integration work with both Desktop and Online versions of QB.
Is it possible to use the Intuit Sync Manager to sync the company data up to Intuit and then just use the standard Online APIs to connect to that company file? I have done some testing and I can connect to QB Online via the Online APIs but I cannot seem to get it to see the synced company files.
Any help with this would be great. Just looking for a little direction here.
Thanks in advance for any help.
For QBO, of-course, you can use QBO REST APIs(V3) API.
Ref - https://developer.intuit.com/docs/0025_quickbooksapi
But for QBD, QBSDK and web-connector is still the only approach.
QBD V2 and V3 REST APIs are already deprecated.
https://developer.intuit.com/docs/0250_qb
https://developer.intuit.com/docs/0250_qb/0010_get_oriented/0080_quickbooks_web_connector
FAQ
Thanks

Quickbooks PHP SDK Integration

Can anyone Plese help me regarding the Quickbook API integration
I have downloaded SDK from
https://majorapi.com/developers/quickbooks/sdk/php
I have installed it and configured the keys.
I've got some db tables when executing the Quickbook.php file.
I'm stuck there, can anyone please help me further.
If you're building a SaaS app (allowing other people to connect their QuickBooks companies to your app):
If you're building for QuickBooks ONLINE:
Instead of using that lib, use the QuickBooks PHP DevKit that's available on GitHub. It's open-source and well supported, and works fine with OAuth and v3.
You can follow the QuickBooks PHP IPP v3 Quick-Start Guide to get started. You'll go through a similar process to what you went through above, where you'll find in your own OAuth token/secret and app token in the configuration, and then you'll be able to connect to QuickBooks.
From there, you'll find several example scripts:
https://github.com/consolibyte/quickbooks-php/blob/master/docs/example_app_ipp_v3/
If you're building something else (something internal or for use only by a single company):
If you're building for QuickBooks for WINDOWS:
Here is a PHP QuickBooks Library which does exactly what you want to do.
You should follow the QuickBooks PHP Web Connector quick-start guide to get started. You'll want to architect your application so that your PHP script can receive the data, store it temporarily in a database (MySQL, etc.) and then the Web Connector can pick up the data destined for QuickBooks from there.
The Web Connector is a little different than a standard web service in that it works in a sort of backwards manner - the Web Connector will call out to your PHP web service vs. you calling out to it.
There's a overview of how the Web Connector works over here.
You should refer to these scripts (as the quick-start guide does above):
https://github.com/consolibyte/quickbooks-php/tree/master/docs/example_app_web_connector

SharePoint 2010/2013 restful webservices for native iOS mobile development

I'm planning to develop a SharePoint 2010 native iOS solution with some basic features like login and fetch content. Are there any RESTFul web services exposed by SharePoint to work on, which lists the RESTFul web services that we can use?
Is there any initial steps that I need to follow to start up, provided the RESTFul web services are available?
Thanks
Sudheer

Enable Web services in Redmine

Can any one guide me how to enable web services in redmine, specially XML RPC. And a proper way to implement such web service in redmine.
Thanks.
Parthiv
The REST API appears to have been integrated into the trunk a couple of days ago:
http://www.redmine.org/projects/redmine/repository/revisions/3310
http://www.redmine.org/projects/redmine/repository/revisions/3313
Check out Redmine's documentation, with links as to how to use the interface in Ruby and PHP:
http://www.redmine.org/wiki/redmine/Rest_api
However, I think there's only a REST web service interface now, no SOAP nor XML-RPC.

What's the best way to integrate Rails Restful Auth App Login into Wiki (MediaWiki?)

I have a ruby on rails app using restful authentication and I'm looking to add a Wiki to my site. MediaWiki looks like my best option since it's full featured and I can work with the LAMP stack. However, I'm not sold on MediaWiki if there's another (preferably open source) app that will integrate better.
I would like to know if anyone can suggest a way to integrate the login of my rails app with MediaWiki so users don't have to login twice or at the very least can have the same login credentials in both the rails and wiki app.
I've looked through the MediaWiki extensions but can't really determine which is the best solution. The current rails app is hosted on CentOS with enterprise ruby and phusion.
Perhaps not the cleanest solution but MediaWiki provides support for OpenID. Similialy, you can modify RESTful authentication to support OpenID here. This is discussed in the following post.
If both of your applications support OpenID then you've achieved your goals. If this is an internal solution, clearly this is not ideal.

Resources