This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice This article is not considered official documentation for K2 software and is provided "as is" with no warranties.


After enabling the K2 OData API Feed in the K2 Management site and opening the URL, no SmartObjects are displayed, only the <workspace> tag and nothing underneath.

It looks like this:

<service xmlns="" xmlns:atom="" xml:base="">


<atom:title type="text">Default</atom:title>



It should look like this:

<service xmlns="" xmlns:atom="" xml:base="">


<atom:title type="text">Default</atom:title>

<collection href="SMO_Name">

<atom:title type="text">SMO_Name</atom:title>





We tried the following options to resolve the issue:


- Add the K2 SmartForms Application Pool account into the API Management Security.


- Restart the K2 Service

- Checked the "Considerations" section here.

- Checked the "Default List Settings" here.

- Gave the K2 SmartForms Application Pool user account Export Rights in K2 Management

- Checked that the K2 SmartForms Application Pool account has SmartBox Load and GetList permissions on the following two objects:
“Published Objects”

- Tried to install K2 Five 5.0 FP25 and K2 Five 5.1 but both resulted in other issues happening

- As per:

Q: Can I change the connection pooling setting to improve performance?

C:\Program Files (x86)\K2 blackpearl\WebServices\Identity\Sts\Windows\Web.config

Change the following value to true: 

<add key="ConnectAsAppPool" value="true"/>

- Go to the Management > Integration > SmartBox Object
Make sure the app pool account has at least Load and Get list permissions on SmartObjects.WebEndpointPublishing.Management.Settings

None of the above worked.

The next step would've been to get a lot of log files, like HostServer, SmartObject and SQL Profiler Trace logs. We would've also needed the following file:

C:\Program Files (x86)\K2 blackpearl\WebServices\API\SmartObjectService.OData\web.config


The solution to this issue was finally found in the following community article:

The following resolved the issue - manually refresh the URL:


For example: