API Call through Postman

If Postman still shows 404 on access_token call, then it’s most likely due to missing url rewrite rules (second link in my previous post)

Could you please make sure that it’s correctly set?

Yes, We have not used the URL rewrite rules in web.config. I have added the code in my web.config. Now our CMS is not working on opening the CMS it is showing the 500 - Internal server error.

Apart from adding the URL rewrite rules in web.config, kindly suggest if i am supposed to do something else also.

i think we have not installed the IIS module for URL rewrite. We are checking it.

We have installed the IIS module for URL rewrite. Now we are able to call the API through the Postman.

Thanks for your great support…

I’m glad to hear that, sorry that it took some time to find out what was missing, but with custom/manual installations and various server environments, as you see, there are couple of settings that might cause problems and it’s not always obvious where is the problem.

In any case I believe your installation should work fine now, it would be good to install and configure zeroMQ/XMR (if you haven’t already) as well, to fully utilise 1.8 features.

We have configured the ZeroMQ on our IIS Server. However On Report Fault page, we are still getting status “!” for ZeroMQ.

To Configure the ZeroMQ, We have followed the instruction mentioned in the below post.

I assume that you’ve followed the Windows instructions from http://zeromq.org/bindings:php ?

ie downloaded this and put in the appropriate folders (php directory and php extension directory), added the line to the php.ini and restarted your webserver?

we are doing the same. Can you please confirm the version of zeroMQ to be used as we are using the php 5.5.12 version. I think it may be a issue of version compatibility.

can you please explain what functionality will not work, if we don’t have ZeroMQ configured on our server?
We are asking this because we are still not able to configured in on our server.

Request screenshot - although it will work via xmds (same as older versions) in the next release - https://github.com/xibosignage/xibo/issues/1186

Other player actions listed here http://xibo.org.uk/manual/en/xmr.html

Hello Peter,

Now, We have successfully configured the xibo CMS. Can you please share the list of APIs that is available with xibo 1.8.1?

API documentation is here http://xibo.org.uk/manual-tempel/api/

It’s also linked in my API introduction guide.

I am trying to use Display Edit API to update the below parameters

  • Display Name
  • Display Description
  • Default Layout
  • Licensed
  • Email Alert

URL: {{url}}/api/display/3
Passing Values

displayId:3
display:NewDisplayName_API
description:NewDisplayDescription_API
defaultLayoutId:1
licensed:1
emailAlert:1

it gives me below error

{
“error”: {
“message”: “Can not have a display without a name”,
“code”: 422,
“data”: {
“property”: “name”
}
}
}

Ca you please suggest what i am doing wrong in it.

You will need to pass all required parameters ie:

You also do not pass displayId again it’s only passed in the call path.

All edit calls also need to be x-www-form-urlencoded

We are able to call display edit API. When we create the a user group from CMS front end, CMS asks me following inputs.

  • Name
  • Library Quota
  • Receive System Notifications?

We want to create a user group through API. But we have only copy user group API not add user group API. Kindly suggest…

Correct it’s not documented yet.

The GET userGroup call is wrong in the documentation it should be GET /group
as for post:

That being said I’d highly advise to use web ui to assign ACL to the userGroup

We are able to call user group create API. Thanks for your support.

We are trying to call the “Assign one or more Displays to a Display Group” API. But receiving nothing in response. Below is the postman screenshot. Kindly suggest if we are doing some thing wrong here.

We are not able to location any API to “Assign one or more users to a user Group”. Kindly confirm if we have this type of api available for xibo.

Assign displays to displayGroup (in this example we will assign 2 displays to displayGroupId 9)

[] there is important and I believe that’s what you were missing.

There will be nothing in the response I believe as there is no content, the response code should be 204 and obviously those displays should be assigned to the displayGroup.

Assign users to userGroup, that’s not documented yet, but should work in a very similar way to the above displayGroup example.

In this example we will assign one user to userGroup (id11)

Hope that will be helpful.

Thanks for your support.

We are also trying to see how many times & what time my displays were down.
can i get the these details through API or database?

For example, i want to see whether my devices were down today if yes, then i want to see the start time & end time of display down. There may be multiple occurrence of display down, I want to see the all occurrence.