I was trying to access Office365 Audit logs through Office365 Management API(Link). I have done most of the configurations as described in the link. I am able to get AuzreActiveDirectory audit data. But SharePoint and Exchange audit logs are not working.
Note: I have not used webhook. Does this has something to do?
Any help is appreciated.
webhooks are optional. Once you subscribe to a particular content type (EXO, SPO, AAD), you can periodically poll for new content using the /content operation.
When you first subscribe, there can be a lag before data is first available. Are you still not seeing EXO or SPO data?
Related
I am using DocuSign Open API'S to generate a report. Can anyone suggest which API I should use, if any?
I have tried to execute the API from DocuSign but a report API is not available.
Thanks in advance.
DocuSign does not have an API that allows you to access the web console's Reporting function.
Depending on what you're looking for, you can pull data from the Envelopes API.
DocuSign is developing a Data Feed API that will allow much more in-depth access to information. Data Feed is currently in limited, early access - I would recommend reaching out to your Account Manager or the Sales team if that is of interest to you.
Tirnuagari, these APIs are not yet public, but we hope to make them public soon. I can't promise an exact time frame, but I'll update this thread when I hear something from the team working on this. Thanks for your patience!
We are using Chatbase for multiple clients that we identify with a different version number.
See my previous question here: Track multiple context for the same Bot
We have a dashboard for all those clients and would like to show them their own data. A bit like Google analytics allows it.
So:
Is an API in the pipeline (I couldn't find any existing resources)
If not, in what alternative way could we get the data to present it?
We have a .csv export that is currently limited to the first 500 rows of your message variations report. It is on our roadmap to increase the scope of this report, however there is no official timeline for release.
Our recommendation for deploying an integration like you described in your message is as follows:
Have the user create a Chatbase account in order to obtain the API key
Have the user integrate their analytics on your platform by providing the API key
Send the messages from their bot to their Chatbase API
Provide the user deeplinks to the Chatbase reports from within your UI
Alternatively, you could configure your bot to send a redundant message to an internal database, or bigquery table to have access to all of your logs.
If you would like access to data you have sent to Chatbase up to this point, please contact chatbase-support#google.com and provide your bot's name and/or api key and we can provide a one-time export.
We're working on uploading businesses to Foursquare via the API option. We ran a test and have a question but first, here's some background on our situation:
We managed to get venues/add working however, we had issues with venues/claim.
When we attempted to claim a clinic which already existed on Foursquare,
we received the response code 403 and the following details:
{meta={code=403, errorType=not_authorized,
requestId=59416bb6db04f547b5e4b8a5, errorDetail=not authorized to
claim via api}, response={}, notifications=[{item={unreadCount=0},
type=notificationTray}]}
The API documentation indicates that the user performing this API call “Must be venue manager”. We don’t know whether our account is a venue manager and foursquare hasn't been too helpful in telling us if it is or isn't.
Can anyone please let us know how can we become a venue manager?
We are going to have approximately 2,000 locations uploaded via API and of that amount, we anticipate existing clinics to be a reoccurring theme so any insights in making this an efficient process would be greatly appreciated!
Venue claims are generally not available via API. Business owners will usually go through this page (https://foursquare.com/venue/claim) to claim their business.
If you're interested in claiming via API, please send us a note at api#foursquare.com!
We are doing an integration with DocuSign where users can submit documents stored in our system to DocuSign to get the documents signed. We have the DocuSign Connect feature working in our demo account. We can process messages from DocuSign successfully.
We were concerned that getting users to add a Connect Configuration themselves may be too challenging for some and it will be error-prone.
I see now in the documentation that it is possible to automatically get DocuSign to push notifications by passing the information in the EventNotification attribute when we call createEnvelope. Is this an acceptable way to get push notifications from DocuSign? Will this cause issues with getting the integration certified?
Is there any other way to get Connect configured easily in customer accounts?
This is an old question, but I wanted, for the record to have answers, since it's important to anyone who may be reading this.
We see now in the documentation that it is possible to automatically
get DocuSign to push notifications by passing the information in the
EventNotification attribute when we call createEnvelope. Is this an
acceptable way to get push notifications from DocuSign?
Yes, it is. It's a very good way in fact, to reduce polling and make your app better. We highly recommend that you use EvenNotification and sign-up for events going through a webhook to your app such that you can handle them in your code only when they occur, instead of polling DocuSign APIs repeatedly.
Will this cause issues with getting the integration certified?
The opposite is true. If you use polling you may have issues being certified. Using connect events with a webhook is one way to avoid the need for excessive polling which could cause issues with the certification.
Is there any other way to get Connect configured easily in customer
accounts?
You can configure connect like you suggested using EventNotification at the envelope level. This approach works well for ISVs since you don't need your customers to have admin access to their accounts.
The other option is account-level connect configuration, which does require admin level access and there are some other limitations. This approach adds the connect webhook for all envelopes in the account. So it may or may not be better, depending on your scenario.
I am getting information from client through internal portal and sending the request for envelope creation (along with details from client) from Server.
Everything is fine.
But the problem is with AUDIT history.
in the Audit history the IP address information is all SERVER information as server is the source for sending REST request.
But in my case Client is the one who provided the details.
I am trying to see if I can send the CLient IP address in the REST API so that it will inline with the actual events.
is this possible or reference to any achievable way is greatly appreciated.
Are you referring to Embedded Signing?
All entries are not changeable.
The Envelope is being created by your server, so you will not be able to change that.
You'll have the client's IP when they enter their signature.
See screenshot below for the web version of this info for a test document.
Unfortunately, I don't think it's possible to set the Client IP address via REST API. The information recorded to the Envelope Audit Trail is based upon data collected by DocuSign throughout the envelope's history. The fact that DocuSign records data exactly as it truly occurs is what gives credibility to the Audit Trail information, and therefore I wouldn't expect DocuSign to ever allow any of the Audit Trail properties to be set explicity via an API call. (Doing so would open the door to fraud, as an integrated application could use the API to falsify information in an envelope's audit trail.)