REST API Query parameters not working for events endpoint (/admin/v1/orgs/{orgId}/events)

[kumarak]

The REST API calls with query parameter `to` and `from` does not return any results for the events endpoint (/admin/v1/orgs/{orgId}/events). 

The API documentation does mention these parameters and I would like to use them to filter events. (https://developer.atlassian.com/cloud/admin/organization/rest/api-group-orgs/#api-orgs-orgid-events-get)

I am using `curl` to query the results. The query calls for me looks as shown below.  The date and time are provided in the Unix timestamp format.

curl --request GET --url 'https://api.atlassian.com/admin/v1/orgs/{orgId}/events?from=1634642484&to=1634828884' --header 'Authorization: Bearer <API-Key>'

There are events generated in this time interval but the API call shows no results. Could you look into it and let me know if I am doing something wrong? 

This is what I see as output. It does not show any error. I am using an account with the trial plan for testing. 

{"data":[],"links":{},"meta":{"attributes":null,"next":null,"prev":null,"page_size":30,"start_index":null,"end_index":null,"total":0}}

[Craig Castle-Mead]

Hi @Phil Tayles 

You are correct - there is no way to enforce SSO by product automatically. Access is about securing user accounts, not enforcing policies by product/instance.

Access now gives you the option to auto claim all accounts for a domain, or selectively, so you could move to selective claim and then only claim users you know are using Jira, however this means your users are “unsecure” by default, so I’d recommend auto-claiming all users for the domain and manually adding users you know are only using Trello to your non-billable/no-SSO policy. Users can obviously go from being Trello only to also using Jira, so this would need to be monitored on an ongoing basis to be accurate. The formal REST APIs for Access admin functions do not have feature parity with the UI either, so even scripting some of this (get all users and products, ensure appropriate users are in expected policies based on product access) is not a viable path. 

CCM