In a previous post, we discussed how we can get objects by path before and why that would be of use in certain situations.
You can also get objects by ID and in some cases that’s what you want to do.

What do you need?

Getting started is just as easy as when we showed you how to get started with getting objects by path. This time, we will be passing the id in the path of the GET request and not as a query parameter. You can use the /.api/api.svc/objects/byPath?path=/my/path to get the object id for…

Currently, the API v1 endpoints that retrieve object contents for a Forum Topic article, Wiki Article or Document increment the view count.  While this makes sense if you're building an integration that consumes content, it also causes problems if you're building an integration that is meant to drive users to that content.

We're excited to announce new Object Summary API endpoints that will be available in the next release (currently targetted for July 10) that will allow your integration to…

Today, as part of our Customer Care evolution, we’re pleased to present the new Igloo Developer Center. Our biggest update ever!

 We’ve worked hard to make it easier to find information and deliver new content - along with a better user experience.

  A few highlights include:

• A complete revamp of our API documentation.  We’ve standardized on Swagger / OpenAPI – and these documents are generated and updated directly from our codebase – so they’re always up to date.
  
  
  

• New content in the “get…

It can be cumbersome inspecting the DOM to get an object’s ID. Luckily we can use an object’s URL path to query objects for their information. Using the /.api/api.svc/objects/byPath?path=/my/path endpoint you can get object data from Igloo without the need for an object ID.

What do you need?
Getting started is straight forward enough. Find the URL path of the object you want to query and pass it as a query parameter in your GET request. You don't need the entire URL path, only everything after…

First things first

For us to build a widget that displays group specific content, we must first create or repurpose a group. Remember to add some users to the group!

Let’s start coding

The first thing that we need to do is create an object with the groups you’d like to target content for. In this example we’ll add one property to our groups object - ITGroup. We’ll also populate this property with the group’s ID.  While we’re doing this statically in our example, a great improvement would…

What’s Axios?

Axios is a powerful promise based HTTP client available for your browser and node.js. It allows you to easily make API calls to content or data endpoints in your digital workplace without having to worry about re-authenticating. Every Igloo digital workplace has Axios available to widgets it out-of-the box.

How can I use it?

In our example, we’ll build a widget that displays the 10 most recent blog posts in a channel.  

Let’s dive into some simple code:

We’ll focus on lines…

What are integration widgets?

Integration widgets are custom built elements that help you empower your users by bringing additional functionality to your digital workplace. They’re a great way to surface functionality that would otherwise require users to navigate to locations outside of a digital workplace. Integration widgets from the Marketplace are often built by third parties, partners and sometimes even customers.

Where do they come from?

It starts with our Product team

In many cases,…

Who Are You? – Authenticating To Igloo

Making any API call against IGLOO requires you to authenticate. Authentication creates a session key which holds the context of the user who authenticated. If you create a blog while authenticated as Joe, the creation event will be attributed to Joe.

Authentication requires that you have:

• an appId and an appPassword 
• a digital workplace and user credentials

These are provided to you when you register as a developer. 

Authenticating using…

What is the Integration Widget?
If you’re anything like we are, then your organization uses a lot of tools. Some of them are commercial, and some are custom built.  Isn’t it frustrating to have to go http://here.com for one thing and http://there.com for another? 

Wouldn’t it be great if you could surface the functionality of various services in one place? 

The Integration Widget might be your ticket to digital nirvana.  It’s an easy way to integrate your digital services, used every day in your…