Free tools Windows power users keep installed
One-click scans. No signup required.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Authenticate every Display & Video 360 API request with an OAuth 2.0 access token, then let Display & Video 360’s own user provisioning and role assignments determine what that token can do. The working identity chain is: a Google Cloud OAuth client creates consent or service-account credentials; the credentials request a DV360 scope; Google issues an access token; and DV360 checks whether the represented Google Account is a DV360 user with the required role and access to the target partner or advertiser. Use https://www.googleapis.com/auth/display-video for ordinary read/write operations. Methods in the users service also require https://www.googleapis.com/auth/display-video-user-management. No API key or alternative authorization protocol can replace OAuth 2.0.
What authentication does the Display & Video 360 API use?
The API supports OAuth 2.0 only. Every request must carry an authorization token, normally as a bearer token in the HTTP Authorization header:
Authorization: Bearer ACCESS_TOKEN
Google’s authorization documentation says that every request to the Display & Video 360 API must include an authorization token and that no other authorization protocols are supported. An API key, a username-and-password exchange, or a token minted for an unrelated Google API will not authenticate a DV360 request.
Recommended Free Tools
Authentication and authorization are separate checks:
#1 Best Overall
- Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
- With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
- Wide Application: attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
- Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
- Economical &Reusable: Built durable materials with a long-lasting battery,our CAGIWIRU air duster it's a sustainable alternative to disposable air cans.
- Authentication proves which Google Account or service identity is represented by the token.
- Authorization checks the OAuth scope, the account’s DV360 role, and its access to the particular partner or advertiser resource.
A valid token can therefore still receive a permission error. The token may identify a real Google Account while that account is not provisioned as a DV360 user, lacks access to the requested partner, has an insufficient role, or is missing the user-management scope.
Which OAuth scopes should I request?
Request the narrowest scope that covers the methods your integration will call.
| Scope | Use | Additional requirement |
|---|---|---|
https://www.googleapis.com/auth/display-video |
Ordinary Display & Video 360 API read and write operations. | The represented Google Account must be a DV360 user with access to the relevant partner or advertiser. |
https://www.googleapis.com/auth/display-video-user-management |
Methods in the users service, such as managing DV360 users. |
Use an identity that is a DV360 user with an Admin role at the target partner, in addition to configuring this scope. |
The user-management scope is not a substitute for the ordinary DV360 scope. If an application calls regular campaign, advertiser, or partner methods and user-management methods, request both scopes and ensure the account’s role supports each operation. If it never calls the users service, do not request the extra scope.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →What must be configured before the first API call?
Prepare both sides of the access boundary: the Google Cloud project that owns the OAuth client and the DV360 account that grants resource access.
Google Cloud project prerequisites
- Select an existing Google Cloud project or create a new one that your team controls.
- In the Google Cloud Console, open APIs & Services > Library, search for Display & Video 360 API, and enable it.
- Configure the OAuth consent screen for the application. Use the application identity and support details your operators will recognize at the consent prompt.
- Open APIs & Services > Credentials, choose Create credentials > OAuth client ID, select the application type, and download the client-secret JSON. Treat that file as sensitive; do not commit it to source control or send it through chat or email.
Display & Video 360 prerequisites
- The Google Account used interactively, or the identity represented by a service account, must be provisioned as a Display & Video 360 user.
- That DV360 user must be granted access to the exact partner or advertiser that the request addresses.
- The DV360 role must match the operation: Read only for retrieval-oriented access, Standard for most ordinary retrieval, creation, and update operations, or Admin for user-resource administration.
Enabling the API in Cloud Console does not grant access to any DV360 partner. Cloud configuration permits an OAuth client to request a token; DV360 provisioning decides which resources that token can reach.
Rank #2
- Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
- Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
- Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
- Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
- Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth
How do I set up an interactive OAuth application?
An installed application, desktop tool, web application, or operator-run integration can use a human Google Account. The operator signs in and grants consent, and the resulting credentials are used to obtain access tokens.
- Create or select the Cloud project. Confirm that the Display & Video 360 API is enabled in that project.
- Configure consent. Set up the OAuth consent screen and identify the application clearly. Request
https://www.googleapis.com/auth/display-video; addhttps://www.googleapis.com/auth/display-video-user-managementonly if the application will call theusersservice. - Create the client. From APIs & Services > Credentials, create an OAuth 2.0 client ID for an installed app or web app, according to your integration’s execution environment. Download the client-secret JSON and store it securely.
- Run the authorization flow. Send the operator to Google’s consent prompt. The operator signs in with a Google Account that is already a DV360 user and approves the requested scopes.
- Store the resulting credential securely. Your OAuth library uses the authorization result to obtain an access token and, where the flow provides one, a refresh credential for later token acquisition. Keep credential storage server-side or in the operating system’s protected credential store.
- Construct the DV360 client. Configure the client for the Display & Video 360 API and attach the access token as a bearer token on every request. The documented v4 discovery document is available at https://displayvideo.googleapis.com/$discovery/rest?version=v4.
- Test with a read. List a resource that the signed-in user can access. Confirm that the response belongs to the expected partner or advertiser before attempting a create or update call.
- Expand privileges only when needed. Add write calls after read access works, and add user-management calls only after the additional scope and Admin role have been verified.
The account selected at the consent screen matters more than the person who created the Cloud project. If an operator signs in with a Google Account that is not a DV360 user, the OAuth flow can complete while subsequent DV360 calls fail authorization.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →How do DV360 roles affect what a token can do?
OAuth scopes describe the API surface an application may request; the DV360 role limits what the represented user may actually perform. The effective permission is the intersection of both.
| DV360 role | Retrieval | Create or update | User resources | Scope and level notes |
|---|---|---|---|---|
| Read only | Retrieves most resources. | Not permitted for normal write operations. | Excluded. | Use for read-oriented integrations. |
| Standard | Retrieves most resources. | Creates and updates most resources. | Can retrieve User resources. | Does not provide the Admin capability required to create or update User resources. |
| Admin | Retrieves resources. | Creates and updates resources, including User resources. | Retrieves, creates, and updates User resources. | Available at partner level; required for user administration. |
A Standard user can have the ordinary display-video scope and still be unable to change users. Conversely, an Admin user without the display-video-user-management scope cannot successfully call methods that require that scope. Both conditions must be satisfied.
Can I use a service account for unattended jobs?
Yes. Google documents two service-account patterns: associate the service account directly with a DV360 user, or use domain-wide delegation to impersonate a Workspace user. For a scheduled job that needs one stable identity, direct association is generally the simpler model because it avoids impersonation and domain-wide delegation policy.
Rank #3
- 【Large size】:Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
- 【LED backlight mouse pad】:Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
- 【Anti-slip rubber base】:Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
- 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
- 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.
Directly associate a service account with a DV360 user
- Create a service account in the Google Cloud project that has the Display & Video 360 API enabled.
- Use the service account’s email address when provisioning a Display & Video 360 user, and grant it access to the target partner or advertiser.
- Assign the role required by the workload. A job that manages DV360 users needs an Admin role at the target partner.
- Configure the application to request the required OAuth scope. For user-management methods, include
https://www.googleapis.com/auth/display-video-user-management; includehttps://www.googleapis.com/auth/display-videofor ordinary API methods. - Generate or obtain service-account credentials through your approved key-management process, then use the service account to mint OAuth 2.0 access tokens.
- Send the resulting bearer token with each request and test a read against the partner or advertiser before enabling writes.
The service account acts as the provisioned DV360 user. Its Google Cloud ownership does not, by itself, confer access to any DV360 resource.
Use domain-wide delegation when impersonation is required
Domain-wide delegation lets a service account impersonate one or more DV360 users in a Google Workspace domain. It is appropriate when your organization needs an automation identity to act as existing domain users rather than as one separately provisioned service-account user.
- A Workspace administrator must authorize the delegated OAuth scopes for the service account.
- The users being impersonated must be linked to accounts under that same domain.
- The application must select an impersonated user from that domain.
- The impersonated user must itself have the required DV360 provisioning, partner or advertiser access, and role.
Delegation adds domain-level impersonation power. Keep the delegated scope list narrow, document which users can be impersonated, and review the administrator authorization independently of the DV360 role assignment.
How do I manage DV360 users through the API?
User-resource operations have two extra gates: the user-management OAuth scope and an Admin DV360 role at partner level.
- Provision the calling identity as a DV360 user. For a service account, associate its email address with a DV360 user; for delegation, identify the Workspace user that will be impersonated.
- Grant that identity Admin access to the target partner.
- Request
https://www.googleapis.com/auth/display-video-user-managementin the OAuth flow or service-account token configuration. - For calls that also touch ordinary DV360 resources, request
https://www.googleapis.com/auth/display-videoas well. - Test a permitted user-resource retrieval before attempting create or update operations.
A token with only the ordinary DV360 scope can work for campaigns or other standard resources and still fail every call in the users service. Likewise, an Admin role without the extra scope is insufficient.
Rank #4
- 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
- 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
- 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
- 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
- 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.
What is the difference between interactive OAuth and service-account authentication?
Both patterns end with an OAuth 2.0 bearer token, but they represent different identities and operational controls.
| Decision point | Interactive OAuth user flow | Service account or delegation |
|---|---|---|
| Consent at run time | A human signs in and grants consent; suitable for development and operator-driven tools. | A directly associated service account does not require interactive consent at run time. Delegation requires administrator authorization in the Workspace domain. |
| Identity in DV360 | A human Google Account provisioned as a DV360 user. | A service account associated with a DV360 user, or an impersonated Workspace user. |
| Best fit | Desktop applications, web applications, and workflows where a person initiates each session. | Scheduled jobs, back-end services, and unattended automation. |
| Primary controls | OAuth scopes, the signed-in user’s DV360 role, and that user’s partner or advertiser access. | OAuth scopes, service-account provisioning, the DV360 role, and—when delegated—Workspace domain policy. |
| User management | Requires the user-management scope and an Admin DV360 user. | Requires the user-management scope and an Admin DV360 identity, whether directly associated or impersonated. |
Choose the human flow when accountability to an operator and an interactive consent decision are central. Choose a service account when a job must run without a person present, then decide whether direct association or delegation is the smaller security and administration boundary.
Why does my DV360 API token get permission denied?
Work through the identity chain in order. A failure at an earlier layer can look similar to a role failure, so classify the HTTP response and the resource being requested.
| Symptom | Likely cause | What to check |
|---|---|---|
| 401 Unauthorized, missing-token, or invalid-token behavior | The request has no usable OAuth 2.0 access token, or the token was minted without the DV360 scope. | Confirm the Authorization: Bearer header, token freshness, and that the token includes https://www.googleapis.com/auth/display-video for the method. |
| Permission denied for a partner or advertiser | The Google Account represented by the token is not a DV360 user or lacks access to that exact resource. | Check the account identity, partner-level or advertiser-level assignment, and the resource ID in the request. |
| User-resource call fails while ordinary calls work | The additional user-management scope is missing, or the identity is not an Admin DV360 user. | Add https://www.googleapis.com/auth/display-video-user-management and verify Admin access at the target partner. |
| Create or update fails for a Read only user | The DV360 role permits retrieval but not the attempted write. | Use a Standard role for ordinary creates and updates, or Admin where user resources are involved. |
| Delegated service-account call fails | Domain-wide delegation is incomplete or the impersonated user is outside the authorized domain. | Verify administrator scope authorization, same-domain user linkage, the selected subject user, and that user’s DV360 provisioning and role. |
A practical isolation sequence
- Log the HTTP status and method without logging the access token itself.
- Confirm the token was minted for the intended Cloud project and includes the required DV360 scope.
- Identify the Google Account, service account, or impersonated user represented by the credential.
- Check that identity in DV360 and verify access to the exact partner or advertiser in the request.
- Retry a read-only listing operation before testing a write.
- If the failing method belongs to the
usersservice, verify both the extra scope and Admin role.
Do not solve a resource-level permission error by blindly adding broader scopes. A broader token cannot grant a Google Account access that DV360 has not provisioned.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchHow should credentials and tokens be protected?
OAuth client secrets and service-account key files are credentials, not configuration samples. Google cautions that a service-account key file grants access to the Google services authorized for that account; with domain-wide delegation, the account can also carry domain-level impersonation power.
Best Value
- 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
- 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
- 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
- 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
- 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.
- Keep client-secret JSON and service-account keys out of source repositories, tickets, build logs, and shared documents.
- Use a protected secret store or operating-system credential store, with access limited to the process that needs it.
- Prefer narrowly scoped OAuth permissions and the smallest DV360 role that supports the job.
- Separate development and production Cloud projects and identities where your operating model permits.
- Do not print bearer tokens in exception messages or request traces.
- For delegated service accounts, document the administrator-approved scopes and the set of users that may be impersonated.
- Revoke or replace credentials when an operator, service, or integration no longer needs them.
Security controls do not replace DV360 provisioning: they reduce the impact if a credential is exposed, while the DV360 role and resource assignment still determine the actions it can perform.
Does the Display & Video 360 API provide performance reports?
No. The Display & Video 360 API is not the endpoint for retrieving performance data. Google’s API FAQ directs developers to the Bid Manager API for DV360 offline reports. Keep reporting credentials and workflows separate from the resource-management calls described here.
Which API version should a new integration target?
The cited Google FAQ identifies v4 as the latest Display & Video 360 API version addressed by that documentation. Use the v4 discovery URL when generating a client, but verify the current version and permission behavior in Google’s documentation before production deployment because API versions and authorization rules can change.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Frequently Asked Questions
Can a service account call DV360 without domain-wide delegation?
Yes. Associate the service account’s email address with a DV360 user and grant that user the required partner or advertiser access. Domain-wide delegation is needed only when the service account must impersonate Workspace users rather than operate as its own provisioned DV360 identity.
Should an application request both DV360 OAuth scopes at sign-in?
Request both only when the same application genuinely calls ordinary DV360 methods and the users service. Asking for the user-management scope in an application that never manages users expands consent and credential privileges without adding functionality.
Why does enabling the API in Google Cloud not fix a DV360 access error?
API enablement authorizes the Cloud project to request credentials; it does not assign a Google Account to a DV360 partner or advertiser. DV360 provisioning, resource assignment, scope, and role checks still have to pass for each request.
When is an interactive user flow the safer choice?
Use it when a person should explicitly approve access and each action should be attributable to that person’s DV360 account. It avoids storing a long-lived unattended identity, although the user must remain provisioned and authorized for the resources the tool uses.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.

