Skip to Content
Author's profile photo Former Member

SAP Jam developer community and OData API add flexibility for partners and developers

The new SAP Jam developer community

If you’re a partner or developer and you’ve wanted to customize SAP Jam or build integrations for your own customers, now you can.

For the May 2014 release of SAP Jam, we’ve created a new OData-based API that allows you to create innovations that support the company, departmental, or industry-specific needs that matter to your clients. They’ll be able to get social collaboration right where they work – including customized work patterns and in-context business data.


To support you and ensure your success, we’ve also created an SAP Jam developer community, where you’ll find the tools and documentation you need. Along with API reference documentation and sample code to help you get started, you’ll also get access to a special developer sandbox where you can create and test your new work patterns and integrations – and even submit support tickets for any bugs you find. You’ll also get access to a community of developers – and the SAP Jam team – and be able to provide feedback for future additions to our API.

For more information about the developer community, visit the SAP Jam developer community page.

The new SAP Jam OData API

In creating the API, we’ve considered requests we’ve received and also spoken to leading partners to ask what they need to do to address the needs of their customers. Taking that feedback into consideration, we’ve built the API to offer the following functionality.

  • Group manipulation
    • Create groups, read groups, update groups and delete groups
    • Copy groups
  • Group membership
    • Manipulate group membership (by adding or removing members), group admin data, or the group picture
  • Group content
    • Create, read, update, and delete group content like wikis and blogs
    • Create, read, update, and delete forums, questions, discussions, and ideas
    • Add or feature complex business objects to a group
  • Get notifications and accept or dismiss them

Non-OData-based APIs

We also provide REST endpoints to:

  • Create, read, update, delete kudos
  • Trigger and get usage reports
  • Create and delete bookmarks
  • Search SAP Jam

For more information about the OData API, visit the SAP Jam developer community page.

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member

      Just in time! We where waiting for this API & Doc update!


      Author's profile photo Former Member
      Former Member

      Hi Mika,

      I'm new on this topic (JAM), I'm investigating a possible integration on our system. What I really don't undertand is:

      1)Is there a way from API to know which version is installed on the customer JAM system?

      2)Which is the best way to make authorization against JAM? oAuth1.0a or SAML?

      3)Why, with the new API (oData), many of the previous methods are not provided anymore (eg: get feed list by user)?

      I'm currently Admin of the JAM application so I should be able to do any configuration wheter you will advise.

      I really appreciate your feedback!


      Author's profile photo Ruediger Mueller
      Ruediger Mueller

      Hi Massimiliano,

      On 1) SAP Jam is a cloud product. So there is only one version out there. Or are you interested in finding out the edition the customer has licensed? I am not aware of an API that returns that information (it can only be enterprise or advanced+ - all others don't include API access).

      On 2)Both work - it depends on your environment. Is your app capabable of securely storing an access token? Then you you can go for OAuth 1.0a, If you don't want each user to authorize access but setup system level trust you should go for OAuth with SAML

      On 3)I don't have an answer right away. Will need to follow up.



      Author's profile photo Former Member
      Former Member

      First of all, thanks a lot for answers.

      I found on Admin pages the following information. But from those I cannot infer which API version is installed:

      - Revision: R310_078160f_201501300732

      - Product Version:SAP Jam enterprise edition

      how to get API version? should I ask to my IS team?
      Could you explain better how the SAML authentication works?
      I've already read the documentation, but I have some trouble understanding the process.
      I know that I should register the oAuth client and then the IDP provider,
      but how could I get the X509 certificate and the single sign-on URL?
      Is it necessary that the JAM platforn should be configured in a particular way to allow SAML requests?

      I really appreciate your feedback, cause I'm struggling on this topic
      Author's profile photo Robert Horne
      Robert Horne

      The only important information that you need is that you have the SAP Jam enterprise edition. This means you have access to the API.

      With regard to SAML authentication, you need an actual SAML Identity Provider (IDP). Your SAML IDP would have all the configuration information including the X509 certificate that you would need to fill in the SAML IDP meta data in Jam.

      If you have a enterprise SAML IDP you would want to talk to the administrator to get that information. This is why I mentioned it might be easier use OAuth at least initially.

      Author's profile photo Robert Horne
      Robert Horne

      I'll add to Ruediger's comments.

      2. OAuth 1.0a requires end user interaction, but is a lot simpler to set up and POC. SAML should be used when you need true SSO. If you are just trying to POC something I would suggest OAuth 1.0a.

      3. The main reason we don't have full coverage of the old API is generally because of time and scope, but in some cases we have decided to approach things differently with the OData API.

      For example we don't really suggest that anyone consumes our feed API, because of its complexity. We suggest using one of our Feed widgets to embed in your application. This way you don't have to code to the full complexity of every feed type that we produce. But with that said we have a number of additions to our feed API capabilities coming up in our March release.