Setting Access for Web Service Clients

Jive exposes much of its functionality as web services. Through a web service client, other applications can interact with Jive. In order for this to happen, you'll need to first enable one or more of the web service styles that Jive supports. To set up mobile access for Jive, see the Jive Mobile documentation.

Admin Console: System > Settings > Web Services

Settings

You can enable client access for the following kinds of web services:

Core API web services provide access to APIs using REST services. See the developer documentation for more information on using REST services. Core API web services are enabled by default. If you disable this, you will disable users' access to the Jive Apps Market and Jive Mobile functionality.
Bridging web services access lets other Jive communities create bridges to the current one. Note that you must enable bridging here for the bridging feature to work. (For more on bridging, see Connecting Communities with Bridges.)
OpenClient v3 is an alternative REST API for providing client access to Jive data. This feature is for customers upgrading to Jive 5.0 who need to support existing web service clients. Note that as of Jive 5.0, this API is deprecated and will be removed in the next major release.
Legacy Web Services provide access for clients using Simple Object Access Protocol (SOAP) and Representational State Transfer (REST) for core functionality. Note that as of Jive 5.0, this feature is deprecated and will be removed in the next major release.

You can set who will be able to access the community via web services. To restrict access to specific groups, for example, click Specific Groups, then type the names of user groups in the box provided, using commas to separate the group names. (For more on user accounts and groups, see Managing User Accounts and User Groups.)

Select Force SSL to require that all web services clients use Secure Sockets Layer (SSL) when connecting with your community. Note that the Force SSL setting governs access from bridge web services.

Note: Although requests from the Jive Desktop Office add-in can be filtered based on request URL (as described in Configuration Support for External Client Access), it can't be disabled or enabled from the admin console.