What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
Display & Video 360 (DV360) API authentication uses OAuth 2.0 exclusively. The complete access chain is: a Google Cloud OAuth client obtains an access token for the required scope, that token represents a Google Account provisioned as a DV360 user, and the user’s DV360 role determines which partner or advertiser resources the request can use. Ordinary read and write calls use https://www.googleapis.com/auth/display-video; methods in the users service also require https://www.googleapis.com/auth/display-video-user-management.
Enabling the API in Google Cloud is only the first step. Permission errors usually mean the token’s account is not a DV360 user for the target partner or advertiser, the scope is incomplete, or the DV360 role is too restrictive. Use an interactive OAuth flow for human-operated tools, and associate a service account with a DV360 user (or use domain-wide delegation) for scheduled and unattended workloads.
As an Amazon Associate I earn from qualifying purchases.
Outdated 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 matchWindows 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 reinstallKeep authentication and authorization separate in your design. OAuth proves the Google identity that requested the token; DV360 provisioning and role assignments decide what that identity can see or change. No API key, basic-auth credential or alternative authorization protocol substitutes for the required OAuth bearer token.
What does the DV360 API authenticate, and what controls access?
Authentication proves which Google identity is making the request. DV360 authorization then decides what that identity may do. Google states that every request must include an authorization token and that no other authorization protocols are supported.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
The identity chain has five links:
- Google Cloud project: the project owns the API configuration and OAuth credentials.
- OAuth scope: the token declares which DV360 API operations it can request.
- Bearer access token: the client sends this token in the HTTP
Authorizationheader. - DV360 user: the Google Account represented by the token must be provisioned as a Display & Video 360 user.
- Resource permission: that DV360 user must have access to the specific partner or advertiser addressed by the call.
A valid token therefore does not grant universal DV360 access. Cloud-project ownership, OAuth consent and DV360 partner permissions are separate controls. Someone who can edit a Cloud project is not automatically a DV360 user, and a DV360 user cannot call the API without a token carrying the appropriate scope.
For diagnosis, identify the account represented by the token before inspecting the request body. The same application can succeed for one signed-in account and fail for another because their DV360 user records, partner assignments or roles differ.
Which OAuth scopes does Display & Video 360 use?
Use https://www.googleapis.com/auth/display-video for ordinary DV360 API read and write operations. Add https://www.googleapis.com/auth/display-video-user-management whenever the application calls methods in the users service.
| Scope | Use it for | Important limitation |
|---|---|---|
https://www.googleapis.com/auth/display-video |
Retrieving, creating and updating ordinary DV360 resources, subject to the user’s role | It does not by itself authorize user-management methods |
https://www.googleapis.com/auth/display-video-user-management |
Methods that manage DV360 User resources | The represented DV360 user still needs an Admin role at the target partner |
Request only the scopes your application needs. A token carrying the ordinary scope can still receive a permission error if a method belongs to the user-management service. An integration that both manages campaigns or other ordinary resources and administers users should request both scope strings and still satisfy the separate DV360 role requirements.
Scopes are not roles. The scope expresses what the application is asking the API to permit; the DV360 role expresses what the represented account is allowed to do. Supplying a broader scope cannot elevate a Read only or Standard user.
How do I set up interactive OAuth for a desktop or web application?
Interactive OAuth is appropriate when a person signs in, grants consent and operates the integration. The resulting credential represents that person’s Google Account and its DV360 permissions.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minute- Select or create a Google Cloud project. Keep the project associated with the application that will make DV360 requests.
- Enable the Display & Video 360 API. In Google Cloud Console, open APIs & Services, choose Library, find the Display & Video 360 API, and select Enable.
- Configure the OAuth consent screen. Supply the application information requested by Google and declare the DV360 scopes the application will request.
- Create an OAuth client ID. Open APIs & Services → Credentials → Create credentials → OAuth client ID. Select the client type that matches your application, then download the client-secret JSON. Treat that file as sensitive and do not commit it to source control or share it.
- Implement the OAuth flow. Use an installed-application flow for a desktop tool or a web flow for a server-backed application. Request
https://www.googleapis.com/auth/display-video, and include the user-management scope only if the application will call theusersservice. - Have the operator sign in and consent. The first authorization sends the user to Google’s consent prompt. Store the resulting credential according to your application’s security policy; the credential is used to obtain access tokens for API calls.
- Build the authorized DV360 client. Configure the client library or HTTP layer with the OAuth credential and the DV360 API endpoint. The documented v4 discovery document is https://displayvideo.googleapis.com/$discovery/rest?version=v4.
- Test a read operation first. List a resource that the signed-in user can access. Only after that succeeds should you test create or update methods that the user’s role allows.
The signed-in account must already be a DV360 user with access to the partner or advertiser you intend to query. OAuth consent cannot substitute for DV360 provisioning. If the user can authorize the Cloud application but has no DV360 assignment, authentication may complete successfully while the first API call is denied.
During development, keep the test account, target partner and target advertiser explicit in configuration. That makes it easier to distinguish a bad resource identifier from a token belonging to the wrong Google Account.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
How do I send the access token with a DV360 request?
Every request carries the OAuth 2.0 bearer token in an HTTP header. The value must be the current access token minted for the DV360 scope.
Authorization: Bearer ACCESS_TOKENUse the API client library’s authenticated transport when possible, because it handles token acquisition and renewal. If you make raw HTTP requests, ensure the header is present on every call and that the URL and API version match the method you are invoking. A missing, malformed or incorrectly scoped token produces authentication failures before DV360 evaluates partner permissions.
Do not place access tokens in URLs, source repositories, issue reports or ordinary application logs. Log request metadata that helps diagnosis, such as the method and target resource, without recording the bearer value itself.
What DV360 roles are required for reading, writing and user management?
The DV360 role attached to the represented account determines the operations allowed after authentication. The role is assigned in DV360, not in the Google Cloud project.
| DV360 role | Resource access described by Google | Typical API effect |
|---|---|---|
| Read only | Retrieval of most resources, excluding User resources | Read calls can work; create and update calls are not permitted |
| Standard | Retrieval, creation and updating of most resources, plus retrieval of User resources | Suitable for ordinary resource management when user administration is not required |
| Admin | Retrieval, creation and updating of User resources | Required for user-management operations; available at partner level |
Role checks are resource-specific. An account may be valid for one partner or advertiser and still receive a permission error when the request targets another. Confirm both the role and the exact partner or advertiser assignment.
The role table also explains why a seemingly valid token can fail only on writes. Read only is retrieval-oriented, while Standard permits ordinary resource creation and updating. Admin is the role needed for creating or updating User resources, and Google makes it available at partner level.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →How do service accounts authenticate to DV360?
Service accounts are intended for back-end services, scheduled jobs and other unattended workloads. Google documents two patterns.
Directly associate a service account with a DV360 user
This is the preferred pattern for many automated integrations. Create a service account in Google Cloud, then associate its service-account email address with a DV360 user. The service account acts as that provisioned DV360 user, so its effective access comes from the DV360 role and partner or advertiser assignments attached to that user.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
- Create the service account in the Google Cloud project that will run the integration.
- Configure the application to request the DV360 OAuth scope using the service account credentials.
- Add the service-account email as a DV360 user and grant access to the required partner or advertiser.
- For user-management calls, also request
https://www.googleapis.com/auth/display-video-user-managementand grant the service-account DV360 user an Admin role for the target partner. - Run a least-privilege read test before enabling scheduled writes.
Association is not merely an address-book step: it establishes the DV360 identity used for authorization. If the service-account email has not been added as a DV360 user, a correctly formed Google token still lacks the required DV360 identity and resource permissions.
Use domain-wide delegation to impersonate a Workspace user
Domain-wide delegation allows a service account to impersonate one or more DV360 users in a Google Workspace domain. It is appropriate when an organization centrally administers identities and needs automation to act as existing domain users, but it adds domain-level administration and policy requirements.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →- A Workspace administrator must authorize the delegated OAuth scopes for the service account.
- The users being impersonated must be linked to accounts in that same domain.
- The application must specify an impersonated user from that domain.
- The impersonated identity still needs the required DV360 user provisioning, partner or advertiser access and role.
Domain-wide delegation does not bypass DV360 permissions. It changes which Workspace identity the service account presents; DV360 still evaluates that identity’s role. It is therefore not required for every scheduled job: direct service-account association is sufficient when one dedicated DV360 identity is appropriate.
How do I manage DV360 users through the API?
User resources have an extra security boundary. A call to the users service must include both the ordinary DV360 scope and https://www.googleapis.com/auth/display-video-user-management, and the token must represent a DV360 user with an Admin role for the target partner.
- Provision the calling Google Account or service account as a DV360 user.
- Grant that user Admin access at the partner level where user administration is required.
- Request the user-management scope during OAuth authorization or service-account token creation.
- Send the resulting bearer token with the user-management request.
- If the call fails, verify the scope and Admin role before changing application code.
A Standard user can retrieve User resources according to the documented role model but cannot create or update them. A Read only user cannot use User resources for retrieval. Thus, listing users and changing users are different authorization cases even though both use the users service.
Which authentication pattern should I choose?
Choose based on who must authorize the work and whether a human is present when requests run.
| Decision point | Interactive OAuth user flow | Service account or delegation |
|---|---|---|
| Human consent | A user signs in and grants consent; consent is part of setup. | A directly associated service account runs without interactive consent; delegation requires domain administration. |
| 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 tools, web applications and operator-run workflows. | Scheduled jobs, back-end services and automation. |
| Access controls | OAuth scopes combined with the person’s DV360 role and resource assignments. | Scopes combined with service-account provisioning, DV360 role and, for delegation, domain policy. |
| User management | Requires the additional user-management scope and Admin access. | Requires the additional scope and an Admin DV360 user; delegation does not remove that requirement. |
Interactive flow is usually easier to introduce because the operator supplies consent and can immediately verify the account being used. Service accounts provide a stable identity for automation, but they require deliberate DV360 provisioning and stronger key or delegation controls. Choose the narrowest identity and role that can complete the job rather than granting Admin by default.
Why does my DV360 API request return 401 or permission denied?
Diagnose the failure in order: token validity, scope, DV360 user provisioning, resource assignment and role.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
| Symptom | Likely cause | What to check |
|---|---|---|
401, missing-token or unauthenticated response |
No valid OAuth 2.0 bearer token reached the API, or the token is not minted for DV360. | Inspect the outgoing request for Authorization: Bearer ...; obtain a fresh token with https://www.googleapis.com/auth/display-video. |
| Permission denied for a partner or advertiser | The Google Account in the token is not a DV360 user for that exact resource. | Check the account identity, then verify its partner or advertiser assignment in DV360. |
| User-resource method fails while ordinary calls work | The user-management scope is missing, or the DV360 user lacks Admin access. | Add https://www.googleapis.com/auth/display-video-user-management and verify an Admin role at the target partner. |
| Create or update fails for a Read only user | The role permits retrieval but not writes. | Use a Standard role for ordinary resource writes or Admin where user-resource changes are required. |
| Service-account calls are denied | The service-account email is not provisioned as a DV360 user, or delegation is incomplete. | Confirm direct DV360 association or, for delegation, Workspace administrator authorization, domain alignment and the impersonated user. |
| Configuration calls succeed but reporting calls fail | Performance reporting is not served by this API. | Use the Bid Manager API for DV360 offline reports rather than changing DV360 scopes or roles. |
Change one control at a time while troubleshooting. First prove that a simple read works for the intended identity, then add the user-management scope or write operation. This isolates token problems from DV360 role and resource-assignment problems. If a test works for one partner but not another, retain the same token and compare the DV360 resource assignment instead of rebuilding OAuth credentials.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Is the DV360 API used for performance reporting?
No. The DV360 API manages configuration and resources; the DV360 API FAQ states that performance data is not retrieved through this API. Use the Bid Manager API for DV360 offline reports instead, and keep its authentication and reporting workflow separate from DV360 resource-management calls.
A successful configuration request therefore does not prove that a reporting endpoint, report type or reporting identity is available. Treat reporting as a separate integration with its own API documentation and authorization requirements.
Which API version should a new integration use?
The official FAQ identifies v4 as the latest version addressed by that documentation. API versions and permission behavior can change, so verify the current version and discovery document when you build or upgrade an integration. The v4 discovery URL is https://displayvideo.googleapis.com/$discovery/rest?version=v4.
Pin the discovery document or client-library version used by a deployment, and review the current Google documentation when upgrading. Version selection does not change the fundamental authorization chain: every call still needs an OAuth token, the correct scope and a DV360 user with access to the addressed resource.
How should credentials and keys be protected?
OAuth client-secret files and service-account key files are credentials, not configuration samples. Store them in a secret manager or equivalent protected location, restrict filesystem and build-system access, and keep them out of source repositories and logs. A service-account key grants access to the Google services authorized for that account; with domain-wide delegation, compromise can also enable impersonation within the delegated domain. Narrow scopes, narrow DV360 roles and narrowly assigned partner or advertiser access reduce the impact of a leaked credential.
Free tools Windows power users keep installed
One-click scans. No signup required.
Apply the same discipline to downloaded client-secret JSON and stored user credentials. Separate development and production projects where practical, restrict who can create or download keys, and remove unused credentials. Never solve a permission error by copying a privileged key into a wider environment; first verify the token scope, DV360 user record and resource assignment.
Implementation checklist
- Choose the Cloud project and enable the Display & Video 360 API.
- Choose the identity pattern: interactive Google Account, directly associated service account or delegated Workspace user.
- Configure the OAuth consent screen and request
display-video; adddisplay-video-user-managementonly forusersmethods. - Create and protect the OAuth client or service-account credentials.
- Provision the represented identity as a DV360 user.
- Assign the exact partner or advertiser and the least-privilege role required.
- For delegation, obtain Workspace administrator approval, use a same-domain user and specify that impersonated identity.
- Send
Authorization: Beareron every request. - Test an accessible read before testing writes or user administration.
- Use the Bid Manager API, not the DV360 API, for offline performance reports.
Frequently Asked Questions
Does enabling the Display & Video 360 API grant access to a partner?
No. Enabling the API only permits the Cloud project to call the service. The Google Account represented by each token must still be added as a DV360 user and assigned to the relevant partner or advertiser.
Is domain-wide delegation required for every scheduled DV360 job?
No. A service account can be associated directly with a DV360 user and run without impersonation. Delegation is an additional option when an organization needs a service account to act as existing Workspace users under centrally managed domain policy.
Can a Standard DV360 user change other DV360 users?
No. Standard access allows retrieval of User resources but not their creation or updates. User administration requires the user-management scope and an Admin role at the partner level.
Recommended Free Tools
Why can a token work for configuration calls but not for reports?
Configuration and resource management use the Display & Video 360 API. Offline performance reporting is provided through the separate Bid Manager API, so a successful DV360 token does not make reporting methods available.
Can I authenticate with an API key instead of OAuth 2.0?
No. Google states that every DV360 API request must include an authorization token and that no other authorization protocols are supported.
Why does a service-account token still receive permission denied?
A service account must be associated with a DV360 user, assigned to the target partner or advertiser and given a sufficient role. With domain-wide delegation, the Workspace administrator must also authorize the delegated scopes and the impersonated user must belong to the same domain.
Which scope is needed for ordinary DV360 resource updates?
Use https://www.googleapis.com/auth/display-video. Add https://www.googleapis.com/auth/display-video-user-management only when calling methods in the users service.
What should I test first after setting up OAuth?
List a resource that the represented DV360 user can access. Once that read succeeds, test a write or user-management method only if the role and additional scope permit it.
The Bottom Line
DV360 access is a chain, not a single setting: OAuth 2.0 token, correct scope, provisioned DV360 user, resource assignment and sufficient role. Use interactive OAuth for human-operated tools, a directly associated service account or domain-wide delegation for automation, and the separate Bid Manager API for performance reports.
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.
