Permission for automated Overwatch Career Profile access

API Discussion
1

Hello,

I am developing an Overwatch LFG service called LOBIWA.

We are evaluating a self-hosted implementation based on OverFast to retrieve information available on users’ public Overwatch Career Profiles.

The information may include:

  • Competitive Role ranks (Tank, Damage, and Support)
  • Platform information
  • Public profile metadata
  • Career statistics
  • Play time
  • Games played and wins
  • Role-specific or hero-specific statistics
  • Other information publicly available through the Overwatch Career Profile

We would first identify which fields are technically available and would only use information that is actually necessary for LOBIWA’s player profile and LFG features.

We do not intend to automatically store or display every field that can technically be retrieved.

The implementation would use automated HTTP requests and parsing of publicly accessible Career Profile pages.

We would not:

  • Attempt to access or bypass private profiles
  • Bypass authentication, access controls, rate limits, or other technical restrictions
  • Provide Blizzard OAuth access tokens, client secrets, passwords, or other credentials to OverFast
  • Attempt to retrieve information that Blizzard has made private or unavailable

If implemented, we would also:

  • Self-host the profile retrieval service
  • Cache requests to minimize traffic to Blizzard services
  • Limit request frequency
  • Inform users about the information being retrieved and how it is used
  • Allow users to remove or unlink information associated with their LOBIWA profile

I understand that Blizzard’s terms may restrict scraping, crawling, or automated queries outside authorized API use.

Questions

  1. Is automated HTTP access and parsing of public Overwatch Career Profile pages permitted for this type of third-party community service?

  2. If it is not generally permitted, is there an official process for requesting prior written permission for this specific use?

  3. Are there restrictions on which public Career Profile information may be:

    • retrieved,
    • cached,
    • stored, or
    • displayed?

  4. Are there required:

    • rate limits,
    • caching or refresh intervals,
    • retention periods,
    • attribution requirements,
    • deletion requirements, or
    • other technical or privacy requirements?

  5. Does the permitted use differ depending on whether the service is non-commercial, commercial, ad-supported, or otherwise monetized?

  6. If this request should be directed to Blizzard Legal, Developer Relations, licensing, or another team, could you please provide the appropriate contact method?

We will not deploy this automated Career Profile retrieval functionality to production until its permitted use has been sufficiently clarified.

I would be happy to provide additional technical details about the proposed architecture, data fields, caching behavior, or retention policy if needed.

Thank you.