Is "Enumerate sites" out of beta? - sharepoint

The Graph API docs mention that site enumeration is available in beta: https://learn.microsoft.com/en-us/graph/api/site-list?view=graph-rest-beta&tabs=http That page is not available in v1.
However, when calling https://graph.microsoft.com/v1.0/sites I got get a response, and, in fact, get almost all sites.
I'd like to know if site enumeration is indeed out of beta and safe to use in production apps.

It's not recommended to use beta endpoints in production apps. You can have a try below method to get all sites:
https://learn.microsoft.com/en-us/answers/questions/113056/microsoft-graph-api-fetch-sharepoint-sites-new-sit.html

Related

API versioning in strapi

so by default strapi puts APIs into the api folder. But what if i want to version my APIs like v1/v2/v3 etc?
I didn't see any file that has the route to api folder.
Unfortunately, there is no api versioning provided by Strapi right now, but the feature is to be added soon and is there in their roadmap. Refer to their productboard here.
If you scroll down in the page mentioned above, you could see the idea request

How to enable Vulnerability alerts through the GitHub API or GraphQL

I have searched high and low, but I can't find anything telling me how to enable GitHub Vulnerability alerts through their API. I conversely can't find anything saying it's not supported.
Does anyone know where I can find the API documentation if it is supported, or can someone tell me it's not? I have just completed a migration to GitHub for my origination and we have ~750 repositories so enabling them all manually is... less than ideal.
we released an API for this scenario a while back, so you can now enable or disable security alerts in bulk using that. We also published a sample which calls that API for all the repositories in an organization.
API: https://developer.github.com/v3/previews/#enable-or-disable-vulnerability-alerts-for-a-repository
Sample: https://github.com/github/enable-security-alerts-sample
#Russ looks like it's only available according to the UI. I am in the same position in needing to enable this for a very large number of repos.
Take a look at: https://github.community/t5/GitHub-API-Development-and/Security-vulnerability-alerts/td-p/15846
I got this from my companies GitHub service rep:
Enable security vulnerability via API (v3 or v4)
I've raised this and currently in conversations with the team that is responsible for
this feature to see when this could be addressed. I have to say this
is an exception to the GitHub rule of API/Platform first. I apologise
for that.

Privacy Policy URL - What if I use it for the owner's website only?

So, apparently I need to provide a Privacy Policy URL for my Instagram application.
The only reason I'm using this application, is for a website I built for a client of mine. The client wanted an automatic integration for her Instagram, so I went through the whole Instagram API hassle.
Now, the website is ready for production, so I wanted to get my app out of sandbox mode, but it looks like I need this Privacy Policy URL.
What's the best way to go about this?
Put a Privacy Policy page up on their website (really any website you can link to) and use that link. It can be a static HTML page, as long as you can link to it.
Instagram won't let you take an application like this out of Sandbox, btw. Your use case is not an approved use case. From Instagram's Developer Documentation under Invalid Use Cases:
One-off Projects. If you are an agency building websites or other integrations, note that we don't grant permissions to clients created for one-off projects. If you are interested in building a product, platform, or widget that will be used as a service across multiple projects, then you may submit a single client_id that you can use across multiple projects.
You can (probably) still achieve the outcome you're looking for but you will need to go back to the drawing board and rethink your application's use case before getting out of the Sandbox. I know some developers who really just don't understand (or care to understand) the policies and never make it out of Sandbox. It's a shame because they can read the technical portions of the documentation so easily but just can't/don't read/understand the more critical parts (like the Invalid Use Cases section).

Can I use Yandex Maps in a Nokiax app?

I need to use Yandex Maps in an app instead of Here Maps. Could this be possible? Any hints or tricks to help me?
Thanks
Basically the rules of using APIs is very simple. If the API is not requiring any parts that are not available in the platform, then it works.
Thus if the API is using parts that are supported in AOSP 4.1.2 API level 16, and using any Google services, then it is likely to work just fine.
And you can always check the compatibility with free online tools very easily. First go to Online Analyser drag and drop the APK there, and let the tool check the compatibility issues.
Then you can also use a real device for testing, just visit Remote Device Access, and reserve a device for testing your app.
Both steps should onlky take you couple of minutes to complete.
For Yandex maps, you would need to visit their developer site to see how the maps API can be used, and what restrictions they would pose on utilizing the API.

Using ServiceStack with a ServiceReferenceClient

I'm trying to call ServiceStack service from a console app with a service reference client (generated after using Add Service Reference in VS 2010).
I looked at the sample at github but was unable to create a similar client code.
My objective is to provide a set of services with a simple API that can be called by a .NET client as easy as possible. Ideally, client should not need any knowledge of ServiceStack to call the services.
My questions are:
How should I create request if the service does not need any parameters?
How can I resolve proxy.Properties?
Here is the gist
You can use SOAP/WSDL's Add Service Reference but you should be mindful of SOAP's Limitations.
Although the current recommendations for client libraries is to use your preferred choice of ServiceStack's built-in generic service clients.
Got it working, updated gist Removed properties, version, request

Resources