Permissions for Camera+Images / Product data - nest-api

I've requested to "Verify company" over a month ago so that I can get permissions on my developer account to access my own camera data. Apparently verification is still pending because I still can't add this permission to my developer account.
Is nest development still supported? The #nest twitter account referred me specifically to this tag on Slack for nest API questions when I inquired what needed to be done to get verification approved.

The answer to this issue is to request verification, REMOVE the current Camera permission, then add back the "Camera + images" permission. There can only be one permission at a time despite this not really being documented and apparently permission to add it is granted once you request verification, but this is not documented either. I was able to find something that led me to the answer over on nestdevelopers.io

"Verify company" is only for using the Resource Use API. As noted above, you can only have one camera permission at a time, so depending on your camera needs, only select the one that is most appropriate.

Related

Force permission on Google OAuth consent screen

I am currently developping an app which allows Google sign-in. We are asking permissions to get access to the users contacts (for invitation) and agenda (to create events).
Our app has been validated by Google a few weeks ago.
The main issue is that we would prefer to require our users to grant permission to access their accounts during the sign-in process, but we have a (rather long) list of checkboxes that the user must manually click on, which is a really bad UX.
I understand the privacy reason for that behavior, but I know that it is somehow possible, since I've tested that on another app myself (see below)
Google support is non existant on that subject, and the resources I found here or somewhere else are either deprecated or doesn't answer the question.
Have some of you encountered the same problem and fixed it?
Thanks a lot!
These checkboxes are due to the granular account permission change added in 2018. They are there to give the user the option to accept or reject your request, and can not be turned off.
You can read up on this in the original blog post. this Google Developers blog post

UnauthorizedAccessException for limited permissions user via REST API

not sure if this is the right place to post dev question so please point me to the right place if its not...
I have a customer that gave a user permission to one specific list.
for example:
https://[tenant].sharepoint.com/sites/qa/permissions/lists/tasks
The user cannot browse to the site:
https://[tenant].sharepoint.com/sites/qa/permissions
But he can get to the list with no problems.
When we try to get the list items using REST api, that user gets "UnauthorizedAccessException" error.
Rest API url we tried:
https://[tenant].sharepoint.com/sites/qa/permissions/_api/web/lists/getbytitle('tasks')
https://[tenant].sharepoint.com/sites/qa/permissions/_api/web/lists/getbytitle('tasks')/items
Users with at least read permissions on the site /sites/qa/permissions have no problems getting to both these API endpoints.
Is there a different way to make the REST API work for users with permissions to just one list?
Is there a limitation of the REST API and it does not support that?
Thanks!
(I posted this on technet as well, and will update here if I get an answer there)
You can deactivate the site collection feature Limited-access user permission lockdown mode.
When this feature is activated, users with "Limited access" as permissions have reduced permissions which prevent them from accessing the list item/documents properties. This will cause the Unauthorized Exception error while accessing SharePoint artefacts.
So, go to your Site Settings > Site collection features
And Deactivate the Limited-access user permission lockdown mode feature.
After that, refresh and check.
More details - Enable or disable site collection features

Instagram public_content permission

My app worked for a year and then the API calls to instagram stopped returning any data.
I use the following instagram endpoint:
https://api.instagram.com/v1/media/search?lat=48.858844&lng=2.294351&access_token=MY_TOKEN
I noticed I need the public_content permission but.. what Instagram requires in order to give me this permission? I couldn't understand anything from the documentation and they dissapproved my request for this permission.
The Instagram API Platform can be used to build non-automated, authentic, high-quality apps and services that:
Help individuals share their own content with 3rd party apps.
Help brands and advertisers understand, manage their audience and
media rights.
Help broadcasters and publishers discover content, get digital rights to media, and share media with proper attribution.
Best way to get public content permission is register an client application follow in one of those tree categories above, fill use case carefully with an screencast of you application and cross your fingers ;).
Leonel's answer is not correct. You get the public_content scope for your app by re-requesting an auth token with that additional permission. This has nothing to do with Sandbox mode or Live mode. This can be done for Live and Sandbox apps, but inclusiveness of the results will be determined by which mode you are in. Even when you have public_content scope for a Sandbox Mode app, you can only see the public content from sandbox users you invite to your client.
So Leonel is partially correct in the sense that the permissions problem may not even matter to you if you cannot get your client approved.
Read this short explanation of Instagram scopes and modes.

Error from Instagram: The access_token provided does not match an approved application

This was working fine for many months and now it's just a blank space. I get the following error: Error from Instagram: The access_token provided does not match an approved application. How can I get a new access_token for an existing client??
You need to check you application hasn't been put into sandbox by Instagram. They made big changes to their API on the 1st of June and if you had it submitted your app for review it will be put in sandbox mode and only sandbox users will be able to use it.
Even if you are not in sandbox mode you may need to get your users to reaurhorize your app due to new scopes being used to control access to everything other than basic user information.
Check Instagram Developer Docs for more information on the changes
You need to check your Access token's Scope and asking for login permission
where some new Scope had been added ex:public_content Added. Also don't forget to check for requirements Scope for API you are using and if it's need and Authentications "Valid access Token". where also had some changes.
basic - to read a user’s profile info and media
public_content to read any public profile info and media on a user’s behalf
follower_list to read the list of followers and followed-by users
comments - to post and delete comments on a user’s behalf
relationships - to follow and unfollow accounts on a user’s behalf
likes - to like and unlike media on a user’s behalf
And take look about **Sandbox API behavior of your application not life yet :**
API Behavior
The behavior of the API when you are in sandbox mode is the same as when your app is live, but comes with the following restrictions:
Data is restricted to sandbox users and the 20 most recent media from each sandbox user
Reduced API rate limits
The first point is important and it means that the API behaves as if the only users on Instagram were your sandbox users, and the only media ever posted were the last 20 for each of these users.
For example, if you query the /users/{user-id}/ endpoint and the {user-id} is a sandbox user, then you will get the normal API response; but if the {user-id} is not a sandbox user, you will get a APINotFound error.
As another example, let's consider an endpoint that returns a list of media: /tags/{tag-name}/media/recent. The response returned by this endpoint will contain only media with the given tag, as expected. But instead of returning media from any public Instagram user, it will return only media that belongs to your sandbox users, restricted to the last 20 for each user.
Good luck
The following video clearly explains what steps to follow to get this working with the new auth
https://www.youtube.com/watch?v=0k4RhTS94Hw
Kind Regards
Sandeep Sahoo

What are these brands, advertisers, broadcasters and publishers in instagram?

I need public_content permission of instagram, when i applied for it the team denied it with comment
public_content:
"This permission (public_content) is only granted to apps that enable brands, advertisers, broadcasters and publishers to discover public content. We do not grant access to apps that do not fall into these categories. Please review our documentation (https://www.instagram.com/developer/review) for more information."
This permission is needed and vary important for my plugin which uses below code to change username with their corresponding user id:
code:
'https://api.instagram.com/v1/users/search?q='.$this->username.'&access_token='.$this->access_token'
Now i want to know 2 things here:
1- Is there any alternative code for plugin to replace with.
2- What are these brands, advertisers, broadcasters and publishers in instagram.
No alternative, you must get your app approved.
Confusing as can be, don't understand it yet myself.
Makes no sense why people are downvoting the question. It's pretty valid.

Resources