url stringlengths 11 2.25k | text stringlengths 88 50k | ts timestamp[s]date 2026-01-13 08:47:33 2026-01-13 09:30:40 |
|---|---|---|
https://developers.google.com/admob/api/v1/getting-started?hl=ko | AdMob API 시작하기 | Google for Developers 기본 콘텐츠로 건너뛰기 AdMob API / English Deutsch Español Español – América Latina Français Indonesia Italiano Polski Português – Brasil Tiếng Việt Türkçe Русский עברית العربيّة فارسی हिंदी বাংলা ภาษาไทย 中文 – 简体 中文 – 繁體 日本語 한국어 로그인 AdMob 가이드 참조 라이브러리 및 예제 지원 AdMob API AdMob 가이드 참조 라이브러리 및 예제 지원 시작하기 기본사항 기본 요건 일반적인 오류 승인 개요 설정 타사 통합 놀이터 보고서 보고서 설정 측정항목 및 측정기준 목록 보고서 생성하기 인벤토리 앱 및 광고 단위 미디에이션 미디에이션 관리 광고 소스 Adapters 광고 단위 매핑 미디에이션 그룹 미디에이션 A/B 실험 홈 제품 AdMob API 가이드 AdMob API 시작하기 컬렉션을 사용해 정리하기 내 환경설정을 기준으로 콘텐츠를 저장하고 분류하세요. 중요: 새 사용자 역할 및 권한은 AdMob API에서 반환되는 데이터에 영향을 미칩니다. 자세히 알아보기 이 가이드는 AdMob API를 사용하여 AdMob 계정의 데이터를 프로그래매틱 방식으로 하려는 개발자를 위한 것입니다. 모든 Google AdMob API 호출은 OAuth2 를 통해 승인되어야 앱이 사용자를 대신하여 웹 서비스와 상호작용할 수 있습니다. OAuth2를 사용하면 AdMob API 클라이언트 앱이 사용자의 사용자 이름이나 비밀번호를 처리하거나 저장하지 않고도 사용자의 AdMob 계정에 액세스할 수 있습니다. 승인 개요는 승인 을 참고하세요. 다음 단계에 따라 OAuth2 사용자 인증 정보를 생성하고 첫 번째 요청을 합니다. 기본 요건 Google 계정 Google AdMob 계정 REST 기본사항 및 OAuth 2.0으로 요청 승인 에 대한 지식 인증 유형 확인 아래 표를 참고하여 앱에 가장 적합한 인증 유형 을 확인하세요. OAuth2 인증 유형 선택 판단 기준 데스크톱 앱 단일 최상위 관리자 계정을 사용하여 모든 AdMob API 계정을 관리합니다. 처음 사용하는 사용자이거나 가장 간단한 설정으로 빠르게 시작하고 싶습니다. 앱이 한 대의 컴퓨터에서만 Google AdMob 사용자를 인증합니다. 웹 앱 앱이 AdMob API 계정 데이터에 액세스할 수 있는 권한을 부여할 수 있는 사용자로 인증하려고 합니다. 예를 들어 서드 파티 계정을 관리하기 위해 여러 승인 사용자 인증 정보를 쉽게 생성하고 싶습니다. 앱에 콜백 URL이 필요합니다. 콜백 URL은 데스크톱 앱 흐름에서 지원되지 않습니다. 핵심 사항: 서버에서 실행되는 앱을 개발하는 경우에도 데스크톱 앱 흐름을 선택할 수 있습니다. 차이점은 OAuth 승인이 로컬에서 완료되는지 아니면 원격으로 완료되는지입니다. 데스크톱 흐름은 로컬 머신에서 승인을 완료해야 하는 반면 웹 흐름은 Google의 승인 서버에서 승인을 완료할 수 있습니다. 프로젝트 만들기 AdMob API를 사용하려면 먼저 Google API 콘솔에서 프로젝트를 만들거나 선택하고 설정 도구 를 사용하여 API를 사용 설정해야 합니다. 설정 도구는 절차를 안내하고 AdMob API를 자동으로 활성화합니다. 기존 프로젝트에 API 사용 설정 다음 단계는 기존 프로젝트가 있고 AdMob API를 수동으로 활성화하려는 사용자에게 적용됩니다. 프로젝트에서 API를 사용 설정하려면 다음 단계를 따르세요. Google API Console의 Open the API Library If prompted, select a project, or create a new one. API Library 에는 사용 가능한 모든 API가 제품군 및 인기도별로 분류되어 있습니다. 사용 설정하려는 API가 목록에 없는 경우 검색을 사용하여 찾거나 속한 제품군에서 모두 보기 를 클릭합니다. 사용 설정하려는 API를 선택한 다음 사용 설정 버튼을 클릭합니다. If prompted, enable billing. If prompted, read and accept the API's Terms of Service. OAuth2 사용자 인증 정보 만들기 다음 안내에서는 설치된 앱 흐름 과 함께 사용할 OAuth 2.0 클라이언트 ID를 만드는 과정을 안내합니다. Go to the Clients page . 사용자 인증 정보 만들기 > OAuth 클라이언트 ID 를 클릭합니다. 이전에 이 프로젝트의 OAuth 동의 화면을 구성하지 않았다면 지금 구성하라는 메시지가 표시됩니다. 동의 화면 구성 을 클릭합니다. OAuth 2.0 클라이언트 ID를 사용하도록 동의 화면을 구성하는 방법에는 여러 가지가 있습니다. 사용자 유형을 외부 로, 게시 상태를 게시됨 으로 설정합니다. 또는 사용자 유형을 외부 로, 게시 상태를 테스트 로 설정한 다음 사용자 추가 를 선택하여 테스트 사용자 를 추가하여 OAuth 2.0 클라이언트 ID를 사용할 수 있는 액세스 권한을 부여합니다. OAuth 동의 화면 설정 에 관한 추가 정보를 참고하세요. 애플리케이션 유형으로 데스크톱 앱 또는 웹 애플리케이션 을 선택하고 이름을 지정한 다음 만들기 를 클릭합니다. 완료되면 OAuth 2.0 클라이언트 ID와 클라이언트 보안 비밀번호가 표시되며, 이를 JSON 형식으로 다운로드하여 나중에 사용할 수 있도록 저장할 수 있습니다. 요청하기 AdMob API는 HTTP 및 JSON을 기반으로 작성되었기 때문에 모든 표준 HTTP 클라이언트가 AdMob API에 요청을 보내고 응답을 파싱할 수 있습니다. 하지만 Google API 클라이언트 라이브러리 는 더 나은 언어 통합, 향상된 보안, 승인된 요청을 지원합니다. 클라이언트 라이브러리는 다양한 프로그래밍 언어로 제공되므로 HTTP 요청을 직접 설정하고 응답을 파싱하지 않아도 됩니다. 참고: OAuth 흐름을 처음 활성화하면 AdMob 게시자 ID를 제공하고 브라우저에서 승인 메시지를 수락하라는 메시지가 표시됩니다. 수락하기 전에 AdMob 계정에 액세스할 수 있는 Google 계정으로 로그인되어 있는지 확인하세요. 그러면 앱이 현재 로그인된 계정을 대신하여 데이터에 액세스할 수 있습니다. OAuth 2.0 사용자 인증 정보가 생성 되면 AdMob API를 사용할 수 있습니다. OAuth 2.0을 사용하여 액세스를 요청하려면 앱에 범위 정보도 필요합니다. 범위 의미 https://www.googleapis.com/auth/admob.readonly 모든 AdMob 데이터를 확인합니다. 여기에는 계정 정보, 인벤토리 및 미디에이션 설정, 보고서 및 기타 데이터가 포함될 수 있습니다. 결제나 캠페인 세부정보와 같은 민감한 정보는 포함되지 않습니다. https://www.googleapis.com/auth/admob.report 광고 실적 및 수익 보고서를 확인합니다. 게시자 ID, 시간대, 기본 통화 코드를 확인합니다. Java , PHP , Python 또는 curl 의 예시를 사용하여 보고서를 생성하는 첫 번째 요청을 합니다. 공유 토큰 취소 공유 토큰은 다음 두 가지 방법으로 취소할 수 있습니다. Google 계정 권한 페이지 로 이동하여 관련 프로젝트의 액세스 권한을 취소합니다. 또는 Google Identity API 를 사용하여 웹 애플리케이션 토큰을 취소할 수 있습니다. 달리 명시되지 않는 한 이 페이지의 콘텐츠에는 Creative Commons Attribution 4.0 라이선스 에 따라 라이선스가 부여되며, 코드 샘플에는 Apache 2.0 라이선스 에 따라 라이선스가 부여됩니다. 자세한 내용은 Google Developers 사이트 정책 을 참조하세요. 자바는 Oracle 및/또는 Oracle 계열사의 등록 상표입니다. 최종 업데이트: 2025-08-31(UTC) [[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["필요한 정보가 없음","missingTheInformationINeed","thumb-down"],["너무 복잡함/단계 수가 너무 많음","tooComplicatedTooManySteps","thumb-down"],["오래됨","outOfDate","thumb-down"],["번역 문제","translationIssue","thumb-down"],["샘플/코드 문제","samplesCodeIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-08-31(UTC)"],[],["To use the AdMob API, developers must authorize requests via OAuth2. Key actions include creating a project in the Google API Console and enabling the AdMob API. Developers then generate OAuth2 credentials, choosing between desktop or web app authentication types. The OAuth consent screen must be configured. Finally, with created credentials and specifying the scope (`admob.readonly` or `admob.report`), developers can use HTTP or Google API client libraries to make their first API request and start retrieving AdMob data. Shared tokens can be revoked.\n"]] 제품 정보 사용량 한도 가격 책정 서비스 약관 프로그램 Google Developer Program Google Developer Groups Google Developer Experts Accelerators Google Cloud & NVIDIA 개발자 콘솔 Google API Console Google Cloud Platform Console Google Play Console Firebase Console Actions on Google Console Cast SDK Developer Console Chrome Web Store Dashboard Google Home Developer Console Android Chrome Firebase Google Cloud Platform Google AI 모든 제품 약관 개인정보처리방침 Manage cookies English Deutsch Español Español – América Latina Français Indonesia Italiano Polski Português – Brasil Tiếng Việt Türkçe Русский עברית العربيّة فارسی हिंदी বাংলা ภาษาไทย 中文 – 简体 中文 – 繁體 日本語 한국어 | 2026-01-13T09:30:11 |
https://developers.cloudflare.com/ai-gateway/observability/costs/ | Costs · Cloudflare AI Gateway docs Skip to content Cloudflare Docs Search Docs Directory APIs SDKs Help Log in Select theme Dark Light Auto AI Gateway No results found. Try a different search term, or use our global search . Overview Getting started Using AI Gateway Unified API (OpenAI compat) Provider Native Workers AI Amazon Bedrock Anthropic Azure OpenAI Baseten Cartesia Cerebras Cohere Deepgram DeepSeek ElevenLabs Fal AI Google AI Studio Google Vertex AI Groq HuggingFace Ideogram Mistral AI OpenAI OpenRouter Parallel Perplexity Replicate xAI WebSockets API Beta Overview Realtime WebSockets API Non-realtime WebSockets API Features Overview Unified Billing Caching Rate limiting Dynamic routing Beta Overview Using a dynamic route JSON Configuration Data Loss Prevention (DLP) Beta Overview Set up Data Loss Prevention (DLP) Guardrails Beta Overview Set up Guardrails Supported model types Usage considerations Configuration BYOK (Store Keys) Beta Custom costs Custom Providers Beta Manage gateways Request handling Authenticated Gateway Observability Costs Custom metadata Analytics Logging Overview Workers Logpush Integrations Vercel AI SDK Agents ↗ AI Gateway Binding Methods Workers AI Tutorials Platform Overview Limits Pricing Audit logs Changelog Header Glossary REST API reference ↗ API MCP server ↗ MCP AI Assistant ↗ Architectures LLM resources llms.txt prompt.txt AI Gateway llms-full.txt Developer Platform llms-full.txt GitHub X.com YouTube Select theme Dark Light Auto On this page Overview Track costs across AI providers Custom costs On this page Overview Track costs across AI providers Custom costs Was this helpful? Edit Issue Directory … AI Gateway Observability Costs Copy page Costs Cost metrics are only available for endpoints where the models return token data and the model name in their responses. Track costs across AI providers AI Gateway makes it easier to monitor and estimate token based costs across all your AI providers. This can help you: Understand and compare usage costs between providers. Monitor trends and estimate spend using consistent metrics. Apply custom pricing logic to match negotiated rates. Note The cost metric is an estimation based on the number of tokens sent and received in requests. While this metric can help you monitor and predict cost trends, refer to your provider's dashboard for the most accurate cost details. Caution Providers may introduce new models or change their pricing. If you notice outdated cost data or are using a model not yet supported by our cost tracking, please submit a request ↗ Custom costs AI Gateway allows users to set custom costs when operating under special pricing agreements or negotiated rates. Custom costs can be applied at the request level, and when applied, they will override the default or public model costs. For more information on configuration of custom costs, please visit the Custom Costs configuration page. Was this helpful? Edit page Last updated: May 15, 2025 Previous Authenticated Gateway Next Custom metadata Resources API New to Cloudflare? Directory Sponsorships Open Source Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Speed Test Is BGP Safe Yet? RPKI Toolkit Certificate Transparency Community X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings | 2026-01-13T09:30:11 |
https://developer.android.com/samples?hl=tr | Örnekler {9/}| ↗ Android Geliştiricileri | Samples | Android Developers Ana içeriğe atla Kaçırmamanız gereken oyunlar Yapay zeka deneyimleri oluşturma Gemini API'leri ve daha fazlasıyla yapay zeka destekli Android uygulamaları geliştirin. Başlama Başlama İlk uygulamanızı oluşturarak başlayın. Eğitim kurslarımızla daha ayrıntılı bilgi edinin veya uygulama geliştirmeyi kendi kendinize öğrenin. Hello world Eğitim kursları Eğitimler Ekipler için Compose Android için Kotlin Google Play ile para kazanma ↗️ Android Geliştirici Doğrulaması Cihaza göre genişletme Kullanıcılarınıza telefondan tablete, kol saatinden kulaklığa kadar her cihazda sorunsuz deneyimler sunan uygulamalar geliştirin. Uyarlanabilir uygulamalar Android XR Wear OS Arabalar için Android Android TV ChromeOS Kategoriye göre oluşturma Google'ın yönlendirici ve kişisel görüşe dayalı rehberliğini takip ederek kullanım alanınıza uygun çözümler geliştirmeyi öğrenin. Oyunlar Kamera ve medya Sosyal ve mesajlaşma Sağlık ve form koruma Verimlilik Kurumsal uygulamalar En son sürümünü edinin Yıl boyunca yeni çıkanları takip edin, önizleme programlarımıza katılın ve geri bildirimlerinizi bizimle paylaşın. Son güncellemeler Deneysel güncellemeler Android Studio önizlemesi Jetpack ve Compose kitaplıkları Wear OS sürümleri Özel Korumalı Alan ↗️ Tasarım ve Planlama Mükemmel deneyimler En iyi kullanıcılarınız için en iyi deneyimleri oluşturun. Daha fazla bilgi Kullanıcı arayüzü tasarımı Android'deki en iyi uygulamaları kullanarak güzel bir kullanıcı arayüzü tasarlayın. Android için tasarım Cep Uyarlanabilir kullanıcı arayüzü XR Kulaklıklar ve XR Gözlükler Yapay Zeka Gözlükleri Widget'lar Wear OS Android TV Arabalar için Android Mimari Güçlü, test edilebilir ve bakımı yapılabilir uygulama mantığı ve hizmetleri tasarlayın. Giriş Kütüphaneler Gezinme Modülerleştirme Test Kotlin Multiplatform Kalite Uygulama kalitesini planlayın ve Play Store yönergelerine uyun. Genel bakış Temel değer Kullanıcı deneyimi Erişilebilirlik Teknik kalite Mükemmel deneyimler Güvenlik Kullanıcıları tehditlere karşı koruyun ve güvenli bir Android deneyimi sağlayın. Genel bakış Gizlilik İzinler Kimlik Sahtekarlığı önleme Geliştirme Android Studio'da Gemini Android geliştirmede yapay zeka geliştirme arkadaşınız. Daha fazla bilgi Android Studio'yu edinme Temel alanlar İhtiyacınız olan özelliklerle ilgili örnekleri ve dokümanları edinin. Örnekler Kullanıcı arayüzleri Arka plan çalışması Veriler ve dosyalar Bağlanabilirlik Tüm temel alanlar ⤵️ Araçlar ve iş akışı Uygulamanızı yazmak ve oluşturmak için IDE'yi kullanın veya kendi işlem hattınızı oluşturun. Kod yazma ve hata ayıklama Proje oluşturma Uygulamanızı test etme Performans Komut satırı araçları Gradle eklentisi API'si Cihaz teknolojisi Form faktörleri için kod yazma Cihazları bağlayın ve verileri paylaşın. Uyarlanabilir kullanıcı arayüzü Wear OS Android XR Android Health Arabalar için Android Android TV Tüm cihazlar ⤵️ Kütüphaneler Tüm ayrıntıları içeren API referans belgelerine göz atın. Android platformu Jetpack kitaplıkları Compose kitaplıkları Google Play Hizmetleri ↗️ Google Play SDK Dizini ↗️ Google Play Play Console Uygulamanızı veya oyununuzu yayınlayın ve Google Play'de işinizi büyütün. Play Console'a git Daha fazla bilgi ↗️ Temel Bilgiler Kullanıcılarla etkileşim kurmayı, uygulamanızdan para kazanmayı ve uygulamanızı güvenli hale getirmeyi öğrenin. Play'de para kazanma Play Integrity Play Politikaları Play Programları ↗️ Games Dev Center Oyun geliştirme ve yayınlama Araçlar, indirilenler ve örnekler Genel bakış Play Asset Delivery Play Games Hizmetleri PC Üzerinde Play Games Tüm Play rehberleri ⤵️ Kütüphaneler Tüm ayrıntıları içeren API referans belgelerine göz atın. Play Özellik Dağıtımı Play uygulama içi güncellemeleri Play uygulama içi yorumları Play Install Referrer Google Play Hizmetleri ↗️ Google Play SDK Dizini ↗️ Tüm Play kitaplıkları ⤵️ Araçlar ve kaynaklar Uygulamanızı yayınlama, tanıtma ve yönetme araçları. Android App Bundle Marka ve pazarlama Play Console API'leri ↗️ Topluluk / English Deutsch Español – América Latina Français Indonesia Italiano Polski Português – Brasil Tiếng Việt Türkçe Русский עברית العربيّة فارسی हिंदी বাংলা ภาษาไทย 中文 – 简体 中文 – 繁體 日本語 한국어 Android Studio Oturum aç Kaçırmamanız gereken oyunlar Diğer Tasarım ve Planlama Diğer Geliştirme Diğer Google Play Diğer Topluluk Android Studio Yapay zeka deneyimleri oluşturma Başlama Başlama Hello world Eğitim kursları Eğitimler Ekipler için Compose Android için Kotlin Google Play ile para kazanma ↗️ Android Geliştirici Doğrulaması Cihaza göre genişletme Uyarlanabilir uygulamalar Android XR Wear OS Arabalar için Android Android TV ChromeOS Kategoriye göre oluşturma Oyunlar Kamera ve medya Sosyal ve mesajlaşma Sağlık ve form koruma Verimlilik Kurumsal uygulamalar En son sürümünü edinin Son güncellemeler Deneysel güncellemeler Android Studio önizlemesi Jetpack ve Compose kitaplıkları Wear OS sürümleri Özel Korumalı Alan ↗️ Mükemmel deneyimler Daha fazla bilgi Kullanıcı arayüzü tasarımı Android için tasarım Cep Uyarlanabilir kullanıcı arayüzü XR Kulaklıklar ve XR Gözlükler Yapay Zeka Gözlükleri Widget'lar Wear OS Android TV Arabalar için Android Mimari Giriş Kütüphaneler Gezinme Modülerleştirme Test Kotlin Multiplatform Kalite Genel bakış Temel değer Kullanıcı deneyimi Erişilebilirlik Teknik kalite Mükemmel deneyimler Güvenlik Genel bakış Gizlilik İzinler Kimlik Sahtekarlığı önleme Android Studio'da Gemini Daha fazla bilgi Android Studio'yu edinme Temel alanlar Örnekler Kullanıcı arayüzleri Arka plan çalışması Veriler ve dosyalar Bağlanabilirlik Tüm temel alanlar ⤵️ Araçlar ve iş akışı Kod yazma ve hata ayıklama Proje oluşturma Uygulamanızı test etme Performans Komut satırı araçları Gradle eklentisi API'si Cihaz teknolojisi Uyarlanabilir kullanıcı arayüzü Wear OS Android XR Android Health Arabalar için Android Android TV Tüm cihazlar ⤵️ Kütüphaneler Android platformu Jetpack kitaplıkları Compose kitaplıkları Google Play Hizmetleri ↗️ Google Play SDK Dizini ↗️ Play Console Play Console'a git Daha fazla bilgi ↗️ Temel Bilgiler Play'de para kazanma Play Integrity Play Politikaları Play Programları ↗️ Games Dev Center Genel bakış Play Asset Delivery Play Games Hizmetleri PC Üzerinde Play Games Tüm Play rehberleri ⤵️ Kütüphaneler Play Özellik Dağıtımı Play uygulama içi güncellemeleri Play uygulama içi yorumları Play Install Referrer Google Play Hizmetleri ↗️ Google Play SDK Dizini ↗️ Tüm Play kitaplıkları ⤵️ Araçlar ve kaynaklar Android App Bundle Marka ve pazarlama Play Console API'leri ↗️ Android Developers Geliştirme Samples Koleksiyonlar ile düzeninizi koruyun İçeriği tercihlerinize göre kaydedin ve kategorilere ayırın. Örnekler Uygulama geliştirme sürecini hızlandırmak için kullanabileceğiniz kod örnekleri ve şablonlar. Uygulamalarınız için farklı bileşenleri nasıl oluşturacağınızı öğrenmek üzere örneklere göz atın. Kotlin Java C++ Mimari Köprü Kamera ve Medya Bağlantı Grafik Sensörler Gizlilik ve Güvenlik Depolama Kullanıcı arayüzü (Oluştur) Kullanıcı arayüzü (Görünümler) Giyilebilir Cihazlar Öne çıkanlar Now in Android Artık Android'de Kotlin ve Jetpack Compose ile geliştirilmiş tüm işlevleri var. Android tasarım ve geliştirme ile ilgili en iyi uygulamaların modelini çıkarır ve geliştiriciler için yararlı bir başvuru kaynağı olarak tasarlanmıştır. GitHub'da görüntüle [[["Anlaması kolay","easyToUnderstand","thumb-up"],["Sorunumu çözdü","solvedMyProblem","thumb-up"],["Diğer","otherUp","thumb-up"]],[["İhtiyacım olan bilgiler yok","missingTheInformationINeed","thumb-down"],["Çok karmaşık / çok fazla adım var","tooComplicatedTooManySteps","thumb-down"],["Güncel değil","outOfDate","thumb-down"],["Çeviri sorunu","translationIssue","thumb-down"],["Örnek veya kod sorunu","samplesCodeIssue","thumb-down"],["Diğer","otherDown","thumb-down"]],[],[],[]] X X'te @AndroidDev'i takip edin YouTube YouTube'da Android Developers'a göz atın LinkedIn Connect with the Android Developers community on LinkedIn Android hakkında daha fazla Android İşletmeler için Android Güvenlik Kaynak Haber Blog Podcast'ler Keşfet Oyun Makine Öğrenimi Sağlık ve Fitness Kamera ve Medya Gizlilik 5G Android Cihazlar Büyük ekranlar Wear OS ChromeOS cihazlar Arabalar için Android Android TV Sürümler Android 15 Android 14 Android 13 Android 12 Android 11 Android 10 Pie Belgeler ve İndirmeler Android Studio kılavuzu Geliştirici kılavuzları API referansı Studio'yu indir Android NDK Destek Platform hatası bildir Belge hatası bildir Google Play support Araştırma çalışmalarına katıl Android Chrome Firebase Google Cloud Platform Tüm ürünler Gizlilik Lisans Marka kuralları Manage cookies E-postayla haberler ve ipuçları al Abone ol English Deutsch Español – América Latina Français Indonesia Italiano Polski Português – Brasil Tiếng Việt Türkçe Русский עברית العربيّة فارسی हिंदी বাংলা ภาษาไทย 中文 – 简体 中文 – 繁體 日本語 한국어 | 2026-01-13T09:30:11 |
https://developers.cloudflare.com/ai-gateway/usage/providers/google-ai-studio/ | Google AI Studio · Cloudflare AI Gateway docs Skip to content Cloudflare Docs Search Docs Directory APIs SDKs Help Log in Select theme Dark Light Auto AI Gateway No results found. Try a different search term, or use our global search . Overview Getting started Using AI Gateway Unified API (OpenAI compat) Provider Native Workers AI Amazon Bedrock Anthropic Azure OpenAI Baseten Cartesia Cerebras Cohere Deepgram DeepSeek ElevenLabs Fal AI Google AI Studio Google Vertex AI Groq HuggingFace Ideogram Mistral AI OpenAI OpenRouter Parallel Perplexity Replicate xAI WebSockets API Beta Overview Realtime WebSockets API Non-realtime WebSockets API Features Overview Unified Billing Caching Rate limiting Dynamic routing Beta Overview Using a dynamic route JSON Configuration Data Loss Prevention (DLP) Beta Overview Set up Data Loss Prevention (DLP) Guardrails Beta Overview Set up Guardrails Supported model types Usage considerations Configuration BYOK (Store Keys) Beta Custom costs Custom Providers Beta Manage gateways Request handling Authenticated Gateway Observability Costs Custom metadata Analytics Logging Overview Workers Logpush Integrations Vercel AI SDK Agents ↗ AI Gateway Binding Methods Workers AI Tutorials Platform Overview Limits Pricing Audit logs Changelog Header Glossary REST API reference ↗ API MCP server ↗ MCP AI Assistant ↗ Architectures LLM resources llms.txt prompt.txt AI Gateway llms-full.txt Developer Platform llms-full.txt GitHub X.com YouTube Select theme Dark Light Auto On this page Overview Endpoint Examples cURL @google/genai OpenAI-Compatible Endpoint On this page Overview Endpoint Examples cURL @google/genai OpenAI-Compatible Endpoint Was this helpful? Edit Issue Directory … AI Gateway Using AI Gateway Provider Native Google AI Studio Copy page Google AI Studio Google AI Studio ↗ helps you build quickly with Google Gemini models. Endpoint Base URL: https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/google-ai-studio Then you can append the endpoint you want to hit, for example: v1/models/{model}:{generative_ai_rest_resource} So your final URL will come together as: https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/google-ai-studio/v1/models/{model}:{generative_ai_rest_resource} . Examples cURL With API Key in Request With Authenticated Gateway Unauthenticated Gateway Terminal window curl "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_name}/google-ai-studio/v1/models/gemini-2.5-flash:generateContent" \ --header 'content-type: application/json' \ --header 'cf-aig-authorization: Bearer {CF_AIG_TOKEN}' \ --header 'x-goog-api-key: {google_studio_api_key}' \ --data '{ "contents": [ { "role":"user", "parts": [ {"text":"What is Cloudflare?"} ] } ] }' Terminal window curl "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_name}/google-ai-studio/v1/models/gemini-2.5-flash:generateContent" \ --header 'content-type: application/json' \ --header 'x-goog-api-key: {google_studio_api_key}' \ --data '{ "contents": [ { "role":"user", "parts": [ {"text":"What is Cloudflare?"} ] } ] }' With Stored Keys (BYOK) / Unified Billing Terminal window curl "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_name}/google-ai-studio/v1/models/gemini-2.5-flash:generateContent" \ --header 'content-type: application/json' \ --header 'cf-aig-authorization: Bearer {CF_AIG_TOKEN}' \ --data '{ "contents": [ { "role":"user", "parts": [ {"text":"What is Cloudflare?"} ] } ] }' @google/genai If you are using the @google/genai package, you can set your endpoint like this: With Key in Request With Authenticated Gateway Unauthenticated Gateway import { GoogleGenAI } from "@google/genai" ; const ai = new GoogleGenAI ( { apiKey : "{google_studio_api_key}" , httpOptions : { baseUrl : `https://gateway.ai.cloudflare.com/v1/ ${ account_id } / ${ gateway_name } /google-ai-studio` , headers : { 'cf-aig-authorization' : 'Bearer {cf_aig_token}' , } } } ) ; const response = await ai . models . generateContent ( { model : "gemini-2.5-flash" , contents : "What is Cloudflare?" , } ) ; console . log ( response . text ) ; import { GoogleGenAI } from "@google/genai" ; const ai = new GoogleGenAI ( { apiKey : "{google_studio_api_key}" , httpOptions : { baseUrl : `https://gateway.ai.cloudflare.com/v1/ ${ account_id } / ${ gateway_name } /google-ai-studio` , } } ) ; const response = await ai . models . generateContent ( { model : "gemini-2.5-flash" , contents : "What is Cloudflare?" , } ) ; console . log ( response . text ) ; With Stored Keys (BYOK) / Unified Billing import { GoogleGenAI } from "@google/genai" ; const ai = new GoogleGenAI ( { apiKey : "{cf_aig_token}" , httpOptions : { baseUrl : `https://gateway.ai.cloudflare.com/v1/ ${ account_id } / ${ gateway_name } /google-ai-studio` , } } ) ; const response = await ai . models . generateContent ( { model : "gemini-2.5-flash" , contents : "What is Cloudflare?" , } ) ; console . log ( response . text ) ; OpenAI-Compatible Endpoint You can also use the OpenAI-compatible endpoint ( /ai-gateway/usage/chat-completion/ ) to access Google AI Studio models using the OpenAI API schema. To do so, send your requests to: https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions Specify: { " model " : "google-ai-studio/{model}" } Was this helpful? Edit page Last updated: Nov 25, 2025 Previous Fal AI Next Google Vertex AI Resources API New to Cloudflare? Directory Sponsorships Open Source Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Speed Test Is BGP Safe Yet? RPKI Toolkit Certificate Transparency Community X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings | 2026-01-13T09:30:11 |
https://vi-vn.facebook.com/login/?next=https%3A%2F%2Fwww.facebook.com%2Fshare_channel%2F%3Ftype%3Dreshare%26link%3Dhttp%253A%252F%252Fads-developers.googleblog.com%252F2021%252F09%252Fadsense-management-api-v14-sunset.html%26app_id%3D966242223397117%26source_surface%3Dexternal_reshare%26display%26hashtag | Facebook Facebook Email hoặc điện thoại Mật khẩu Bạn quên tài khoản ư? Tạo tài khoản mới Bạn tạm thời bị chặn Bạn tạm thời bị chặn Có vẻ như bạn đang dùng nhầm tính năng này do sử dụng quá nhanh. Bạn tạm thời đã bị chặn sử dụng nó. Back Tiếng Việt 한국어 English (US) Bahasa Indonesia ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch Đăng ký Đăng nhập Messenger Facebook Lite Video Meta Pay Cửa hàng trên Meta Meta Quest Ray-Ban Meta Meta AI Nội dung khác do Meta AI tạo Instagram Threads Trung tâm thông tin bỏ phiếu Chính sách quyền riêng tư Trung tâm quyền riêng tư Giới thiệu Tạo quảng cáo Tạo Trang Nhà phát triển Tuyển dụng Cookie Lựa chọn quảng cáo Điều khoản Trợ giúp Tải thông tin liên hệ lên & đối tượng không phải người dùng Cài đặt Nhật ký hoạt động Meta © 2026 | 2026-01-13T09:30:11 |
https://developers.google.com/admob/api/reference/rest/v1/accounts.networkReport/generate | Method: accounts.networkReport.generate | AdMob API | Google for Developers Skip to main content AdMob API / English Deutsch Español Español – América Latina Français Indonesia Italiano Polski Português – Brasil Tiếng Việt Türkçe Русский עברית العربيّة فارسی हिंदी বাংলা ภาษาไทย 中文 – 简体 中文 – 繁體 日本語 한국어 Sign in AdMob Guides Reference Libraries & Examples Support AdMob API AdMob Guides Reference Libraries & Examples Support Release notes AdMob API v1 REST Resources accounts Overview get list accounts.adUnits Overview list accounts.apps Overview list accounts.mediationReport Overview generate accounts.networkReport Overview generate Types DateRange LocalizationSettings ReportFooter ReportHeader ReportRow SortOrder StringList v1beta REST Resources accounts Overview get list accounts.adSources Overview list accounts.adSources.adapters Overview list accounts.adUnitMappings Overview batchCreate accounts.adUnits Overview create list accounts.adUnits.adUnitMappings Overview create list accounts.apps Overview create list accounts.campaignReport Overview generate accounts.mediationGroups Overview create list patch accounts.mediationGroups.mediationAbExperiments Overview create stop accounts.mediationReport Overview generate accounts.networkReport Overview generate Types DateRange LocalizationSettings MediationGroupLine ReportFooter ReportHeader ReportRow SortOrder StringList API dictionary Ad sources Adapters Home Products AdMob API Reference Method: accounts.networkReport.generate Stay organized with collections Save and categorize content based on your preferences. Page Summary outlined_flag The AdMob Network report can be generated based on a provided report specification using a POST request. The report specification includes parameters such as date range, dimensions, metrics, filters, and sorting conditions. The report response is a server-side streaming RPC, returning a sequence of responses including a header, rows of data, and a footer. Dimensions are attributes used to break down data, while metrics are quantitative measurements of performance. Authorization for generating the report requires specific OAuth scopes. HTTP request Path parameters Request body JSON representation Response body JSON representation Authorization scopes NetworkReportSpec JSON representation Dimension Metric DimensionFilter JSON representation SortCondition JSON representation Examples Try it! Generates an AdMob Network report based on the provided report specification. Returns result of a server-side streaming RPC. The result is returned in a sequence of responses. HTTP request POST https://admob.googleapis.com/v1/{parent=accounts/*}/networkReport:generate The URL uses gRPC Transcoding syntax. Path parameters Parameters parent string Resource name of the account to generate the report for. Example: accounts/pub-9876543210987654 Request body The request body contains data with the following structure: JSON representation { "reportSpec" : { object ( NetworkReportSpec ) } } Fields reportSpec object ( NetworkReportSpec ) Network report specification. Response body The streaming response for the AdMob Network report where the first response contains the report header, then a stream of row responses, and finally a footer as the last response message. For example: [{ "header": { "dateRange": { "startDate": {"year": 2018, "month": 9, "day": 1}, "endDate": {"year": 2018, "month": 9, "day": 1} }, "localizationSettings": { "currencyCode": "USD", "languageCode": "en-US" } } }, { "row": { "dimensionValues": { "DATE": {"value": "20180918"}, "APP": { "value": "ca-app-pub-8123415297019784~1001342552", displayLabel: "My app name!" } }, "metricValues": { "ESTIMATED_EARNINGS": {"microsValue": 6500000} } } }, { "footer": {"matchingRowCount": 1} }] If successful, the response body contains data with the following structure: JSON representation { // Union field payload can be only one of the following: "header" : { object ( ReportHeader ) } , "row" : { object ( ReportRow ) } , "footer" : { object ( ReportFooter ) } // End of list of possible types for union field payload . } Fields Union field payload . Each stream response message contains one type of payload. payload can be only one of the following: header object ( ReportHeader ) Report generation settings that describes the report contents, such as the report date range and localization settings. row object ( ReportRow ) Actual report data. footer object ( ReportFooter ) Additional information about the generated report, such as warnings about the data. Authorization scopes Requires one of the following OAuth scopes: https://www.googleapis.com/auth/admob.readonly https://www.googleapis.com/auth/admob.report For more information, see the OAuth 2.0 Overview . NetworkReportSpec The specification for generating an AdMob Network report. For example, the specification to get clicks and estimated earnings for only the 'US' and 'CN' countries can look like the following example: { 'dateRange': { 'startDate': {'year': 2021, 'month': 9, 'day': 1}, 'endDate': {'year': 2021, 'month': 9, 'day': 30} }, 'dimensions': ['DATE', 'APP', 'COUNTRY'], 'metrics': ['CLICKS', 'ESTIMATED_EARNINGS'], 'dimensionFilters': [ { 'dimension': 'COUNTRY', 'matchesAny': {'values': [{'value': 'US', 'value': 'CN'}]} } ], 'sortConditions': [ {'dimension':'APP', order: 'ASCENDING'}, {'metric':'CLICKS', order: 'DESCENDING'} ], 'localizationSettings': { 'currencyCode': 'USD', 'languageCode': 'en-US' } } For a better understanding, you can treat the preceding specification like the following pseudo SQL: SELECT DATE, APP, COUNTRY, CLICKS, ESTIMATED_EARNINGS FROM NETWORK_REPORT WHERE DATE >= '2021-09-01' AND DATE <= '2021-09-30' AND COUNTRY IN ('US', 'CN') GROUP BY DATE, APP, COUNTRY ORDER BY APP ASC, CLICKS DESC; JSON representation { "dateRange" : { object ( DateRange ) } , "dimensions" : [ enum ( Dimension ) ] , "metrics" : [ enum ( Metric ) ] , "dimensionFilters" : [ { object ( DimensionFilter ) } ] , "sortConditions" : [ { object ( SortCondition ) } ] , "localizationSettings" : { object ( LocalizationSettings ) } , "maxReportRows" : integer , "timeZone" : string } Fields dateRange object ( DateRange ) The date range for which the report is generated. dimensions[] enum ( Dimension ) List of dimensions of the report. The value combination of these dimensions determines the row of the report. If no dimensions are specified, the report returns a single row of requested metrics for the entire account. metrics[] enum ( Metric ) List of metrics of the report. A report must specify at least one metric. dimensionFilters[] object ( DimensionFilter ) Describes which report rows to match based on their dimension values. sortConditions[] object ( SortCondition ) Describes the sorting of report rows. The order of the condition in the list defines its precedence; the earlier the condition, the higher its precedence. If no sort conditions are specified, the row ordering is undefined. localizationSettings object ( LocalizationSettings ) Localization settings of the report. maxReportRows integer Maximum number of report data rows to return. If the value is not set, the API returns as many rows as possible, up to 100000. Acceptable values are 1-100000, inclusive. Values larger than 100000 return an error. timeZone string A report time zone. Accepts an IANA TZ name values, such as "America/Los_Angeles." If no time zone is defined, the account default takes effect. Check default value by the get account action. Warning: The "America/Los_Angeles" is the only supported value at the moment. Dimension The dimensions of the network report. Dimensions are data attributes to break down or refine the quantitative measurements (metrics) by certain attributes, such as the ad format or the platform an ad was viewed on. Enums DIMENSION_UNSPECIFIED Default value for an unset field. Do not use. DATE A date in the YYYYMMDD format (for example, "20210701"). Requests can specify at most one time dimension. MONTH A month in the YYYYMM format (for example, "202107"). Requests can specify at most one time dimension. WEEK The date of the first day of a week in the YYYYMMDD format (for example, "20210701"). Requests can specify at most one time dimension. AD_UNIT The unique ID of the ad unit (for example, "ca-app-pub-1234/1234"). If AD_UNIT dimension is specified, then APP is included automatically. APP The unique ID of the mobile application (for example, "ca-app-pub-1234~1234"). AD_TYPE Type of the ad (for example, "text" or "image"), an ad delivery dimension. Warning: The dimension is incompatible with AD_REQUESTS , MATCH_RATE and IMPRESSION_RPM metrics. COUNTRY CLDR country code of the place where the ad views/clicks occur (for example, "US" or "FR"). This is a geography dimension. FORMAT Format of the ad unit (for example, "banner", "native"), an ad delivery dimension. PLATFORM Mobile OS platform of the app (for example, "Android" or "iOS"). MOBILE_OS_VERSION Mobile operating system version, e.g. "iOS 13.5.1". GMA_SDK_VERSION GMA SDK version, e.g. "iOS 7.62.0". APP_VERSION_NAME For Android, the app version name can be found in versionName in PackageInfo. For iOS, the app version name can be found in CFBundleShortVersionString. SERVING_RESTRICTION Restriction mode for ads serving (e.g. "Non-personalized ads"). Metric The metrics of the network report. Metrics are quantitative measurements indicating how the publisher business is performing. They are aggregated from the individual ad events and grouped by the report dimensions. The metric value is either integer, or decimal (without rounding). Enums METRIC_UNSPECIFIED Default value for an unset field. Do not use. AD_REQUESTS The number of ad requests. The value is an integer. Warning: The metric is incompatible with AD_TYPE dimension. CLICKS The number of times a user clicks an ad. The value is an integer. ESTIMATED_EARNINGS The estimated earnings of the AdMob publisher. The currency unit (USD, EUR, or other) of the earning metrics are determined by the localization setting for currency. The amount is in micros. For example, $6.50 would be represented as 6500000. IMPRESSIONS The total number of ads shown to users. The value is an integer. IMPRESSION_CTR The ratio of clicks over impressions. The value is a double precision (approximate) decimal value. IMPRESSION_RPM The estimated earnings per thousand ad impressions. The value is in micros. For example, $1.03 would be represented as 1030000. Equivalent to eCPM in the AdMob UI. Warning: The metric is incompatible with AD_TYPE dimension. MATCHED_REQUESTS The number of times ads are returned in response to a request. The value is an integer. MATCH_RATE The ratio of matched ad requests over the total ad requests. The value is a double precision (approximate) decimal value. Warning: The metric is incompatible with AD_TYPE dimension. SHOW_RATE The ratio of ads that are displayed over ads that are returned, defined as impressions / matched requests. The value is a double precision (approximate) decimal value. DimensionFilter Describes which report rows to match based on their dimension values. JSON representation { "dimension" : enum ( Dimension ) , // Union field operator can be only one of the following: "matchesAny" : { object ( StringList ) } // End of list of possible types for union field operator . } Fields dimension enum ( Dimension ) Applies the filter criterion to the specified dimension. Union field operator . Filter operator to be applied. operator can be only one of the following: matchesAny object ( StringList ) Matches a row if its value for the specified dimension is in one of the values specified in this condition. SortCondition Sorting direction to be applied on a dimension or a metric. JSON representation { "order" : enum ( SortOrder ) , // Union field sort_on can be only one of the following: "dimension" : enum ( Dimension ) , "metric" : enum ( Metric ) // End of list of possible types for union field sort_on . } Fields order enum ( SortOrder ) Sorting order of the dimension or metric. Union field sort_on . Identifies which values to sort on. sort_on can be only one of the following: dimension enum ( Dimension ) Sort by the specified dimension. metric enum ( Metric ) Sort by the specified metric. Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License , and code samples are licensed under the Apache 2.0 License . For details, see the Google Developers Site Policies . Java is a registered trademark of Oracle and/or its affiliates. Last updated 2025-08-20 UTC. [[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-20 UTC."],[],["This document outlines the process of generating an AdMob Network report via an API. Key actions involve sending a `POST` request to a specific URL, including the account resource name in the path. The request body requires a `NetworkReportSpec` object that defines the report's parameters like `dateRange`, `dimensions`, `metrics`, filters (`DimensionFilter`), and sorting (`SortCondition`). The response is a stream containing a header, rows of data, and a footer, conforming to specified JSON structures. The report data is sorted and filtered based on parameters that are set in the `NetworkReportSpec`.\n"]] Product info Usage limits Pricing Terms of Service Programs Google Developer Program Google Developer Groups Google Developer Experts Accelerators Google Cloud & NVIDIA Developer consoles Google API Console Google Cloud Platform Console Google Play Console Firebase Console Actions on Google Console Cast SDK Developer Console Chrome Web Store Dashboard Google Home Developer Console Android Chrome Firebase Google Cloud Platform Google AI All products Terms Privacy Manage cookies English Deutsch Español Español – América Latina Français Indonesia Italiano Polski Português – Brasil Tiếng Việt Türkçe Русский עברית العربيّة فارسی हिंदी বাংলা ภาษาไทย 中文 – 简体 中文 – 繁體 日本語 한국어 | 2026-01-13T09:30:11 |
https://www.linkedin.com/company/reddit-com#main-content | Reddit, Inc. | LinkedIn Skip to main content LinkedIn Top Content People Learning Jobs Games Sign in Join for free Reddit, Inc. Social Networking Platforms San Francisco, California 472,304 followers The heart of the internet, where millions gather for conversation and community. See jobs Follow View all 4,550 employees Report this company Overview Jobs Life About us Reddit is the heart of the internet, where millions of people get together to talk about any topic imaginable. Share, vote, and decide what matters in everything from breaking news, to fandoms, lifehacks, gaming, sports, health, and the internet’s cutest animals. With over 100,000 subreddit communities about every topic you could think of (and thousands more you couldn’t), whatever it is, there’s a place for you on Reddit. Interested in joining our growing team? Check out redditinc.com/careers. Website http://redditinc.com External link for Reddit, Inc. Industry Social Networking Platforms Company size 1,001-5,000 employees Headquarters San Francisco, California Type Public Company Founded 2005 Specialties Software Engineering, Full-Stack Engineering, Frontend Engineering, Backend Engineering, Social Media, Data Science , Mobile Apps, and Online Advertising Products Reddit, Inc. Reddit, Inc. Social Networking Software Reddit gives you the best of the internet in one place. Get a constantly updating feed of breaking news, fun stories, pics, memes, and videos just for you. Passionate about something niche? Reddit has thousands of vibrant communities with people that share your interests. Alternatively, find out what’s trending across all of Reddit on r/popular. Reddit is also anonymous so you can be yourself, with your Reddit profile and persona disconnected from your real-world identity. Locations Primary San Francisco, California 94103, US Get directions Employees at Reddit, Inc. Dave Habiger Maria Angelidou-Smith Brian Landers Jon Chester See all employees Updates Reddit, Inc. 472,304 followers 15h Report this post New year, new job? From Communications to Engineering to Data Science, we have tons of open roles at Reddit. 👀 Learn more about what it's like working at the heart of the internet on our Careers page: https://lnkd.in/gy6rqYcK 100 4 Comments Like Comment Share Reddit, Inc. reposted this Adam Collins 4d Report this post For real world advice, try Reddit I couldn’t have said it any better than The Wall Street Journal did today. This story, which is a delightful read from Lettie Teague (you should read it), focuses on recommendations and advice between wine lovers. But the point applies to countless passions, hobbies and interests. In a world increasingly dominated by algorithms, the value of authentic human engagement has never beer higher. And Reddit, Inc. is the most human place on the internet. Reddit is where real people come together to form communities, get answers, share ideas, discuss life, and offer advice. https://lnkd.in/g3DJUHjC For Real-World Advice on Wine, Try Reddit wsj.com 234 20 Comments Like Comment Share Reddit, Inc. 472,304 followers 4d Report this post 🛑 ALERT: It's January 8th, you are now entering the “no more Happy New Year” zone. Proceed with caution. 🛑 1,565 81 Comments Like Comment Share Reddit, Inc. reposted this Reddit for Business 34,754 followers 6d Report this post A fresh year calls for a fresh reset. Join us at the Reddit Conversation Bar to discover the human conversations powering culture, discovery, and what’s next for you & your business in 2026. Also, get a taste of fresh-squeezed Reddit Community Intelligence™ and an early look at our newest ad products. We’d love to see you this week! 📍Find us at CES Reddit HQ Primrose 3, Aria East Convention Center 🗓️ Open for meetings daily 🤝 Reach out to your Reddit rep to schedule time 🕒 Or drop by during open hours: 2–4 PM today & tomorrow …more 148 3 Comments Like Comment Share Reddit, Inc. 472,304 followers 1w Report this post Unfortunately, it's my business again. Reddit, Inc. 472,304 followers 1mo Between now and January 5th, my inbox is none of my business. 2,364 19 Comments Like Comment Share Reddit, Inc. 472,304 followers 1w Report this post The UK is getting on the Reddit train, er, tube. 🇬🇧 By the numbers: - Reddit is now the 6th most visited website by UK internet users ages 18-24. - 3 in 5 UK internet users now leverage Reddit, up from a third in 2023. - More than half of our UK users are women. 71% of them have a personal interest in all things skincare and beauty. - UK subreddits for pregnancy and parenting have doubled in size over the last year. Our COO Jen Wong shares more insights with The Guardian : https://lnkd.in/eZ29Zghu Reddit overtakes TikTok in UK thanks to search algorithms and gen Z theguardian.com 360 7 Comments Like Comment Share Reddit, Inc. 472,304 followers 3w Report this post Happy "15 days until CES" to those who celebrate. 128 12 Comments Like Comment Share Reddit, Inc. 472,304 followers 3w Report this post Between now and January 5th, my inbox is none of my business. 774 22 Comments Like Comment Share Reddit, Inc. reposted this Redditch United Football Club 2,241 followers 3w Report this post Office Display 📈 All the way from America, Reddit Brand Creative Manager (and now huge Reds fan, right David Benham ? 👀), sent us his new office set-up. Can anyone else's office/bedroom/living room beat this? 146 8 Comments Like Comment Share Reddit, Inc. reposted this Alana Saltzman 3w Edited Report this post My first week at Reddit, Inc. I discovered that there were more women than men using our platform in the UK. Since then, I’ve been on a mission to challenge misconceptions of who is a redditor… This latest DAZED piece by Ashleigh Spiliopoulou does just that - with a deep dive into how, and why, women are shifting to Reddit. https://lnkd.in/eekzufRC Reddit is the fastest growing social platform for women in the UK - with millions building a collective handbook for modern life. Whether that’s dissecting your favourite reality TV episode, finding makeup tips for hooded eyes, navigating an NHS referral, or learning how to set up a pension - there’s a community for you. - Almost half of women (45%) on Reddit in the UK have children - communities like r/pregnancyUK and r/UKparenting are booming, serving as late night lifelines. - r/AskWomenOver30 (one of my faves) taps the collective wisdom of women on everything from relationships, to family dynamics, to friendships, to how to navigate work and advocate for yourself. - More than 70% of women on Reddit in the UK are passionate about skincare, beauty, and cosmetics, turning to the platform for advice, education, and recommendations. Reddit is becoming THE place to validate and inform your shopping. - When it comes to health: research shows that 81% of women feel less alone on their journey because of Reddit communities. The platform hosts conversations on everything from reproductive health and chronic conditions to navigating neurodiversity and mental health challenges. We see this in the growth of UK views to communities like r/Menopause, r/endometriosis, r/PCOS, r/autisminwomen, and r/adhdwomen amongst others. What are the conversations you’re coming to Reddit for? Why are so many women joining Reddit? dazeddigital.com 936 43 Comments Like Comment Share Join now to see what you are missing Find people you know at Reddit, Inc. Browse recommended jobs for you View all updates, news, and articles Join now Affiliated pages Reddit for Business Advertising Services San Francisco, CA Similar pages Discord Software Development San Francisco, CA Pinterest Software Development San Francisco, California Airbnb Software Development San Francisco, CA Netflix Entertainment Providers Los Gatos, CA Stripe Technology, Information and Internet South San Francisco, California Spotify Musicians Stockholm, Stockholm County Google Software Development Mountain View, CA Atlassian Software Development Sydney, NSW Dropbox Software Development San Francisco, California Zapier Software Development San Francisco, CA Show more similar pages Show fewer similar pages Browse jobs Analyst jobs 694,057 open jobs Engineer jobs 555,845 open jobs Manager jobs 1,880,925 open jobs Project Manager jobs 253,048 open jobs Director jobs 1,220,357 open jobs Marketing Manager jobs 106,879 open jobs Account Manager jobs 121,519 open jobs Scientist jobs 48,969 open jobs Associate jobs 1,091,945 open jobs Product Manager jobs 199,941 open jobs Senior Software Engineer jobs 78,145 open jobs Senior Product Manager jobs 50,771 open jobs Specialist jobs 768,666 open jobs Machine Learning Engineer jobs 148,937 open jobs Account Executive jobs 71,457 open jobs Customer Service Representative jobs 185,647 open jobs Executive jobs 690,514 open jobs Developer jobs 258,935 open jobs Vice President jobs 235,270 open jobs Staff Software Engineer jobs 64,945 open jobs Show more jobs like this Show fewer jobs like this Funding Reddit, Inc. 9 total rounds Last Round Series F Sep 12, 2021 External Crunchbase Link for last round of funding US$ 410.0M Investors Fidelity + 4 Other investors See more info on crunchbase More searches More searches Engineer jobs Analyst jobs Manager jobs Scientist jobs Director jobs Project Manager jobs Software Engineer jobs Associate jobs Machine Learning Engineer jobs Account Manager jobs Product Manager jobs Senior Product Manager jobs Senior Software Engineer jobs Developer jobs Intern jobs Specialist jobs Marketing Manager jobs Engineering Manager jobs Product Designer jobs Vice President jobs Data Scientist jobs Designer jobs Account Executive jobs User Experience Designer jobs Head jobs Staff Software Engineer jobs Data Analyst jobs Writer jobs Human Resources Specialist jobs Program Manager jobs Consultant jobs Principal Product Manager jobs Operational Specialist jobs Senior Manager jobs Recruiter jobs Client Partner jobs Associate Product Manager jobs Director of Engineering jobs Marketing Director jobs Executive jobs Partner jobs Full Stack Engineer jobs Assistant jobs Senior Scientist jobs Senior Director jobs President jobs Director of Product Management jobs Marketing Specialist jobs Lead Product Manager jobs Accountant jobs Senior Data Engineer jobs Researcher jobs Software Engineering Manager jobs Science Manager jobs Attorney jobs Sales Manager jobs Senior Engineering Manager jobs Coordinator jobs Head of Marketing jobs Sales Director jobs LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language Agree & Join LinkedIn By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . Sign in to see who you already know at Reddit, Inc. Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or New to LinkedIn? Join now By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . | 2026-01-13T09:30:11 |
https://addons.mozilla.org/en-US/firefox/addon/1password-x-password-manager/reviews/2236629/#login | Reviews for 1Password: Password Manager – Add-ons for Firefox (en-US) To use these add-ons, you'll need to download Firefox . Dismiss this notice Firefox Browser Add-ons Extensions Themes More… for Firefox Dictionaries & Language Packs Other Browser Sites Add-ons for Android Log in Search Search Reviews for 1Password: Password Manager 1Password: Password Manager by 1Password Rated 3.8 out of 5 3.8 Stars out of 5 5 1,033 4 182 3 108 2 106 1 342 Review by Will Blackwood Rated 4 out of 5 by Will Blackwood , 7 months ago Show all reviews Show only five-star reviews Show only four-star reviews Show only three-star reviews Show only two-star reviews Show only one-star reviews Go to Mozilla's homepage Add-ons About Firefox Add-ons Blog Extension Workshop Developer Hub Developer Policies Community Blog Forum Report a bug Review Guide Browsers Desktop Mobile Enterprise Products Browsers VPN Relay Monitor Pocket Bluesky (@firefox.com) Instagram (Firefox) YouTube (firefoxchannel) Privacy Cookies Legal Except where otherwise noted , content on this site is licensed under the Creative Commons Attribution Share-Alike License v3.0 or any later version. Change language Čeština Deutsch Dolnoserbšćina Ελληνικά English (Canadian) English (British) English (US) Español (de Argentina) Español (de Chile) Español (de España) Español (de México) suomi Français Furlan Frysk עברית Hrvatski Hornjoserbsce magyar Interlingua Italiano 日本語 ქართული Taqbaylit 한국어 Norsk bokmål Nederlands Norsk nynorsk Polski Português (do Brasil) Português (Europeu) Română Русский slovenčina Slovenščina Shqip Svenska Türkçe Українська Tiếng Việt 中文 (简体) 正體中文 (繁體) | 2026-01-13T09:30:11 |
https://developers.cloudflare.com/ssl/concepts/#ai:local:ssl | Concepts · Cloudflare SSL/TLS docs Skip to content Cloudflare Docs Search Docs Directory APIs SDKs Help Log in Select theme Dark Light Auto SSL/TLS No results found. Try a different search term, or use our global search . Overview Concepts Get started Edge certificates Overview Universal SSL Overview Enable Universal SSL certificates Disable Universal SSL certificates Alerts Limitations Troubleshooting Advanced certificates Overview Manage advanced certificates API commands Custom certificates Overview Manage custom certificates Renewal and expiration Bundle methodologies Remove key file password Troubleshooting Enforce HTTPS connections Domain control validation (DCV) Overview Methods Overview Delegated TXT HTTP Validation backoff schedule Domain control validation flow Troubleshooting Geo Key Manager Overview Beta Setup Supported options Add CAA records Staging environment Beta Backup certificates ECH Protocol Beta Additional options Cipher suites About Customize cipher suites Overview Use the dashboard Use the API Security levels Compliance standards Supported cipher suites Troubleshooting Certificate Transparency Monitoring HTTP Strict Transport Security (HSTS) Certificate Signing Requests (CSRs) TLS 1.3 Minimum TLS Version Automatic HTTPS Rewrites Total TLS Overview Enable Error messages Always Use HTTPS Opportunistic Encryption Troubleshooting CAs and certificates FAQ Certification Authority Authorization (CAA) FAQ Origin server Encryption modes Overview Off (no encryption) Flexible Full Full (strict) Strict (SSL-Only Origin Pull) SSL/TLS Recommender Deprecated Cloudflare origin CA Setup Troubleshooting Authenticated Origin Pulls (mTLS) Overview About AWS integration Setup Zone-level Per-hostname Manage certificates Rollback Custom Origin Trust Store Cipher suites Client certificates (mTLS) Overview Create a client certificate Enable mTLS Bring your own CA for mTLS Forward certificate to server Label client certificates Revoke a client certificate Configure your mobile app or IoT device Troubleshooting mTLS for Zero Trust ↗ Cloudflare for SaaS ↗ Keyless SSL Overview Get started Cloudflare Tunnel Public DNS Hardware security modules Overview Configuration AWS cloud HSM Azure Dedicated HSM Azure Managed HSM Entrust nShield Connect Fortanix DSM Google Cloud HSM IBM Cloud HSM SoftHSMv2 Upgrade your key server Reference High availability Scaling and benchmarking Keyless delegation Glossary Troubleshooting Post-quantum About PQC PQC support PQC to your origin PQC and Zero Trust Reference TLS protocols Certificate and hostname priority Certificate authorities Browser compatibility Migration guides Entrust distrust Certificate pinning Certificate statuses Validity periods and renewal Features and plans Cloudflare and CVE-2019-1559 PCI compliance and vulnerabilities mitigation Troubleshooting Full resources list General SSL errors ERR_SSL_VERSION_OR_CIPHER_MISMATCH ERR_TOO_MANY_REDIRECTS Mixed content errors FAQ Changelog GitHub X.com YouTube Select theme Dark Light Auto On this page Overview SSL/TLS certificate Edge certificate Origin certificate Validity period Certificate authority (CA) Validation level Origin pull Cipher suites Trust store Chain of trust On this page Overview SSL/TLS certificate Edge certificate Origin certificate Validity period Certificate authority (CA) Validation level Origin pull Cipher suites Trust store Chain of trust Was this helpful? Edit Issue Directory … SSL/TLS Concepts Copy page Concepts This page defines and articulates key concepts that are relevant to Cloudflare SSL/TLS and are used in this documentation. For more concepts and broader descriptions, check out the Cloudflare Learning Center ↗ . SSL/TLS certificate An SSL/TLS certificate is what enables websites and applications to establish secure connections. With SSL/TLS, a client - such as a browser - can verify the authenticity and integrity of the server it is connecting with, and use encryption to exchange information. Since Cloudflare's global network ↗ is at the core of several products and services that Cloudflare offers, what this implies in terms of SSL/TLS is that, instead of only one certificate, there can actually be two certificates involved in a single request: an edge certificate and an origin certificate. Edge certificate The edge certificates are the ones that Cloudflare presents to clients visiting your website or application. You can manage edge certificates through the Cloudflare Dashboard ↗ . Origin certificate Origin certificates guarantee the security and authentication on the other side of the network, between Cloudflare and the origin server of your website or application. Origin certificates are managed on your origin server. SSL/TLS encryption modes control whether and how Cloudflare will use both these ceritifcates, and you can choose between different modes on the SSL/TLS overview page ↗ . Validity period One common aspect of every SSL/TLS certificate is that they must have a fixed expiration date. If a certificate is expired, clients - such as your visitor's browser - will consider that a secure connection cannot be established, resulting in warnings or errors. Different certificate authorities (CAs) support different validity periods. Cloudflare works with them to guarantee that both Universal and Advanced edge certificates are always renewed. Certificate authority (CA) A certificate authority (CA) is a trusted third party that generates and gives out SSL/TLS certificates. The CA digitally signs the certificates with their own private key, allowing client devices - such as your visitor's browser - to verify that the certificate is trustworthy. As explained in the article about what is an ssl certificate ↗ , this means that, besides not being expired, an SSL/TLS certificate should be issued by a certificate authority (CA) in order to avoid warnings or errors. Validation level SSL/TLS certificates vary in terms of the level to which a CA has validated them. As explained in the article about types of certificates ↗ , SSL/TLS certificates can be DV (Domain Validated), OV (Organization Validated) or EV (Extended Validation). Certificates issued through Cloudflare - Universal , Advanced , and Custom Hostname certificates - are Domain Validated (DV). You can upload a custom certificate if your organization needs OV or EV certificates. Origin pull When visitors request content from your website or application, Cloudflare first attempts to serve content from the cache ↗ . If this attempt fails, Cloudflare sends a request back to your origin web server to get the content. This request between Cloudflare and your origin web server is called origin pull. This relates to the difference between edge certificates and origin certificates , and also explains why some specifications such as cipher suites can be set differently depending on whether they refer to the connection between Cloudflare and your visitor's browser or between Cloudflare and your origin server. Cipher suites Besides the authentication and integrity aspects that valid certificates guarantee, the other important aspect of SSL/TLS certificates is encryption. Cipher suites determine the set of algorithms that can be used for encryption/decryption and that will be negotiated during an SSL/TLS handshake ↗ . For the purpose of this documentation, keep in mind that cipher suites supported at Cloudflare's network may not be the same as cipher suites presented by Cloudflare to your origin server . Trust store The list of certificate authority (CA) and intermediate certificates that are trusted by operating systems, web browsers or other software that interacts with SSL/TLS certificates is called trust store. Cloudflare maintains its trust store on a public GitHub repository ↗ . While for most cases you do not have to worry about this list or how it is used when a client checks your SSL/TLS certificate, some features such as Custom Origin Trust Store , and processes such as bundle methodologies , are directly related to it. Chain of trust Depending on your organization requirements, or if you have to troubleshoot an issue with your certificates, for example, you might come across the terms root certificate, intermediate certificate and leaf certificate. These terms refer to the way in which the certificate presented to a client - the leaf certificate - has to be traceable back to a trusted certificate authority (CA) certificate - the root certificate ↗ . This process is structured around a chain of trust ↗ . Was this helpful? Edit page Last updated: Sep 23, 2025 Previous Overview Next Get started Resources API New to Cloudflare? Directory Sponsorships Open Source Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Speed Test Is BGP Safe Yet? RPKI Toolkit Certificate Transparency Community X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings | 2026-01-13T09:30:11 |
https://developers.cloudflare.com/ai-gateway/usage/providers/baseten/ | Baseten · Cloudflare AI Gateway docs Skip to content Cloudflare Docs Search Docs Directory APIs SDKs Help Log in Select theme Dark Light Auto AI Gateway No results found. Try a different search term, or use our global search . Overview Getting started Using AI Gateway Unified API (OpenAI compat) Provider Native Workers AI Amazon Bedrock Anthropic Azure OpenAI Baseten Cartesia Cerebras Cohere Deepgram DeepSeek ElevenLabs Fal AI Google AI Studio Google Vertex AI Groq HuggingFace Ideogram Mistral AI OpenAI OpenRouter Parallel Perplexity Replicate xAI WebSockets API Beta Overview Realtime WebSockets API Non-realtime WebSockets API Features Overview Unified Billing Caching Rate limiting Dynamic routing Beta Overview Using a dynamic route JSON Configuration Data Loss Prevention (DLP) Beta Overview Set up Data Loss Prevention (DLP) Guardrails Beta Overview Set up Guardrails Supported model types Usage considerations Configuration BYOK (Store Keys) Beta Custom costs Custom Providers Beta Manage gateways Request handling Authenticated Gateway Observability Costs Custom metadata Analytics Logging Overview Workers Logpush Integrations Vercel AI SDK Agents ↗ AI Gateway Binding Methods Workers AI Tutorials Platform Overview Limits Pricing Audit logs Changelog Header Glossary REST API reference ↗ API MCP server ↗ MCP AI Assistant ↗ Architectures LLM resources llms.txt prompt.txt AI Gateway llms-full.txt Developer Platform llms-full.txt GitHub X.com YouTube Select theme Dark Light Auto On this page Overview Endpoint Prerequisites OpenAI-compatible chat completions API cURL Use OpenAI SDK with JavaScript OpenAI-Compatible Endpoint Model-specific endpoints cURL Use with JavaScript On this page Overview Endpoint Prerequisites OpenAI-compatible chat completions API cURL Use OpenAI SDK with JavaScript OpenAI-Compatible Endpoint Model-specific endpoints cURL Use with JavaScript Was this helpful? Edit Issue Directory … AI Gateway Using AI Gateway Provider Native Baseten Copy page Baseten Baseten ↗ provides infrastructure for building and deploying machine learning models at scale. Baseten offers access to various language models through a unified chat completions API. Endpoint https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/baseten Prerequisites When making requests to Baseten, ensure you have the following: Your AI Gateway Account ID. Your AI Gateway gateway name. An active Baseten API token. The name of the Baseten model you want to use. OpenAI-compatible chat completions API Baseten provides an OpenAI-compatible chat completions API for supported models. cURL Example fetch request curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/baseten/v1/chat/completions \ --header 'Authorization: Bearer {baseten_api_token}' \ --header 'Content-Type: application/json' \ --data '{ "model": "openai/gpt-oss-120b", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] }' Use OpenAI SDK with JavaScript JavaScript import OpenAI from "openai" ; const apiKey = "{baseten_api_token}" ; const accountId = "{account_id}" ; const gatewayId = "{gateway_id}" ; const baseURL = `https://gateway.ai.cloudflare.com/v1/ ${ accountId } / ${ gatewayId } /baseten` ; const openai = new OpenAI ( { apiKey , baseURL , } ) ; const model = "openai/gpt-oss-120b" ; const messages = [ { role : "user" , content : "What is Cloudflare?" } ] ; const chatCompletion = await openai . chat . completions . create ( { model , messages , } ) ; console . log ( chatCompletion ) ; OpenAI-Compatible Endpoint You can also use the OpenAI-compatible endpoint ( /ai-gateway/usage/chat-completion/ ) to access Baseten models using the OpenAI API schema. To do so, send your requests to: https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions Specify: { " model " : "baseten/{model}" } Model-specific endpoints For models that don't use the OpenAI-compatible API, you can access them through their specific model endpoints. cURL Example fetch request curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/baseten/model/{model_id} \ --header 'Authorization: Bearer {baseten_api_token}' \ --header 'Content-Type: application/json' \ --data '{ "prompt": "What is Cloudflare?", "max_tokens": 100 }' Use with JavaScript JavaScript const accountId = "{account_id}" ; const gatewayId = "{gateway_id}" ; const basetenApiToken = "{baseten_api_token}" ; const modelId = "{model_id}" ; const baseURL = `https://gateway.ai.cloudflare.com/v1/ ${ accountId } / ${ gatewayId } /baseten` ; const response = await fetch ( ` ${ baseURL } /model/ ${ modelId } ` , { method : "POST" , headers : { "Authorization" : `Bearer ${ basetenApiToken } ` , "Content-Type" : "application/json" , }, body : JSON . stringify ( { prompt : "What is Cloudflare?" , max_tokens : 100 , } ) , } ) ; const result = await response . json () ; console . log ( result ) ; Was this helpful? Edit page Last updated: Nov 25, 2025 Previous Azure OpenAI Next Cartesia Resources API New to Cloudflare? Directory Sponsorships Open Source Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Speed Test Is BGP Safe Yet? RPKI Toolkit Certificate Transparency Community X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings | 2026-01-13T09:30:11 |
https://developers.cloudflare.com/ai-gateway/reference/pricing/ | Pricing · Cloudflare AI Gateway docs Skip to content Cloudflare Docs Search Docs Directory APIs SDKs Help Log in Select theme Dark Light Auto AI Gateway No results found. Try a different search term, or use our global search . Overview Getting started Using AI Gateway Unified API (OpenAI compat) Provider Native Workers AI Amazon Bedrock Anthropic Azure OpenAI Baseten Cartesia Cerebras Cohere Deepgram DeepSeek ElevenLabs Fal AI Google AI Studio Google Vertex AI Groq HuggingFace Ideogram Mistral AI OpenAI OpenRouter Parallel Perplexity Replicate xAI WebSockets API Beta Overview Realtime WebSockets API Non-realtime WebSockets API Features Overview Unified Billing Caching Rate limiting Dynamic routing Beta Overview Using a dynamic route JSON Configuration Data Loss Prevention (DLP) Beta Overview Set up Data Loss Prevention (DLP) Guardrails Beta Overview Set up Guardrails Supported model types Usage considerations Configuration BYOK (Store Keys) Beta Custom costs Custom Providers Beta Manage gateways Request handling Authenticated Gateway Observability Costs Custom metadata Analytics Logging Overview Workers Logpush Integrations Vercel AI SDK Agents ↗ AI Gateway Binding Methods Workers AI Tutorials Platform Overview Limits Pricing Audit logs Changelog Header Glossary REST API reference ↗ API MCP server ↗ MCP AI Assistant ↗ Architectures LLM resources llms.txt prompt.txt AI Gateway llms-full.txt Developer Platform llms-full.txt GitHub X.com YouTube Select theme Dark Light Auto On this page Overview Persistent logs Free allocation and overage pricing Logpush Fine print On this page Overview Persistent logs Free allocation and overage pricing Logpush Fine print Was this helpful? Edit Issue Directory … AI Gateway Platform Pricing Copy page Pricing AI Gateway is available to use on all plans. AI Gateway's core features available today are offered for free, and all it takes is a Cloudflare account and one line of code to get started . Core features include: dashboard analytics, caching, and rate limiting. We will continue to build and expand AI Gateway. Some new features may be additional core features that will be free while others may be part of a premium plan. We will announce these as they become available. You can monitor your usage in the AI Gateway dashboard. Persistent logs Persistent logs are available on all plans, with a free allocation for both free and paid plans. Charges for additional logs beyond those limits are based on the number of logs stored per month. Free allocation and overage pricing Plan Free logs stored Overage pricing Workers Free 100,000 logs total N/A - Upgrade to Workers Paid Workers Paid 1,000,000 logs total N/A Allocations are based on the total logs stored across all gateways. For guidance on managing or deleting logs, please see our documentation . Logpush Logpush is only available on the Workers Paid plan. Paid plan Requests 10 million / month, +$0.05/million Fine print Prices subject to change. If you are an Enterprise customer, reach out to your account team to confirm pricing details. Was this helpful? Edit page Last updated: Nov 10, 2025 Previous Limits Next Audit logs Resources API New to Cloudflare? Directory Sponsorships Open Source Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Speed Test Is BGP Safe Yet? RPKI Toolkit Certificate Transparency Community X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings | 2026-01-13T09:30:11 |
https://www.linkedin.com/legal/user-agreement?session_redirect=%2Fservices%2Fproducts%2Fcategories%2Fserver-backup-software&trk=registration-frontend_join-form-user-agreement#key-terms-2 | User Agreement | LinkedIn Skip to main content User Agreement Summary of User Agreement Privacy Policy Professional Community Policies Cookie Policy Copyright Policy Regional Info EU Notice California Privacy Disclosure U.S. State Privacy Laws User Agreement Summary of User Agreement Privacy Policy Professional Community Policies Cookie Policy Copyright Policy Regional Info EU Notice California Privacy Disclosure U.S. State Privacy Laws User Agreement Effective on November 3, 2025 Our mission is to connect the world’s professionals to allow them to be more productive and successful. Our services are designed to promote economic opportunity for our members by enabling you and millions of other professionals to meet, exchange ideas, learn, and find opportunities or employees, work, and make decisions in a network of trusted relationships. Table of Contents: Introduction Obligations Rights and Limits Disclaimer and Limit of Liability Termination Governing Law and Dispute Resolution General Terms LinkedIn “Dos and Don’ts” Complaints Regarding Content How To Contact Us Introduction 1.1 Contract When you use our Services you agree to all of these terms. Your use of our Services is also subject to our Cookie Policy and our Privacy Policy, which covers how we collect, use, share, and store your personal information. By creating a LinkedIn account or accessing or using our Services (described below), you are agreeing to enter into a legally binding contract with LinkedIn (even if you are using third party credentials or using our Services on behalf of a company). If you do not agree to this contract (“Contract” or “User Agreement”), do not create an account or access or otherwise use any of our Services. If you wish to terminate this Contract at any time, you can do so by closing your account and no longer accessing or using our Services. As a Visitor or Member of our Services, the collection, use, and sharing of your personal data is subject to our Privacy Policy , our Cookie Policy and other documents referenced in our Privacy Policy , and updates. You acknowledge and have read our Privacy Policy . Services This Contract applies to LinkedIn.com, LinkedIn-branded apps, and other LinkedIn-related sites, apps, communications, and other services that state that they are offered under this Contract (“Services”), including the offsite collection of data for those Services, such as via our ads and the “Apply with LinkedIn” and “Share with LinkedIn” plugins. LinkedIn and other Key Terms You are entering into this Contract with LinkedIn (also referred to as “we” and “us”). Designated Countries . We use the term “Designated Countries” to refer to countries in the European Union (EU), European Economic Area (EEA), and Switzerland. If you reside in the “Designated Countries”, you are entering into this Contract with LinkedIn Ireland Unlimited Company (“LinkedIn Ireland”) and LinkedIn Ireland will be the controller of your personal data provided to, or collected by or for, or processed in connection with our Services. If you reside outside of the “Designated Countries”, you are entering into this Contract with LinkedIn Corporation (“LinkedIn Corp.”) and LinkedIn Corp. will be the controller of (or business responsible for) your personal data provided to, or collected by or for, or processed in connection with our Services. Affiliates . Affiliates are companies controlling, controlled by or under common control with us, including, for example, LinkedIn Ireland, LinkedIn Corporation, LinkedIn Singapore and Microsoft Corporation or any of its subsidiaries (e.g., Github, Inc.). Social Action . Actions that members take on our services such as likes, comments, follows, sharing content. Content . Content includes, for example, feed posts, feedback, comments, profiles, articles (and contributions), group posts, job postings, messages (including InMails), videos, photos, audio, and/or PDFs. 1.2 Members and Visitors This Contract applies to Members and Visitors. When you register and join the LinkedIn Services, you become a “Member”. If you have chosen not to register for our Services, you may access certain features as a “Visitor.” 1.3 Changes We may make changes to this Contract. We may modify this Contract, our Privacy Policy and our Cookie Policy from time to time. If we materially change these terms or if we are legally required to provide notice, we will provide you notice through our Services, or by other means, to provide you the opportunity to review the changes before they become effective. However, we may not always provide prior notice of changes to these terms (1) when those changes are legally required to be implemented with immediate effect, or (2) when those changes relate to a newly launched service or feature. We agree that changes cannot be retroactive. If you object to any of these changes, you may close your account . Your continued use of our Services after we publish or send a notice about our changes to these terms means that you are consenting to the updated terms as of their effective date. 2. Obligations 2.1 Service Eligibility Here are some promises that you make to us in this Contract: You’re eligible to enter into this Contract and you are at least our “Minimum Age.” The Services are not for use by anyone under the age of 16. To use the Services, you agree that: (1) you must be the "Minimum Age" (described below) or older; (2) you will only have one LinkedIn account, which must be in your real name; and (3) you are not already restricted by LinkedIn from using the Services. Creating an account with false information is a violation of our terms, including accounts registered on behalf of others or persons under the age of 16. “Minimum Age” means 16 years old. However, if law requires that you must be older in order for LinkedIn to lawfully provide the Services to you without parental consent (including using your personal data) then the Minimum Age is such older age. Learn More 2.2 Your Account You will keep your password a secret You will not share your account with anyone else and will follow our policies and the law. Members are account holders. You agree to: (1) protect against wrongful access to your account (e.g., use a strong password and keep it confidential); (2) not share or transfer your account or any part of it (e.g., sell or transfer the personal data of others by transferring your connections); and (3) follow the law, our list of Dos and Don’ts (below), and our Professional Community Policies . Learn More You are responsible for anything that happens through your account unless you close it or report misuse. As between you and others (including your employer), your account belongs to you. However, if the Services were purchased by another party for you to use in connection with your work for them (e.g., Recruiter seat or LinkedIn Learning subscription bought by your employer), the party paying for such Service has the right to control access to and get reports on your use of such paid Service; however, they do not have rights to your personal account. 2.3 Payment You’ll honor your payment obligations and you are okay with us storing your payment information. You understand that there may be fees and taxes that are added to our prices. Refunds are subject to our policy, and we may modify our prices and those modified prices will apply prospectively. If you buy any of our paid Services, you agree to pay us the applicable fees and taxes and you agree to the additional terms specific to the paid Services. Failure to pay these fees will result in the termination of your paid Services. Also, you agree that: Your purchase may be subject to foreign exchange fees or differences in prices based on location (e.g., exchange rates). We may store and continue billing your payment method (e.g., credit card), even after it has expired, to avoid interruptions in your paid Services and to use it to pay for other Services you may buy. If your primary payment method fails, we may automatically charge a secondary payment method, if you have provided one. You may update or change your payment method. Learn more If you purchase a subscription, your payment method automatically will be charged at the start of each subscription period for the fees and taxes applicable to that period. To avoid future charges, cancel before the renewal date. Learn how to cancel or suspend your paid subscription Services. We may modify our prices effective prospectively upon reasonable notice to the extent allowed under the law.< | 2026-01-13T09:30:11 |
https://developers.cloudflare.com/ai-gateway/observability/logging/ | Logging · Cloudflare AI Gateway docs Skip to content Cloudflare Docs Search Docs Directory APIs SDKs Help Log in Select theme Dark Light Auto AI Gateway No results found. Try a different search term, or use our global search . Overview Getting started Using AI Gateway Unified API (OpenAI compat) Provider Native Workers AI Amazon Bedrock Anthropic Azure OpenAI Baseten Cartesia Cerebras Cohere Deepgram DeepSeek ElevenLabs Fal AI Google AI Studio Google Vertex AI Groq HuggingFace Ideogram Mistral AI OpenAI OpenRouter Parallel Perplexity Replicate xAI WebSockets API Beta Overview Realtime WebSockets API Non-realtime WebSockets API Features Overview Unified Billing Caching Rate limiting Dynamic routing Beta Overview Using a dynamic route JSON Configuration Data Loss Prevention (DLP) Beta Overview Set up Data Loss Prevention (DLP) Guardrails Beta Overview Set up Guardrails Supported model types Usage considerations Configuration BYOK (Store Keys) Beta Custom costs Custom Providers Beta Manage gateways Request handling Authenticated Gateway Observability Costs Custom metadata Analytics Logging Overview Workers Logpush Integrations Vercel AI SDK Agents ↗ AI Gateway Binding Methods Workers AI Tutorials Platform Overview Limits Pricing Audit logs Changelog Header Glossary REST API reference ↗ API MCP server ↗ MCP AI Assistant ↗ Architectures LLM resources llms.txt prompt.txt AI Gateway llms-full.txt Developer Platform llms-full.txt GitHub X.com YouTube Select theme Dark Light Auto On this page Overview Default configuration Per-request logging Collect logs (cf-aig-collect-log) Managing log storage How to delete logs Automatic Log Deletion Manual deletion API deletion On this page Overview Default configuration Per-request logging Collect logs (cf-aig-collect-log) Managing log storage How to delete logs Automatic Log Deletion Manual deletion API deletion Was this helpful? Edit Issue Directory … AI Gateway Observability Logging Copy page Logging Logging is a fundamental building block for application development. Logs provide insights during the early stages of development and are often critical to understanding issues occurring in production. Your AI Gateway dashboard shows logs of individual requests, including the user prompt, model response, provider, timestamp, request status, token usage, cost, and duration. These logs persist, giving you the flexibility to store them for your preferred duration and do more with valuable request data. By default, each gateway can store up to 10 million logs. You can customize this limit per gateway in your gateway settings to align with your specific requirements. If your storage limit is reached, new logs will stop being saved. To continue saving logs, you must delete older logs to free up space for new logs. To learn more about your plan limits, refer to Limits . We recommend using an authenticated gateway when storing logs to prevent unauthorized access and protects against invalid requests that can inflate log storage usage and make it harder to find the data you need. Learn more about setting up an authenticated gateway . Default configuration Logs, which include metrics as well as request and response data, are enabled by default for each gateway. This logging behavior will be uniformly applied to all requests in the gateway. If you are concerned about privacy or compliance and want to turn log collection off, you can go to settings and opt out of logs. If you need to modify the log settings for specific requests, you can override this setting on a per-request basis. To change the default log configuration in the dashboard: In the Cloudflare dashboard, go to the AI Gateway page. Go to AI Gateway Select Settings . Change the Logs setting to your preference. Per-request logging To override the default logging behavior set in the settings tab, you can define headers on a per-request basis. Collect logs ( cf-aig-collect-log ) The cf-aig-collect-log header allows you to bypass the default log setting for the gateway. If the gateway is configured to save logs, the header will exclude the log for that specific request. Conversely, if logging is disabled at the gateway level, this header will save the log for that request. In the example below, we use cf-aig-collect-log to bypass the default setting to avoid saving the log. Terminal window curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/openai/chat/completions \ --header "Authorization: Bearer $TOKEN " \ --header 'Content-Type: application/json' \ --header 'cf-aig-collect-log: false \ --data ' { "model" : "gpt-4o-mini", "messages" : [ { "role" : "user", "content" : "What is the email address and phone number of user123?" } ] } ' Managing log storage To manage your log storage effectively, you can: Set Storage Limits: Configure a limit on the number of logs stored per gateway in your gateway settings to ensure you only pay for what you need. Enable Automatic Log Deletion: Activate the Automatic Log Deletion feature in your gateway settings to automatically delete the oldest logs once the log limit you've set or the default storage limit of 10 million logs is reached. This ensures new logs are always saved without manual intervention. How to delete logs To manage your log storage effectively and ensure continuous logging, you can delete logs using the following methods: Automatic Log Deletion To maintain continuous logging within your gateway's storage constraints, enable Automatic Log Deletion in your Gateway settings. This feature automatically deletes the oldest logs once the log limit you've set or the default storage limit of 10 million logs is reached, ensuring new logs are saved without manual intervention. Manual deletion To manually delete logs through the dashboard, navigate to the Logs tab in the dashboard. Use the available filters such as status, cache, provider, cost, or any other options in the dropdown to refine the logs you wish to delete. Once filtered, select Delete logs to complete the action. See full list of available filters and their descriptions below: Filter category Filter options Filter by description Status error, status error type or status. Cache cached, not cached based on whether they were cached or not. Provider specific providers the selected AI provider. AI Models specific models the selected AI model. Cost less than, greater than cost, specifying a threshold. Request type Universal, Workers AI Binding, WebSockets the type of request. Tokens Total tokens, Tokens In, Tokens Out token count (less than or greater than). Duration less than, greater than request duration. Feedback equals, does not equal (thumbs up, thumbs down, no feedback) feedback type. Metadata Key equals, does not equal specific metadata keys. Metadata Value equals, does not equal specific metadata values. Log ID equals, does not equal a specific Log ID. Event ID equals, does not equal a specific Event ID. API deletion You can programmatically delete logs using the AI Gateway API. For more comprehensive information on the DELETE logs endpoint, check out the Cloudflare API documentation . Was this helpful? Edit page Last updated: Aug 20, 2025 Previous Analytics Next Workers Logpush Resources API New to Cloudflare? Directory Sponsorships Open Source Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Speed Test Is BGP Safe Yet? RPKI Toolkit Certificate Transparency Community X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings | 2026-01-13T09:30:11 |
https://developers.cloudflare.com/ai-gateway/features/ | Features · Cloudflare AI Gateway docs Skip to content Cloudflare Docs Search Docs Directory APIs SDKs Help Log in Select theme Dark Light Auto AI Gateway No results found. Try a different search term, or use our global search . Overview Getting started Using AI Gateway Unified API (OpenAI compat) Provider Native Workers AI Amazon Bedrock Anthropic Azure OpenAI Baseten Cartesia Cerebras Cohere Deepgram DeepSeek ElevenLabs Fal AI Google AI Studio Google Vertex AI Groq HuggingFace Ideogram Mistral AI OpenAI OpenRouter Parallel Perplexity Replicate xAI WebSockets API Beta Overview Realtime WebSockets API Non-realtime WebSockets API Features Overview Unified Billing Caching Rate limiting Dynamic routing Beta Overview Using a dynamic route JSON Configuration Data Loss Prevention (DLP) Beta Overview Set up Data Loss Prevention (DLP) Guardrails Beta Overview Set up Guardrails Supported model types Usage considerations Configuration BYOK (Store Keys) Beta Custom costs Custom Providers Beta Manage gateways Request handling Authenticated Gateway Observability Costs Custom metadata Analytics Logging Overview Workers Logpush Integrations Vercel AI SDK Agents ↗ AI Gateway Binding Methods Workers AI Tutorials Platform Overview Limits Pricing Audit logs Changelog Header Glossary REST API reference ↗ API MCP server ↗ MCP AI Assistant ↗ Architectures LLM resources llms.txt prompt.txt AI Gateway llms-full.txt Developer Platform llms-full.txt GitHub X.com YouTube Select theme Dark Light Auto On this page Overview Core Features Performance & Cost Optimization Security & Safety Observability & Analytics Advanced Configuration Feature Comparison by Use Case Getting Started with Features On this page Overview Core Features Performance & Cost Optimization Security & Safety Observability & Analytics Advanced Configuration Feature Comparison by Use Case Getting Started with Features Was this helpful? Edit Issue Directory … AI Gateway Features Copy page Features AI Gateway provides a comprehensive set of features to help you build, deploy, and manage AI applications with confidence. From performance optimization to security and observability, these features work together to create a robust AI infrastructure. Core Features Performance & Cost Optimization Caching Serve identical requests directly from Cloudflare's global cache, reducing latency by up to 90% and significantly cutting costs by avoiding repeated API calls to AI providers. Key benefits: Reduced response times for repeated queries Lower API costs through cache hits Configurable TTL and per-request cache control Works across all supported AI providers Use Caching Rate Limiting Control application scaling and protect against abuse with flexible rate limiting options. Set limits based on requests per time window with sliding or fixed window techniques. Key benefits: Prevent API quota exhaustion Control costs and usage patterns Configurable per gateway or per request Multiple rate limiting techniques available Use Rate Limiting Dynamic Routing Create sophisticated request routing flows without code changes. Route requests based on user segments, geography, content analysis, or A/B testing requirements through a visual interface. Key benefits: Visual flow-based configuration User-based and geographic routing A/B testing and fractional traffic splitting Context-aware routing based on request content Dynamic rate limiting with automatic fallbacks Use Dynamic Routing Security & Safety Guardrails Deploy AI applications safely with real-time content moderation. Automatically detect and block harmful content in both user prompts and model responses across all providers. Key benefits: Consistent moderation across all AI providers Real-time prompt and response evaluation Configurable content categories and actions Compliance and audit capabilities Enhanced user safety and trust Use Guardrails Data Loss Prevention (DLP) Protect your organization from inadvertent exposure of sensitive data through AI interactions. Scan prompts and responses for PII, financial data, and other sensitive information. Key benefits: Real-time scanning of AI prompts and responses Detection of PII, financial, healthcare, and custom data patterns Configurable actions: flag or block sensitive content Integration with Cloudflare's enterprise DLP solution Compliance support for GDPR, HIPAA, and PCI DSS Use Data Loss Prevention (DLP) Authentication Secure your AI Gateway with token-based authentication. Control access to your gateways and protect against unauthorized usage. Key benefits: Token-based access control Configurable per gateway Integration with Cloudflare's security infrastructure Audit trail for access attempts Use Authentication Bring Your Own Keys (BYOK) Securely store and manage AI provider API keys in Cloudflare's encrypted infrastructure. Remove hardcoded keys from your applications while maintaining full control. Key benefits: Encrypted key storage at rest and in transit Centralized key management across providers Easy key rotation without code changes Support for 20+ AI providers Enhanced security and compliance Use Bring Your Own Keys (BYOK) Observability & Analytics Analytics Gain deep insights into your AI application usage with comprehensive analytics. Track requests, tokens, costs, errors, and performance across all providers. Key benefits: Real-time usage metrics and trends Cost tracking and estimation across providers Error monitoring and troubleshooting Cache hit rates and performance insights GraphQL API for custom dashboards Use Analytics Logging Capture detailed logs of all AI requests and responses for debugging, compliance, and analysis. Configure log retention and export options. Key benefits: Complete request/response logging Configurable log retention policies Export capabilities via Logpush Custom metadata support Compliance and audit support Use Logging Custom Metadata Enrich your logs and analytics with custom metadata. Tag requests with user IDs, team information, or any custom data for enhanced filtering and analysis. Key benefits: Enhanced request tracking and filtering User and team-based analytics Custom business logic integration Improved debugging and troubleshooting Use Custom Metadata Advanced Configuration Custom Costs Override default pricing with your negotiated rates or custom cost models. Apply custom costs at the request level for accurate cost tracking. Key benefits: Accurate cost tracking with negotiated rates Per-request cost customization Better budget planning and forecasting Support for enterprise pricing agreements Use Custom Costs Feature Comparison by Use Case Use Case Recommended Features Cost Optimization Caching, Rate Limiting, Custom Costs High Availability Fallbacks using Dynamic Routing Security & Compliance Guardrails, DLP, Authentication, BYOK, Logging Performance Monitoring Analytics, Logging, Custom Metadata A/B Testing Dynamic Routing, Custom Metadata, Analytics Getting Started with Features Start with the basics : Enable Caching and Analytics for immediate benefits Add reliability : Configure Fallbacks and Rate Limiting using Dynamic routing Enhance security : Implement Guardrails , DLP , and Authentication All features work seamlessly together and across all 20+ supported AI providers. Get started with AI Gateway to begin using these features in your applications. Was this helpful? Edit page Last updated: Sep 2, 2025 Previous Non-realtime WebSockets API Next Unified Billing Resources API New to Cloudflare? Directory Sponsorships Open Source Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Speed Test Is BGP Safe Yet? RPKI Toolkit Certificate Transparency Community X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings | 2026-01-13T09:30:11 |
https://extensionworkshop.com/documentation/develop/#user-experience | Create extensions for Firefox and Firefox for Android | Firefox Extension Workshop Extension Workshop Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Submit or Manage Extensions Search Submit or Manage Extensions Search Select a section Page Name Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name <a href="#create-a-captivating- | 2026-01-13T09:30:11 |
https://developers.google.com/admob/api/v1/getting-started?hl=zh-tw | 開始使用 AdMob API | Google for Developers 跳至主要內容 AdMob API / English Deutsch Español Español – América Latina Français Indonesia Italiano Polski Português – Brasil Tiếng Việt Türkçe Русский עברית العربيّة فارسی हिंदी বাংলা ภาษาไทย 中文 – 简体 中文 – 繁體 日本語 한국어 登入 AdMob 指南 參考資料 程式庫與範例 支援 AdMob API AdMob 指南 參考資料 程式庫與範例 支援 開始使用 基本概念 必備條件 常見錯誤 授權 總覽 設定 第三方整合 遊樂場 報表 設定報表 指標和維度清單 產生報表 庫存 應用程式和廣告單元 中介服務 中介服務管理 廣告來源 Adapters 廣告單元對應 中介服務群組 中介服務 A/B 實驗 首頁 產品 AdMob API 指南 開始使用 AdMob API 透過集合功能整理內容 你可以依據偏好儲存及分類內容。 重要事項： 新使用者角色和權限會影響 AdMob API 傳回的資料。 瞭解詳情 本指南適用於想使用 AdMob API，以程式輔助方式取得及管理 AdMob 帳戶資料的開發人員。 所有 Google AdMob API 呼叫都必須透過 OAuth2 授權，應用程式才能代表使用者與網路服務互動。OAuth2 可讓 AdMob API 用戶端應用程式存取使用者的 AdMob 帳戶，不必處理或儲存使用者的使用者名稱或密碼。如要瞭解授權總覽，請參閱 授權 。 請按照下列步驟產生 OAuth2 憑證，並提出第一項要求。 必要條件 Google 帳戶 。 Google AdMob 帳戶 。 熟悉 REST 基本概念 ，以及 使用 OAuth 2.0 授權要求 。 判斷驗證類型 請參閱下表，瞭解哪種 驗證類型 最適合您的應用程式： 選擇 OAuth2 驗證類型 適用條件 電腦版應用程式 您使用單一頂層管理員帳戶管理所有 AdMob API 帳戶。 您是初次使用，或想透過最簡單的設定快速上手。 您的應用程式只會驗證來自一部電腦的 Google AdMob 使用者。 網頁應用程式 您想以可授予應用程式權限的使用者身分進行驗證，以便存取他們的 AdMob API 帳戶資料。 您想輕鬆產生多個授權憑證，以便管理第三方帳戶等。 您的應用程式需要回呼網址，但桌面應用程式流程不支援回呼網址。 重點： 即使您開發的應用程式要在伺服器上執行，仍可選擇桌面應用程式流程。差異在於 OAuth 授權是在本機或遠端完成。桌面流程需要在本機完成授權，而網路流程則可在 Google 的授權伺服器上完成授權。 建立專案 如要開始使用 AdMob API，請先在 Google API 控制台中建立或選取專案，然後使用 設定工具 啟用 API。這項工具會逐步引導您完成該程序，並自動啟用 AdMob API。 為現有專案啟用 API 如果您已有專案，且偏好手動啟用 AdMob API，請按照下列步驟操作。 如要為專案啟用 API，請按照下列步驟操作： Open the API Library 。 Google API Console If prompted, select a project, or create a new one. 「API 程式庫」 API Library 會列出所有可用的 API，並按照產品系列及熱門程度分組。 如果清單裡找不到您想啟用的 API，請使用搜尋功能，或點選所屬產品系列的「查看全部」 。 選取要啟用的 API，然後按一下「Enable」 按鈕。 If prompted, enable billing. If prompted, read and accept the API's Terms of Service. 建立 OAuth2 憑證 請按照下列操作說明，建立 OAuth 2.0 用戶端 ID，以便搭配 已安裝應用程式流程 使用。 Go to the Clients page . 依序點選「建立憑證」>「OAuth 用戶端 ID」 。 如果您先前未設定這個專案的 OAuth 同意畫面，系統會引導您進行設定。點選「設定同意畫面」 。您可以透過多種方式設定同意畫面，以使用 OAuth 2.0 用戶端 ID。 將使用者類型設為「外部」 ，發布狀態設為「已發布」 。 或者，將使用者類型設為「外部」 ，發布狀態設為「測試」 ，然後選取「新增使用者」 ，新增「測試使用者」 ，讓他們有權使用您的 OAuth 2.0 用戶端 ID。 進一步瞭解如何 設定 OAuth 同意畫面 。 將應用程式類型設為「Desktop app」(桌面應用程式) 或「Web Application」(網頁應用程式) ，為應用程式命名，然後按一下「Create」(建立) 。 完成後，系統會顯示 OAuth 2.0 用戶端 ID 和用戶端密鑰，您可以下載 JSON 格式並儲存，以供日後使用。 提出要求 AdMob API 是以 HTTP 和 JSON 做為建構基礎，因此所有標準 HTTP 用戶端都可以向 AdMob API 傳送要求並剖析回應。不過， Google API 用戶端程式庫 不但提供更出色的語言整合功能，安全性也更高，還能發出授權要求。用戶端程式庫支援多種程式語言，只要善加利用，您就不必再手動設定 HTTP 要求及剖析回應。 注意： 首次啟用 OAuth 流程時，系統會要求您提供 AdMob 發布商 ID，並在瀏覽器中接受授權提示。接受邀請前，請先確認您登入的 Google 帳戶有權存取 AdMob 帳戶。應用程式隨後就能代表目前登入的帳戶存取資料。 建立 OAuth 2.0 憑證 後，即可開始使用 AdMob API。如要透過 OAuth 2.0 要求存取權，您的應用程式也需要範圍資訊： 範圍 意義 https://www.googleapis.com/auth/admob.readonly 查看所有 AdMob 資料。這些 AdMob 資料可能包含您的帳戶資訊、廣告空間和中介服務設定、報表以及其他資料，但不含付款或廣告活動詳細資料等這類機密資料。 https://www.googleapis.com/auth/admob.report 查看廣告成效和收益報表。查看發布商 ID、時區和預設貨幣代碼。 使用 Java 、 PHP 、 Python 或 curl 中的範例，發出第一個要求來產生報表。 撤銷共用權杖 您可以使用下列兩種方式撤銷共用權杖： 前往 Google 帳戶權限頁面 ，然後撤銷相關專案的存取權。 或者，您也可以使用 Google Identity API 撤銷網頁應用程式權杖。 除非另有註明，否則本頁面中的內容是採用 創用 CC 姓名標示 4.0 授權 ，程式碼範例則為 阿帕契 2.0 授權 。詳情請參閱《 Google Developers 網站政策 》。Java 是 Oracle 和/或其關聯企業的註冊商標。 上次更新時間：2025-08-31 (世界標準時間)。 [[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["缺少我需要的資訊","missingTheInformationINeed","thumb-down"],["過於複雜/步驟過多","tooComplicatedTooManySteps","thumb-down"],["過時","outOfDate","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["示例/程式碼問題","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-08-31 (世界標準時間)。"],[],["To use the AdMob API, developers must authorize requests via OAuth2. Key actions include creating a project in the Google API Console and enabling the AdMob API. Developers then generate OAuth2 credentials, choosing between desktop or web app authentication types. The OAuth consent screen must be configured. Finally, with created credentials and specifying the scope (`admob.readonly` or `admob.report`), developers can use HTTP or Google API client libraries to make their first API request and start retrieving AdMob data. Shared tokens can be revoked.\n"]] 產品資訊 用量限制 定價 服務條款 計劃 Google Developer Program Google Developer Groups Google Developer Experts Accelerators Google Cloud & NVIDIA 開發人員控制台 Google API Console Google Cloud Platform Console Google Play 管理中心 Firebase Console Actions on Google Console Cast SDK Developer Console Chrome Web Store Dashboard Google Home Developer Console Android Chrome Firebase Google Cloud Platform Google AI 所有產品 條款 隱私權 Manage cookies English Deutsch Español Español – América Latina Français Indonesia Italiano Polski Português – Brasil Tiếng Việt Türkçe Русский עברית العربيّة فارسی हिंदी বাংলা ภาษาไทย 中文 – 简体 中文 – 繁體 日本語 한국어 | 2026-01-13T09:30:11 |
https://developers.google.com/admob/api/reference/rest?hl=ko | AdMob API | Google for Developers 기본 콘텐츠로 건너뛰기 AdMob API / English Deutsch Español Español – América Latina Français Indonesia Italiano Polski Português – Brasil Tiếng Việt Türkçe Русский עברית العربيّة فارسی हिंदी বাংলা ภาษาไทย 中文 – 简体 中文 – 繁體 日本語 한국어 로그인 AdMob 가이드 참조 라이브러리 및 예제 지원 AdMob API AdMob 가이드 참조 라이브러리 및 예제 지원 출시 노트 AdMob API v1 REST 리소스 accounts 개요 get list accounts.adUnit 개요 list accounts.apps 개요 list accounts.MediationReport 개요 generate accounts.networkReport 개요 generate 유형 DateRange LocalizationSettings 보고서 바닥글 보고서 헤더 ReportRow SortOrder StringList v1beta REST 리소스 accounts 개요 get list accounts.adSources 개요 list accounts.adSources.adapters 개요 list accounts.adUnitMappings 개요 batchCreate accounts.adUnit 개요 create list accounts.adUnits.adUnitMappings 개요 create list accounts.apps 개요 create list accounts.campaignReport 클래스의 정적 변수 개요 generate accounts.MediationGroups 개요 create list patch accounts.미디에이션그룹.미디에이션Ab실험 개요 create 중지 accounts.MediationReport 개요 generate accounts.networkReport 개요 generate 유형 DateRange LocalizationSettings 미디에이션 그룹 라인 보고서 바닥글 보고서 헤더 ReportRow SortOrder StringList API 사전 광고 소스 Adapters 홈 제품 AdMob API 참조 AdMob API 컬렉션을 사용해 정리하기 내 환경설정을 기준으로 콘텐츠를 저장하고 분류하세요. AdMob API를 사용하면 게시자가 프로그래매틱 방식으로 AdMob 계정에 대한 정보를 얻을 수 있습니다. REST 리소스: v1beta.accounts REST 리소스: v1beta.accounts.adSources REST 리소스: v1beta.accounts.adSources.adapters REST 리소스: v1beta.accounts.adUnitMappings REST 리소스: v1beta.accounts.adUnits REST 리소스: v1beta.accounts.adUnits.adUnitMappings REST 리소스: v1beta.accounts.apps REST 리소스: v1beta.accounts.campaignReport REST 리소스: v1beta.accounts.mediationGroups REST 리소스: v1beta.accounts.mediationGroups.mediationAbExperiments REST 리소스: v1beta.accounts.mediationReport REST 리소스: v1beta.accounts.networkReport REST 리소스: v1.accounts REST 리소스: v1.accounts.adUnits REST 리소스: v1.accounts.apps REST 리소스: v1.accounts.mediationReport REST 리소스: v1.accounts.networkReport 서비스: admob.googleapis.com 이 서비스를 호출하려면 Google에서 제공하는 클라이언트 라이브러리 를 사용하는 것이 좋습니다. 애플리케이션에서 자체 라이브러리를 사용하여 이 서비스를 호출해야 한다면 API 요청을 실행할 때 다음 정보를 사용해야 합니다. 검색 문서 검색 문서 는 머신에서 읽을 수 있는 사양이며 REST API를 설명하고 사용하는 데 참조할 수 있습니다. 또한 클라이언트 라이브러리, IDE 플러그인, 기타 Google API와 상호작용하는 도구를 빌드하는 데 사용됩니다. 하나의 서비스는 여러 개의 검색 문서를 제공할 수 있습니다. 이 서비스는 다음 검색 문서를 제공합니다. https://admob.googleapis.com/$discovery/rest?version=v1 https://admob.googleapis.com/$discovery/rest?version=v1beta 서비스 엔드포인트 서비스 엔드포인트 는 API 서비스의 네트워크 주소를 지정하는 기준 URL입니다. 하나의 서비스는 여러 서비스 엔드포인트를 포함할 수 있습니다. 이 서비스에는 다음 서비스 엔드포인트가 포함되고, 그 아래의 모든 URI가 이 서비스 엔드포인트와 관련됩니다. https://admob.googleapis.com REST 리소스: v1beta.accounts 메서드 get GET /v1beta/{name=accounts/*} 지정된 AdMob 게시자 계정에 대한 정보를 가져옵니다. list GET /v1beta/accounts 가장 최근에 AdMob UI에서 로그인한 AdMob 게시자 계정을 나열합니다. REST 리소스: v1beta.accounts.adSources 메서드 list GET /v1beta/{parent=accounts/*}/adSources 광고 소스를 나열합니다. REST 리소스: v1beta.accounts.adSources.adapters 메서드 list GET /v1beta/{parent=accounts/*/adSources/*}/adapters 광고 소스의 어댑터를 나열합니다. REST 리소스: v1beta.accounts.adUnitMappings 메서드 batchCreate POST /v1beta/{parent=accounts/*}/adUnitMappings:batchCreate 특정 AdMob 계정에서 광고 단위 매핑을 일괄 생성합니다. REST 리소스: v1beta.accounts.adUnits 메서드 create POST /v1beta/{parent=accounts/*}/adUnits 지정된 AdMob 계정에 광고 단위를 만듭니다. list GET /v1beta/{parent=accounts/*}/adUnits 지정된 AdMob 계정 아래에 광고 단위를 나열합니다. REST 리소스: v1beta.accounts.adUnits.adUnitMappings 메서드 create POST /v1beta/{parent=accounts/*/adUnits/*}/adUnitMappings 특정 AdMob 계정 및 광고 단위 아래에 광고 단위 매핑을 만듭니다. list GET /v1beta/{parent=accounts/*/adUnits/*}/adUnitMappings 지정된 AdMob 계정 및 광고 단위 아래에 광고 단위 매핑을 나열합니다. REST 리소스: v1beta.accounts.apps 메서드 create POST /v1beta/{parent=accounts/*}/apps 지정된 AdMob 계정에 앱을 만듭니다. list GET /v1beta/{parent=accounts/*}/apps 지정된 AdMob 계정에 있는 앱을 나열합니다. REST 리소스: v1beta.accounts.campaignReport 메서드 generate POST /v1beta/{parent=accounts/*}/campaignReport:generate 제공된 사양을 기반으로 캠페인 보고서를 생성합니다. REST 리소스: v1beta.accounts.mediationGroups 메서드 create POST /v1beta/{parent=accounts/*}/mediationGroups 특정 AdMob 계정에서 미디에이션 그룹을 만듭니다. list GET /v1beta/{parent=accounts/*}/mediationGroups 지정된 AdMob 계정 아래에 미디에이션 그룹을 나열합니다. patch PATCH /v1beta/{mediationGroup.name=accounts/*/mediationGroups/*} 지정된 AdMob 계정에서 지정된 미디에이션 그룹을 업데이트합니다. REST 리소스: v1beta.accounts.mediationGroups.mediationAbExperiments 메서드 create POST /v1beta/{parent=accounts/*/mediationGroups/*}/mediationAbExperiments 지정된 AdMob 계정 및 미디에이션 그룹을 위한 A/B 테스트 실험을 만듭니다. stop POST /v1beta/{name=accounts/*/mediationGroups/*/mediationAbExperiments}:stop 미디에이션 A/B 실험을 중지하고 대안을 선택합니다. REST 리소스: v1beta.accounts.mediationReport 메서드 generate POST /v1beta/{parent=accounts/*}/mediationReport:generate 제공된 보고서 사양을 기반으로 AdMob 미디에이션 보고서를 생성합니다. REST 리소스: v1beta.accounts.networkReport 메서드 generate POST /v1beta/{parent=accounts/*}/networkReport:generate 제공된 보고서 사양을 기반으로 AdMob 네트워크 보고서를 생성합니다. REST 리소스: v1.accounts 메서드 get GET /v1/{name=accounts/*} 지정된 AdMob 게시자 계정에 대한 정보를 가져옵니다. list GET /v1/accounts 가장 최근에 AdMob UI에서 로그인한 AdMob 게시자 계정을 나열합니다. REST 리소스: v1.accounts.adUnits 메서드 list GET /v1/{parent=accounts/*}/adUnits 지정된 AdMob 계정 아래에 광고 단위를 나열합니다. REST 리소스: v1.accounts.apps 메서드 list GET /v1/{parent=accounts/*}/apps 지정된 AdMob 계정에 있는 앱을 나열합니다. REST 리소스: v1.accounts.mediationReport 메서드 generate POST /v1/{parent=accounts/*}/mediationReport:generate 제공된 보고서 사양을 기반으로 AdMob 미디에이션 보고서를 생성합니다. REST 리소스: v1.accounts.networkReport 메서드 generate POST /v1/{parent=accounts/*}/networkReport:generate 제공된 보고서 사양을 기반으로 AdMob 네트워크 보고서를 생성합니다. 달리 명시되지 않는 한 이 페이지의 콘텐츠에는 Creative Commons Attribution 4.0 라이선스 에 따라 라이선스가 부여되며, 코드 샘플에는 Apache 2.0 라이선스 에 따라 라이선스가 부여됩니다. 자세한 내용은 Google Developers 사이트 정책 을 참조하세요. 자바는 Oracle 및/또는 Oracle 계열사의 등록 상표입니다. 최종 업데이트: 2025-08-21(UTC) [[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["필요한 정보가 없음","missingTheInformationINeed","thumb-down"],["너무 복잡함/단계 수가 너무 많음","tooComplicatedTooManySteps","thumb-down"],["오래됨","outOfDate","thumb-down"],["번역 문제","translationIssue","thumb-down"],["샘플/코드 문제","samplesCodeIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-08-21(UTC)"],[],["The AdMob API enables programmatic access to AdMob account information through REST resources. Key actions include: retrieving account details; listing ad sources, adapters, ad units, apps, and mediation groups; and creating ad units, apps, and mappings. It allows for batch creation of ad unit mappings, creating and stopping mediation A/B experiments, updating mediation groups, and generating campaign, mediation, and network reports. Two versions of the API are available, v1 and v1beta.\n"]] 제품 정보 사용량 한도 가격 책정 서비스 약관 프로그램 Google Developer Program Google Developer Groups Google Developer Experts Accelerators Google Cloud & NVIDIA 개발자 콘솔 Google API Console Google Cloud Platform Console Google Play Console Firebase Console Actions on Google Console Cast SDK Developer Console Chrome Web Store Dashboard Google Home Developer Console Android Chrome Firebase Google Cloud Platform Google AI 모든 제품 약관 개인정보처리방침 Manage cookies English Deutsch Español Español – América Latina Français Indonesia Italiano Polski Português – Brasil Tiếng Việt Türkçe Русский עברית العربيّة فارسی हिंदी বাংলা ภาษาไทย 中文 – 简体 中文 – 繁體 日本語 한국어 | 2026-01-13T09:30:11 |
https://developers.cloudflare.com/ai-gateway/usage/providers/anthropic/ | Anthropic · Cloudflare AI Gateway docs Skip to content Cloudflare Docs Search Docs Directory APIs SDKs Help Log in Select theme Dark Light Auto AI Gateway No results found. Try a different search term, or use our global search . Overview Getting started Using AI Gateway Unified API (OpenAI compat) Provider Native Workers AI Amazon Bedrock Anthropic Azure OpenAI Baseten Cartesia Cerebras Cohere Deepgram DeepSeek ElevenLabs Fal AI Google AI Studio Google Vertex AI Groq HuggingFace Ideogram Mistral AI OpenAI OpenRouter Parallel Perplexity Replicate xAI WebSockets API Beta Overview Realtime WebSockets API Non-realtime WebSockets API Features Overview Unified Billing Caching Rate limiting Dynamic routing Beta Overview Using a dynamic route JSON Configuration Data Loss Prevention (DLP) Beta Overview Set up Data Loss Prevention (DLP) Guardrails Beta Overview Set up Guardrails Supported model types Usage considerations Configuration BYOK (Store Keys) Beta Custom costs Custom Providers Beta Manage gateways Request handling Authenticated Gateway Observability Costs Custom metadata Analytics Logging Overview Workers Logpush Integrations Vercel AI SDK Agents ↗ AI Gateway Binding Methods Workers AI Tutorials Platform Overview Limits Pricing Audit logs Changelog Header Glossary REST API reference ↗ API MCP server ↗ MCP AI Assistant ↗ Architectures LLM resources llms.txt prompt.txt AI Gateway llms-full.txt Developer Platform llms-full.txt GitHub X.com YouTube Select theme Dark Light Auto On this page Overview Endpoint Examples cURL Anthropic SDK OpenAI-Compatible Endpoint On this page Overview Endpoint Examples cURL Anthropic SDK OpenAI-Compatible Endpoint Was this helpful? Edit Issue Directory … AI Gateway Using AI Gateway Provider Native Anthropic Copy page Anthropic Anthropic ↗ helps build reliable, interpretable, and steerable AI systems. Endpoint Base URL https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/anthropic Examples cURL With API Key in Request With Authenticated Gateway Unauthenticated Gateway Terminal window curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/anthropic/v1/messages \ --header 'x-api-key: {anthropic_api_key}' \ --header 'cf-aig-authorization: Bearer {CF_AIG_TOKEN}' \ --header 'anthropic-version: 2023-06-01' \ --header 'Content-Type: application/json' \ --data '{ "model": "claude-sonnet-4-5", "max_tokens": 1024, "messages": [ {"role": "user", "content": "What is Cloudflare?"} ] }' Terminal window curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/anthropic/v1/messages \ --header 'x-api-key: {anthropic_api_key}' \ --header 'anthropic-version: 2023-06-01' \ --header 'Content-Type: application/json' \ --data '{ "model": "claude-sonnet-4-5", "max_tokens": 1024, "messages": [ {"role": "user", "content": "What is Cloudflare?"} ] }' With Stored Keys (BYOK) / Unified Billing Terminal window curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/anthropic/v1/messages \ --header 'cf-aig-authorization: Bearer {CF_AIG_TOKEN}' \ --header 'anthropic-version: 2023-06-01' \ --header 'Content-Type: application/json' \ --data '{ "model": "claude-sonnet-4-5", "max_tokens": 1024, "messages": [ {"role": "user", "content": "What is Cloudflare?"} ] }' Anthropic SDK With Key in Request With Authenticated Gateway Unauthenticated Gateway import Anthropic from "@anthropic-ai/sdk" ; const baseURL = `https://gateway.ai.cloudflare.com/v1/{accountId}/{gatewayId}/anthropic` ; const anthropic = new Anthropic ( { apiKey : "{ANTHROPIC_API_KEY}" , baseURL , defaultHeaders : { Authorization : `Bearer {cf_api_token}` , }, } ) ; const message = await anthropic . messages . create ( { model : "claude-sonnet-4-5" , messages : [ { role : "user" , content : "What is Cloudflare?" } ] , max_tokens : 1024 , } ) ; import Anthropic from "@anthropic-ai/sdk" ; const baseURL = `https://gateway.ai.cloudflare.com/v1/{accountId}/{gatewayId}/anthropic` ; const anthropic = new Anthropic ( { apiKey : "{ANTHROPIC_API_KEY}" , baseURL , } ) ; const message = await anthropic . messages . create ( { model : "claude-sonnet-4-5" , messages : [ { role : "user" , content : "What is Cloudflare?" } ] , max_tokens : 1024 , } ) ; With Stored Keys (BYOK) / Unified Billing import Anthropic from "@anthropic-ai/sdk" ; const baseURL = `https://gateway.ai.cloudflare.com/v1/{accountId}/{gatewayId}/anthropic` ; const anthropic = new Anthropic ( { baseURL , defaultHeaders : { Authorization : `Bearer {cf_api_token}` , }, } ) ; const message = await anthropic . messages . create ( { model : "claude-sonnet-4-5" , messages : [ { role : "user" , content : "What is Cloudflare?" } ] , max_tokens : 1024 , } ) ; OpenAI-Compatible Endpoint You can also use the OpenAI-compatible endpoint ( /ai-gateway/usage/chat-completion/ ) to access Anthropic models using the OpenAI API schema. To do so, send your requests to: https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions Specify: { " model " : "anthropic/{model}" } Was this helpful? Edit page Last updated: Nov 25, 2025 Previous Amazon Bedrock Next Azure OpenAI Resources API New to Cloudflare? Directory Sponsorships Open Source Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Speed Test Is BGP Safe Yet? RPKI Toolkit Certificate Transparency Community X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings | 2026-01-13T09:30:11 |
https://developers.google.com/admob/api/v1/app-ad-units | Retrieve ad units and app details | AdMob API | Google for Developers Skip to main content AdMob API / English Deutsch Español Español – América Latina Français Indonesia Italiano Polski Português – Brasil Tiếng Việt Türkçe Русский עברית العربيّة فارسی हिंदी বাংলা ภาษาไทย 中文 – 简体 中文 – 繁體 日本語 한국어 Sign in AdMob Guides Reference Libraries & Examples Support AdMob API AdMob Guides Reference Libraries & Examples Support Get started The basics Prerequisites Common errors Authorization Overview Setup Third-party integration Playground Reports Set up your report Metrics and dimensions list Generate reports Inventory Apps and ad units Mediation Mediation management Ad sources Adapters Ad unit mappings Mediation groups Mediation A/B experiment Home Products AdMob API Guides Retrieve ad units and app details Stay organized with collections Save and categorize content based on your preferences. Page Summary outlined_flag This guide explains how to programmatically view your inventory using the AdMob API, including apps and ad units. Prerequisites include creating a project and generating credentials for the AdMob API. You can view app details such as ID, store ID, and platform, and both published and unpublished apps can be added to your AdMob account with details automatically updated when linked to app stores. The guide provides examples of how to list apps and ad units using Java, PHP, Python client libraries, and curl commands. This guide shows you how to programmatically view your inventory including items such as your apps and ad units. Prerequisites Important: New user roles and permissions will affect data returned by the AdMob API. Learn more Create a project Generate credentials App details You can view your app's details and settings programmatically through the AdMob API, such as app ID, app store ID, and platform. For additional information, see accounts.apps.list . Key Point: Published and unpublished apps can currently be added to your AdMob account. If you link your app to the Google Play store or the Apple App Store, the app details are automatically updated and available in the AdMob API. Ad Units An ad unit is the set of ads displayed as a result of one piece of the AdMob ad code. For additional information, see accounts.adUnits.list . Make a request There are several ways to make your first request: Java client library Requests using Java client library Load the client secrets file and generate authorization credentials. The first time you perform this step you'll be asked to accept an authorization prompt in your browser. Before accepting, make sure you're signed in with a Google Account that has access to the AdMob API. Your application will be authorized to access data on behalf of whichever account is currently logged in. import com.google.api.client.auth.oauth2.Credential ; import com.google.api.client.extensions.java6.auth.oauth2.AuthorizationCodeInstalledApp ; import com.google.api.client.extensions.jetty.auth.oauth2.LocalServerReceiver ; import com.google.api.client.googleapis.auth.oauth2.GoogleAuthorizationCodeFlow ; import com.google.api.client.googleapis.auth.oauth2.GoogleClientSecrets ; import com.google.api.client.googleapis.auth.oauth2.GoogleCredential ; import com.google.api.client.googleapis.util.Utils ; import com.google.api.client.http.HttpTransport ; import com.google.api.client.json.JsonFactory ; import com.google.api.client.util.store.DataStoreFactory ; import com.google.api.client.util.store.FileDataStoreFactory ; import com.google.api.services.admob.v1.AdMob ; ... /** Directory to store user credentials. */ private static final java . io . File DATA_STORE_DIR = new java . io . File ( System . getProperty ( "user.home" ), ".store/admobapi_sample" ); private static final HttpTransport HTTP_TRANSPORT = Utils . getDefaultTransport (); private static final JsonFactory JSON_FACTORY = Utils . getDefaultJsonFactory (); // Load client secrets JSON file. String pathToClientSecretsFile = "INSERT_PATH_TO_CLIENT_SECRETS" ; GoogleClientSecrets clientSecrets = GoogleClientSecrets . load ( JSON_FACTORY , Files . newBufferedReader ( Paths . get ( pathToClientSecretsFile ), UTF_8 ) ); // Set up the authorization code flow. // // Note: providing a DataStoreFactory allows auth credentials to be cached, // so they survive multiple runs of the program. This avoids prompting the // user for authorization every time the access token expires, by remembering // the refresh token. ImmutableSet<String> READONLY_SCOPE = ImmutableSet . of ( "https://www.googleapis.com/auth/admob.readonly" ); GoogleAuthorizationCodeFlow flow = new GoogleAuthorizationCodeFlow . Builder ( HTTP_TRANSPORT , JSON_FACTORY , clientSecrets , READONLY_SCOPE ) . setDataStoreFactory ( dataStoreFactory ) . build (); // Build installed application credential. Credential credential = new AuthorizationCodeInstalledApp ( flow , new LocalServerReceiver ()). authorize ( "user" ); Create an authorized AdMob client. // Create an AdMob client instance. AdMob admob = new AdMob . Builder ( HTTP_TRANSPORT , JSON_FACTORY , credential ) . setApplicationName ( "admobapi-java-samples" ) . build (); List apps. ListAppsResponse response ; String nextPageToken = null ; do { // Create and execute the apps list request. response = adMob . accounts () . apps () . list ( ACCOUNT_NAME ) . setPageSize ( PAGE_SIZE ) . setPageToken ( nextPageToken ) . execute (); // Display apps. List<App> apps = response . getApps (); for ( App app : apps ) { AppLinkedAppInfo linkedAppInfo = app . getLinkedAppInfo (); System . out . printf ( "App Name: %s, " + "App ID: %s, " + "App Platform: %s, " + "App Store ID: %s, " + "App Store Display Name: %s, " + "App Manual Info: %s%n" , app . getName (), app . getAppId (), app . getPlatform (), linkedAppInfo == null ? "" : linkedAppInfo . getAppStoreId (), linkedAppInfo == null ? "" : linkedAppInfo . getDisplayName (), app . getManualAppInfo (). getDisplayName ()); } // Update the next page token. nextPageToken = response . getNextPageToken (); } while ( nextPageToken != null && ! nextPageToken . isEmpty ()); List ad units. ListAdUnitsResponse response ; String nextPageToken = null ; do { // Create and execute the ad units list request. response = adMob . accounts () . adUnits () . list ( ACCOUNT_NAME ) . setPageSize ( PAGE_SIZE ) . setPageToken ( nextPageToken ) . execute (); // Display ad units. List<AdUnit> adUnits = response . getAdUnits (); for ( AdUnit adUnit : adUnits ) { System . out . printf ( "Ad Unit Display Name: %s, " + "Ad Unit Name: %s, " + "Ad Unit ID: %s, " + "Ad Unit Format: %s, " + "Ad Unit App ID: %s, " + "Ad Unit Ad Types: %s%n" , adUnit . getDisplayName (), adUnit . getName (), adUnit . getAdUnitId (), adUnit . getAdFormat (), adUnit . getAppId (), adUnit . getAdTypes ()); } // Update the next page token. nextPageToken = response . getNextPageToken (); } while ( nextPageToken != null && ! nextPageToken . isEmpty ()); PHP client library Requests using PHP client library Load the client secrets file and create an authorized AdMob client. The first time you perform this step you'll be asked to accept an authorization prompt in your browser. Before accepting, make sure you're signed in with a Google Account that has access to the AdMob API. Your application will be authorized to access data on behalf of whichever account is currently logged in. // Create an AdMob Client. $client = new Google_Client(); $client->addScope('https://www.googleapis.com/auth/admob.readonly'); $client->setApplicationName('AdMob API PHP Quickstart'); $client->setAccessType('offline'); // Be sure to replace the contents of client_secrets.json with your developer // credentials. $client->setAuthConfig('client_secrets.json'); // Create the URL for the authorization prompt. $authUrl = $client->createAuthUrl(); // Once the authorization prompt has been accepted, exchange the // authorization code for an access and refresh token. $client->authenticate($_GET['code']); $client->getAccessToken(); Create an AdMob service object. // Create an AdMob service object on which to run the requests. $service = new Google_Service_AdMob($client); List apps. // Create the page token variable. $pageToken = ''; $optParams['pageSize'] = $maxPageSize; do { $optParams['pageToken'] = $pageToken; // Get list of apps. $response = $service->accounts_apps->listAccountsApps($accountName, $optParams); $apps = $response->getApps(); // Print list of apps. if (!empty($apps)) { foreach ($apps as $app) { if(!empty($app->getLinkedAppInfo)){ $appStoreId = $app->getLinkedAppInfo()->getAppStoreId(); $displayName = $app->getLinkedAppInfo()->getDisplayName(); } else { $appStoreId = ''; $displayName = ''; } printf( "App Name: '%s' \n" ."App ID: '%s' \n" ."App Platform: '%s' \n" ."App Store ID: '%s' \n" ."App Store Display Name: '%s' \n" ."App Display Name: '%s' \n\n", $app->getName(), $app->getAppId(), $app->getPlatform(), $appStoreId, $displayName, $app->getManualAppInfo()->getDisplayName(), ); } } $pageToken = $response->getNextPageToken(); } while ($pageToken); List ad units. // Create the page token variable. $pageToken = ''; $optParams['pageSize'] = $maxPageSize; do { $optParams['pageToken'] = $pageToken; // Get list of ad units. $response = $service->accounts_adUnits->listAccountsAdUnits($accountName, $optParams); $adUnits = $response->adUnits; // Print list of ad units. if (!empty($adUnits)) { foreach ($adUnits as $adUnit) { printf( "Ad Unit Display Name: '%s' \n" ."Ad Unit Name: '%s' \n" ."Ad Unit ID: '%s' \n" ."Ad Unit Format: '%s' \n" ."Ad Unit App ID: '%s' \n" ."Ad Unit Ad Types: '%s' \n\n", $adUnit->getDisplayName(), $adUnit->getName(), $adUnit->getAdUnitId(), $adUnit->getAdFormat(), $adUnit->getAppId(), json_encode($adUnit->getAdTypes()), ); } } $pageToken = $response->getNextPageToken(); } while ($pageToken); Python client library Requests using Python client library Load the client secrets file and generate authorization credentials. The first time you perform this step you'll be asked to accept an authorization prompt in your browser. Before accepting, make sure you're signed in with a Google Account that has access to the AdMob API. Your application will be authorized to access data on behalf of whichever account is currently logged in. import os from google_auth_oauthlib.flow import Flow from googleapiclient.discovery import build from google.auth.transport.requests import Request ... # Authenticate using the client_secrets file. client_secrets = os . path . join ( os . path . dirname ( __file__ ), 'client_secrets.json' ) flow = Flow . from_client_secrets_file ( client_secrets , scopes = [ 'https://www.googleapis.com/auth/admob.readonly' ], redirect_uri = 'urn:ietf:wg:oauth:2.0:oob' ) # Redirect the user to auth_url on your platform. auth_url , _ = flow . authorization_url () print ( 'Please go to this URL: {} \n ' . format ( auth_url )) # The user will get an authorization code. This code is used to get the # access token. code = input ( 'Enter the authorization code: ' ) flow . fetch_token ( code = code ) credentials = flow . credentials Create an AdMob service object. // Create an AdMob service object on which to run the requests . admob = build ( 'admob' , 'v1' , credentials = credentials ) List apps. next_page_token = '' while True : # Execute the request. response = service . accounts () . apps () . list ( pageSize = PAGE_SIZE , pageToken = next_page_token , parent = 'accounts/ {} ' . format ( publisher_id )) . execute () # Check if the response is empty. if not response : break # Print the result. apps = response [ 'apps' ] for app in apps : print ( 'App ID: ' + app [ 'appId' ]) print ( 'App Platform: ' + app [ 'platform' ]) print ( 'App Name: ' + app [ 'name' ]) if 'linkedAppInfo' in app : linked_app_info = app [ 'linkedAppInfo' ] print ( 'App Store ID: ' + linked_app_info [ 'appStoreId' ]) print ( 'App Store Display Name: ' + linked_app_info [ 'displayName' ]) if 'manualAppInfo' in app : manual_app_info = app [ 'manualAppInfo' ] print ( 'App Manual Info: ' + manual_app_info [ 'displayName' ]) if 'nextPageToken' not in response : break # Update the next page token. next_page_token = response [ 'nextPageToken' ] List ad units. next_page_token = '' while True : # Execute the request. response = service . accounts () . adUnits () . list ( pageSize = PAGE_SIZE , pageToken = next_page_token , parent = 'accounts/ {} ' . format ( publisher_id )) . execute () # Check if the response is empty. if not response : break # Print the result. ad_units = response [ 'adUnits' ] for ad_unit in ad_units : print ( 'Ad Unit Display Name: ' + ad_unit [ 'displayName' ]) print ( 'Ad Unit Name: ' + ad_unit [ 'name' ]) print ( 'Ad Unit ID: ' + ad_unit [ 'adUnitId' ]) print ( 'Ad Unit Format: ' + ad_unit [ 'adFormat' ]) print ( 'Ad Unit App ID: ' + ad_unit [ 'appId' ]) print ( 'Ad Unit Format: ' + ', ' . join ( ad_unit [ 'adTypes' ])) if 'nextPageToken' not in response : break # Update the next page token. next_page_token = response [ 'nextPageToken' ] curl (command line) Requests using curl Load the client secrets file and generate authorization credentials. The first time you perform this step you'll be asked to accept an authorization prompt in your browser. Before accepting, make sure you're signed in with a Google Account that has access to the AdMob API. Your application will be authorized to access data on behalf of whichever account is currently logged in. For authentication and authorization, we recommend using oauth2l , a simple command-line tool for working with Google OAuth 2.0. Install oauth2l and run the command below, replacing path_to_credentials_json with a path to a credentials.json file that you download when registering your cloud application. For the first run, the command walks you through the OAuth 2.0 authorization flow. Subsequent runs refresh the token automatically. oauth2l header --json path_to_credentials_json \ --scope admob.readonly List apps. curl -X GET https://admob.googleapis.com/v1/accounts/ pub-XXXXXXXXXXXXXXXX /apps \ -H "$(oauth2l header --json path_to_credentials_json \ --scope admob.readonly)" Sample response: { " app ": [ { " name ": "accounts/pub-XXXXXXXXXXXXXXXX/apps/XXXXXXXXXX", " appId ": "ca-app-pub-XXXXXXXXXXXXXXXX~XXXXXXXXXX", " platform ": "ANDROID", " manualAppInfo ": { "displayName": "Example App" }, " linkedAppInfo ": { "appStoreId": "com.example.myApp", "displayName": "Example App", } } ] } List ad units. curl -X GET https://admob.googleapis.com/v1/accounts/ pub-XXXXXXXXXXXXXXXX /adUnits \ -H "$(oauth2l header --json path_to_credentials_json \ --scope admob.readonly)" Sample response: { " adUnit ": [ { " name ": "accounts/pub-XXXXXXXXXXXXXXXX/adUnits/XXXXXXXXXX", " adUnitId ": "ca-app-pub-XXXXXXXXXXXXXXXX/XXXXXXXXXX", " appId ": "ca-app-pub-XXXXXXXXXXXXXXXX~XXXXXXXXXX", " displayName ": "AdMob Rewarded", " adFormat ": "REWARDED", " adTypes ": ["RICH_MEDIA", "VIDEO"], } ] } Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License , and code samples are licensed under the Apache 2.0 License . For details, see the Google Developers Site Policies . Java is a registered trademark of Oracle and/or its affiliates. Last updated 2025-08-28 UTC. [[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-28 UTC."],[],["This guide details how to use the AdMob API to programmatically access inventory data. First, create a project and generate credentials. Then, using client libraries (Java, PHP, Python) or `curl`, load client secrets, create an authorized AdMob client, and make requests to list apps and ad units. Apps can be viewed with details such as ID, store ID, and platform; ad units include information like display name, format, and associated ad types. Each client offers a similar process for fetching data.\n"]] Product info Usage limits Pricing Terms of Service Programs Google Developer Program Google Developer Groups Google Developer Experts Accelerators Google Cloud & NVIDIA Developer consoles Google API Console Google Cloud Platform Console Google Play Console Firebase Console Actions on Google Console Cast SDK Developer Console Chrome Web Store Dashboard Google Home Developer Console Android Chrome Firebase Google Cloud Platform Google AI All products Terms Privacy Manage cookies English Deutsch Español Español – América Latina Français Indonesia Italiano Polski Português – Brasil Tiếng Việt Türkçe Русский עברית العربيّة فارسی हिंदी বাংলা ภาษาไทย 中文 – 简体 中文 – 繁體 日本語 한국어 | 2026-01-13T09:30:11 |
https://developer.android.com/get-started?hl=tr | Android'in Temelleri | Android Developers Ana içeriğe atla Kaçırmamanız gereken oyunlar Yapay zeka deneyimleri oluşturma Gemini API'leri ve daha fazlasıyla yapay zeka destekli Android uygulamaları geliştirin. Başlama Başlama İlk uygulamanızı oluşturarak başlayın. Eğitim kurslarımızla daha ayrıntılı bilgi edinin veya uygulama geliştirmeyi kendi kendinize öğrenin. Hello world Eğitim kursları Eğitimler Ekipler için Compose Android için Kotlin Google Play ile para kazanma ↗️ Android Geliştirici Doğrulaması Cihaza göre genişletme Kullanıcılarınıza telefondan tablete, kol saatinden kulaklığa kadar her cihazda sorunsuz deneyimler sunan uygulamalar geliştirin. Uyarlanabilir uygulamalar Android XR Wear OS Arabalar için Android Android TV ChromeOS Kategoriye göre oluşturma Google'ın yönlendirici ve kişisel görüşe dayalı rehberliğini takip ederek kullanım alanınıza uygun çözümler geliştirmeyi öğrenin. Oyunlar Kamera ve medya Sosyal ve mesajlaşma Sağlık ve form koruma Verimlilik Kurumsal uygulamalar En son sürümünü edinin Yıl boyunca yeni çıkanları takip edin, önizleme programlarımıza katılın ve geri bildirimlerinizi bizimle paylaşın. Son güncellemeler Deneysel güncellemeler Android Studio önizlemesi Jetpack ve Compose kitaplıkları Wear OS sürümleri Özel Korumalı Alan ↗️ Tasarım ve Planlama Mükemmel deneyimler En iyi kullanıcılarınız için en iyi deneyimleri oluşturun. Daha fazla bilgi Kullanıcı arayüzü tasarımı Android'deki en iyi uygulamaları kullanarak güzel bir kullanıcı arayüzü tasarlayın. Android için tasarım Cep Uyarlanabilir kullanıcı arayüzü XR Kulaklıklar ve XR Gözlükler Yapay Zeka Gözlükleri Widget'lar Wear OS Android TV Arabalar için Android Mimari Güçlü, test edilebilir ve bakımı yapılabilir uygulama mantığı ve hizmetleri tasarlayın. Giriş Kütüphaneler Gezinme Modülerleştirme Test Kotlin Multiplatform Kalite Uygulama kalitesini planlayın ve Play Store yönergelerine uyun. Genel bakış Temel değer Kullanıcı deneyimi Erişilebilirlik Teknik kalite Mükemmel deneyimler Güvenlik Kullanıcıları tehditlere karşı koruyun ve güvenli bir Android deneyimi sağlayın. Genel bakış Gizlilik İzinler Kimlik Sahtekarlığı önleme Geliştirme Android Studio'da Gemini Android geliştirmede yapay zeka geliştirme arkadaşınız. Daha fazla bilgi Android Studio'yu edinme Temel alanlar İhtiyacınız olan özelliklerle ilgili örnekleri ve dokümanları edinin. Örnekler Kullanıcı arayüzleri Arka plan çalışması Veriler ve dosyalar Bağlanabilirlik Tüm temel alanlar ⤵️ Araçlar ve iş akışı Uygulamanızı yazmak ve oluşturmak için IDE'yi kullanın veya kendi işlem hattınızı oluşturun. Kod yazma ve hata ayıklama Proje oluşturma Uygulamanızı test etme Performans Komut satırı araçları Gradle eklentisi API'si Cihaz teknolojisi Form faktörleri için kod yazma Cihazları bağlayın ve verileri paylaşın. Uyarlanabilir kullanıcı arayüzü Wear OS Android XR Android Health Arabalar için Android Android TV Tüm cihazlar ⤵️ Kütüphaneler Tüm ayrıntıları içeren API referans belgelerine göz atın. Android platformu Jetpack kitaplıkları Compose kitaplıkları Google Play Hizmetleri ↗️ Google Play SDK Dizini ↗️ Google Play Play Console Uygulamanızı veya oyununuzu yayınlayın ve Google Play'de işinizi büyütün. Play Console'a git Daha fazla bilgi ↗️ Temel Bilgiler Kullanıcılarla etkileşim kurmayı, uygulamanızdan para kazanmayı ve uygulamanızı güvenli hale getirmeyi öğrenin. Play'de para kazanma Play Integrity Play Politikaları Play Programları ↗️ Games Dev Center Oyun geliştirme ve yayınlama Araçlar, indirilenler ve örnekler Genel bakış Play Asset Delivery Play Games Hizmetleri PC Üzerinde Play Games Tüm Play rehberleri ⤵️ Kütüphaneler Tüm ayrıntıları içeren API referans belgelerine göz atın. Play Özellik Dağıtımı Play uygulama içi güncellemeleri Play uygulama içi yorumları Play Install Referrer Google Play Hizmetleri ↗️ Google Play SDK Dizini ↗️ Tüm Play kitaplıkları ⤵️ Araçlar ve kaynaklar Uygulamanızı yayınlama, tanıtma ve yönetme araçları. Android App Bundle Marka ve pazarlama Play Console API'leri ↗️ Topluluk / English Deutsch Español – América Latina Français Indonesia Italiano Polski Português – Brasil Tiếng Việt Türkçe Русский עברית العربيّة فارسی हिंदी বাংলা ภาษาไทย 中文 – 简体 中文 – 繁體 日本語 한국어 Android Studio Oturum aç Kaçırmamanız gereken oyunlar Diğer Tasarım ve Planlama Diğer Geliştirme Diğer Google Play Diğer Topluluk Android Studio Yapay zeka deneyimleri oluşturma Başlama Başlama Hello world Eğitim kursları Eğitimler Ekipler için Compose Android için Kotlin Google Play ile para kazanma ↗️ Android Geliştirici Doğrulaması Cihaza göre genişletme Uyarlanabilir uygulamalar Android XR Wear OS Arabalar için Android Android TV ChromeOS Kategoriye göre oluşturma Oyunlar Kamera ve medya Sosyal ve mesajlaşma Sağlık ve form koruma Verimlilik Kurumsal uygulamalar En son sürümünü edinin Son güncellemeler Deneysel güncellemeler Android Studio önizlemesi Jetpack ve Compose kitaplıkları Wear OS sürümleri Özel Korumalı Alan ↗️ Mükemmel deneyimler Daha fazla bilgi Kullanıcı arayüzü tasarımı Android için tasarım Cep Uyarlanabilir kullanıcı arayüzü XR Kulaklıklar ve XR Gözlükler Yapay Zeka Gözlükleri Widget'lar Wear OS Android TV Arabalar için Android Mimari Giriş Kütüphaneler Gezinme Modülerleştirme Test Kotlin Multiplatform Kalite Genel bakış Temel değer Kullanıcı deneyimi Erişilebilirlik Teknik kalite Mükemmel deneyimler Güvenlik Genel bakış Gizlilik İzinler Kimlik Sahtekarlığı önleme Android Studio'da Gemini Daha fazla bilgi Android Studio'yu edinme Temel alanlar Örnekler Kullanıcı arayüzleri Arka plan çalışması Veriler ve dosyalar Bağlanabilirlik Tüm temel alanlar ⤵️ Araçlar ve iş akışı Kod yazma ve hata ayıklama Proje oluşturma Uygulamanızı test etme Performans Komut satırı araçları Gradle eklentisi API'si Cihaz teknolojisi Uyarlanabilir kullanıcı arayüzü Wear OS Android XR Android Health Arabalar için Android Android TV Tüm cihazlar ⤵️ Kütüphaneler Android platformu Jetpack kitaplıkları Compose kitaplıkları Google Play Hizmetleri ↗️ Google Play SDK Dizini ↗️ Play Console Play Console'a git Daha fazla bilgi ↗️ Temel Bilgiler Play'de para kazanma Play Integrity Play Politikaları Play Programları ↗️ Games Dev Center Genel bakış Play Asset Delivery Play Games Hizmetleri PC Üzerinde Play Games Tüm Play rehberleri ⤵️ Kütüphaneler Play Özellik Dağıtımı Play uygulama içi güncellemeleri Play uygulama içi yorumları Play Install Referrer Google Play Hizmetleri ↗️ Google Play SDK Dizini ↗️ Tüm Play kitaplıkları ⤵️ Araçlar ve kaynaklar Android App Bundle Marka ve pazarlama Play Console API'leri ↗️ Android Developers Kaçırmamanız gereken oyunlar Koleksiyonlar ile düzeninizi koruyun İçeriği tercihlerinize göre kaydedin ve kategorilere ayırın. Android'in temel özellikleri Platformu yeni kullanmaya başlayan veya en son sürümdeki özellikleri kullanmak isteyen deneyimli bir geliştirici olmanız fark etmeksizin, Android becerilerinizi geliştirmek için dokümanları, eğitimleri ve codelab'leri inceleyin. Uygulamanızın kullanıcı deneyimini çok sayıda cihazda genişletmeyi öğrenin. Tüm ekran boyutlarında optimize edilmiş bir kullanıcı deneyimi sunmak için telefonlara, tabletlere ve katlanabilir cihazlara (tüm form faktörleri) uyum sağlayan uygulamalar geliştirin. Google Play ile uygulamanızdan para kazanın. Başlangıç Android geliştirme ile ilgili temel konulara genel bir bakış için kısa bir eğitime katılın veya eğitim kursuna derinlemesine göz atın. Başlat Uyarlanabilir tasarım Tüm cihaz form faktörlerinde ve ekran boyutlarında optimize edilmiş bir kullanıcı deneyimi sunan uygulamalar tasarlayıp geliştirin. Derleme Birlikte daha iyi Uygulama deneyiminizi geliştirerek birden fazla cihazda birlikte daha iyi çalışmasını sağlayın. Uzat Para kazanma Google Play ile abonelikler, finansal işlemler ve satın alma akışlarıyla para kazanın. Para kazanma Android sürümleri Mevcut Android sürümünün yanı sıra eski sürümleri de keşfedin. Güncelle Birden fazla cihazı destekleme Android, cihaz tasarımı, özellikleri ve genel değeri konusunda kullanıcılara daha fazla seçenek sunmak için her yerde herkesin kullanabileceği şekilde tasarlanmıştır. En geniş cihaz ve form faktörü yelpazesini destekleyerek kullanıcı deneyimini genişletin. Çok cihazlı geliştirme hakkında bilgi Google Play ile para kazanın Google Play'i kullanarak uygulamanıza bir faturalandırma sistemi entegre edin. Google Play, küresel pazarda uygulamanızla para kazanmanıza yardımcı olacak çeşitli özellikler ve destekler sunar. Google Play Faturalandırma Android'de yapay zeka Uygulamalarınızın içeriği anlamasını, metin ve resim oluşturmasını ve kullanıcılarla etkileşim kurmasını sağlayın. Uygulamalarınızı bilgilendirici ve faydalı hale getirmek için Google'ın yapay zeka ve makine öğrenimi araçlarından oluşan tam paketini kullanın. Android'de yapay zekayı keşfedin Geliştirici merkezleri Verimlilik Sorunsuz çoklu görev ve büyük ekran medya entegrasyonları için uyarlanabilir düzenlerle üretkenlik uygulamalarınızı geliştirin. Geliştirici merkezini göster Oyunlar Android'de oyun geliştirmek ve sunmak için ihtiyacınız olan her şeyi edinin. Geliştirici merkezini göster Medya uygulamaları Medya yapımları oluşturma: Medya uygulamaları geliştirme ile ilgili temel kılavuzunuz. Geliştirici merkezini göster Sosyal Medya ve Mesajlaşma Bağlanan, iletişim kuran ve bilgi paylaşan uygulamalar geliştirin. Geliştirici merkezini göster Sağlık ve Fitness Önemli sağlık ve fitness verilerini kaydetme ve raporlama Codelab'e katılın Kurumsal uygulamalar Yönetilen yapılandırmalar, Tek Oturum Açma ve daha fazlası için kurumsal çözümler oluşturun. Yönergeleri göster Son güncellemeler Android ekosistemindeki yenilikleri keşfedin. Tüm son güncellemeleri görüntüleme Android sürümleri Mevcut önizleme sürümü de dahil olmak üzere en son Android platformu sürümlerini görüntüleyin. Jetpack kitaplıkları Jetpack kitaplıkları, daha hızlı yayınlanabilmeleri için Android OS'den ayrı olarak gönderilir. En yeni kitaplık sürümlerini görün. Android Studio önizlemesi Android Studio'daki en yeni özelliklere ve geliştirmelere erken erişim elde edin. Wear OS Test, geliştirme ve geri bildirim için Wear OS'in sonraki sürümünü edinin. Düşüncelerinizi bizimle paylaşmayı unutmayın! Android üzerinde Özel Korumalı Alan Kullanıcı gizliliğini sağlayın ve mobil uygulamalarda kişiselleştirilmiş reklam deneyimlerini etkinleştirin. Geliştirici hikayeleri Geliştiriciler Android ile nasıl başarıya ulaşıyor? Tüm hikayeleri göster Marvel Strike Force yükleme oranını artırdı Uygulamanın dosya boyutu büyük olduğundan organik yükleme sayısı, ekibin bu kadar popüler bir seride beklediğinden daha düşüktü. Google Play Instant ile kurtuluş! Cuvva, Jetpack Compose'u kullanıyor Cuvva'daki Android mühendislerinin, tek yönlü veri akışı ve Jetpack Compose kullanmak için uygulamalarını nasıl yeniden yapılandırdığını öğrenin. Duolingo, kod tabanındaki satır sayısını %30 azalttı. Duolingo'nun Android geliştiricileri, kod tabanlarındaki satır sayısının yıldan yıla% 46 arttığını gördükten sonra Java'dan Kotlin'e geçerek bu şişkinliği durdurdu. [[["Anlaması kolay","easyToUnderstand","thumb-up"],["Sorunumu çözdü","solvedMyProblem","thumb-up"],["Diğer","otherUp","thumb-up"]],[["İhtiyacım olan bilgiler yok","missingTheInformationINeed","thumb-down"],["Çok karmaşık / çok fazla adım var","tooComplicatedTooManySteps","thumb-down"],["Güncel değil","outOfDate","thumb-down"],["Çeviri sorunu","translationIssue","thumb-down"],["Örnek veya kod sorunu","samplesCodeIssue","thumb-down"],["Diğer","otherDown","thumb-down"]],[],[],[]] X X'te @AndroidDev'i takip edin YouTube YouTube'da Android Developers'a göz atın LinkedIn Connect with the Android Developers community on LinkedIn Android hakkında daha fazla Android İşletmeler için Android Güvenlik Kaynak Haber Blog Podcast'ler Keşfet Oyun Makine Öğrenimi Sağlık ve Fitness Kamera ve Medya Gizlilik 5G Android Cihazlar Büyük ekranlar Wear OS ChromeOS cihazlar Arabalar için Android Android TV Sürümler Android 15 Android 14 Android 13 Android 12 Android 11 Android 10 Pie Belgeler ve İndirmeler Android Studio kılavuzu Geliştirici kılavuzları API referansı Studio'yu indir Android NDK Destek Platform hatası bildir Belge hatası bildir Google Play support Araştırma çalışmalarına katıl Android Chrome Firebase Google Cloud Platform Tüm ürünler Gizlilik Lisans Marka kuralları Manage cookies E-postayla haberler ve ipuçları al Abone ol English Deutsch Español – América Latina Français Indonesia Italiano Polski Português – Brasil Tiếng Việt Türkçe Русский עברית العربيّة فارسی हिंदी বাংলা ภาษาไทย 中文 – 简体 中文 – 繁體 日本語 한국어 | 2026-01-13T09:30:11 |
https://extensionworkshop.com/documentation/develop/#test-and-debug | Create extensions for Firefox and Firefox for Android | Firefox Extension Workshop Extension Workshop Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Submit or Manage Extensions Search Submit or Manage Extensions Search Select a section Page Name Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage a | 2026-01-13T09:30:11 |
https://developers.cloudflare.com/fundamentals/reference/policies-compliances/compliance-docs/#_top | Compliance documentation · Cloudflare Fundamentals docs Skip to content Cloudflare Docs Search Docs Directory APIs SDKs Help Log in Select theme Dark Light Auto Cloudflare Fundamentals No results found. Try a different search term, or use our global search . Overview Concepts How Cloudflare DNS works Traffic flow through Cloudflare Accounts, zones, and profiles Cloudflare IP addresses Get started Accounts Create account Account security Add abuse contact Allow Cloudflare access Leaked Password Notifications Manage active sessions Review audit logs - v1 Audit Logs - v2 Beta SCIM provisioning Overview Microsoft Entra Okta Troubleshooting Secure compromised account Set up SSO ↗ Zone holds Find account and zone IDs Change Super Administrator Organizations Beta Members Overview Manage Policies Roles Role scopes User Groups New Set up dashboard SSO User profiles Overview Verify email address Log in to Cloudflare Profile settings Delete your Cloudflare account Email address and password Multi-Factor Email Authentication Two-factor authentication Domains Overview Add multiple sites via automation Change your domain version Manage subdomains Move a domain between Cloudflare accounts Onboard a domain Pause Cloudflare Redirect one domain to another Remove a domain Star domains Performance Improve SEO Maintenance mode Minimize downtime Optimize site speed ↗ Prepare for surges or spikes in web traffic ↗ Test speed Security Prevent DDoS attacks ↗ Protect your origin server Recovering from a hacked site Scan for PCI compliance Secure your website ↗ Under a DDoS attack? Cloudflare's API Get started Create API token Get Global API key (legacy) Get Origin CA keys Account API tokens How to Make API calls Create tokens via API Control API Access Restrict tokens Roll tokens Reference REST API ↗ API GraphQL API ↗ Wrangler API ↗ API token permissions API deprecations API token templates Rate limits SDKs Troubleshooting Reference Migration guides SCIM migration Policies Cloudflare Cookies Compliance documentation Content Security Policies (CSPs) Delivering Videos with Cloudflare Incident Management Policy ↗ Licenses Project Cybersafe Schools Abuse Overview Review abuse policies ↗ Complaint types Providing specific URLs Customer abuse report obligations View and submit reports SDK ecosystem support policy Troubleshooting /cdn-cgi/ endpoint Account and domain management best practices Cloudflare and Google Analytics Cloudflare crawlers Cloudflare HTTP headers Cloudflare Ray ID Cloudy AI agent Beta Connection limits Cryptographic Attestation of Personhood Glossary Network Layers Network ports Partners Redirects Scans and penetration testing policy TCP connections Under Attack mode RSS Feeds Available RSS Feeds Consuming RSS Feeds GitHub X.com YouTube Select theme Dark Light Auto On this page Overview Public data protection and compliance documentation Tax documentation On this page Overview Public data protection and compliance documentation Tax documentation Was this helpful? Edit Issue Directory … Cloudflare Fundamentals Reference Policies Compliance documentation Copy page Compliance documentation Super Administrators can access common compliance documentation, such as PCI, SOC 2, ISO, and more, through the Cloudflare dashboard. To access compliance documentation: Visit Compliance Documents ↗ and select your account where you are a Super Administrator . If you have not accessed this page before, read the confidentiality statement and select I Agree . Choose the document you need and select Download . Note For confidentiality purposes, only Super Administrators for an account can access compliance documentation. Public data protection and compliance documentation Information and documents about Cloudflare's privacy & data protection are available on our public website at cloudflare.com/trust-hub/ ↗ . On the Trust Hub ↗ , you will find information & documents related to: Privacy Policy Data Processing Addendum (DPA) Europe General Data Protection Regulation (GDPR) Brazil General Data Protection Law (LGPD) Japan Act on the Protection of Personal Information (APPI) Singapore Personal Data Protection Act (PDPA) South Korea Personal Information Protection Act (PIPA) India Digital Personal Data Protection Bill (DPDP) Australia Privacy Act United States California Consumer Privacy Act (CCPA) & Consumer Privacy Rights Act (CPRA) EU Digital Operational Resilience Act (DORA) ISO 27001:2022 ISO 27701:2019 ISO 27018:2019 FedRAMP Moderate SOC 2 Type II PCI DSS 4.0 Global CBPR Global PRP EU Cloud Code of Conduct Cyber Essentials C5:2020 ENS IRAP BSI Qualification WCAG 2.1 AA and Section 508 Tax documentation Super Administrators, Billing Administrators, and Administrators can access tax documentation, such W-9 and Tax Certificates, through the Cloudflare dashboard. To access tax documentation: Visit Tax Documents ↗ and select your account where you are a Super Administrator , Billing Administrator or Administrator . Choose the document you need and select Download . Was this helpful? Edit page Last updated: Aug 22, 2025 Previous Cloudflare Cookies Next Content Security Policies (CSPs) Resources API New to Cloudflare? Directory Sponsorships Open Source Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Speed Test Is BGP Safe Yet? RPKI Toolkit Certificate Transparency Community X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings | 2026-01-13T09:30:11 |
https://developers.google.com/admob/api/v1/auth | OAuth setup | AdMob API | Google for Developers Skip to main content AdMob API / English Deutsch Español Español – América Latina Français Indonesia Italiano Polski Português – Brasil Tiếng Việt Türkçe Русский עברית العربيّة فارسی हिंदी বাংলা ภาษาไทย 中文 – 简体 中文 – 繁體 日本語 한국어 Sign in AdMob Guides Reference Libraries & Examples Support AdMob API AdMob Guides Reference Libraries & Examples Support Get started The basics Prerequisites Common errors Authorization Overview Setup Third-party integration Playground Reports Set up your report Metrics and dimensions list Generate reports Inventory Apps and ad units Mediation Mediation management Ad sources Adapters Ad unit mappings Mediation groups Mediation A/B experiment Home Products AdMob API Guides OAuth setup Stay organized with collections Save and categorize content based on your preferences. Page Summary outlined_flag AdMob API calls require OAuth2 authorization for secure interaction with web services on a user's behalf. You need a Google Account, a Google AdMob account, and familiarity with REST basics and OAuth 2.0 authorization as prerequisites. Choose between Desktop app and Web app authentication types based on your application's needs. To use the AdMob API, you must create or select a project in the Google API Console and enable the AdMob API. Create OAuth 2.0 client ID and client secret credentials to make authorized requests using specific scopes. All Google AdMob API calls must be authorized through OAuth2 so your app can interact with web services on the user's behalf. OAuth2 enables your AdMob API client app to access a user's AdMob account without having to handle or store the user's username or password. For an overview of authorization, see Authorization . Perform the following steps to generate the OAuth2 credentials and make your first request. Prerequisites A Google Account . A Google AdMob account . Familiarity with REST basics and authorizing requests with OAuth 2.0 . Determine your authentication type Check the table below to see which authentication type is most appropriate for your app: Choose your OAuth2 authentication type If ... Desktop app You're managing all of your AdMob API accounts using a single top level manager account. You're a first-time user, or want to get started quickly with the simplest setup. Your app only authenticates Google AdMob users from one machine. Web app You want to authenticate as a user who can grant permission to your app to access their AdMob API account data. You want to easily generate multiple authorization credentials, to manage third-party accounts for example. Your app requires callback URLs. Callback URLs are not supported in the desktop app flow. Key Point: You can still choose the desktop app flow even if you're developing an app to run on a server. The difference is whether the OAuth authorization is completed locally or remotely. A desktop flow requires authorization to be completed on the local machine, whereas the web-flow lets authorization be completed on Google's authorization server. Create a project To get started using the AdMob API, you need to first create or select a project in the Google API Console and enable the API using the setup tool , which guides you through the process and activates the AdMob API automatically. Enabling the API for an existing project The following steps apply to users who have an existing project and prefer to activate the AdMob API for it manually. To enable an API for your project: Open the API Library in the Google API Console. If prompted, select a project, or create a new one. The API Library lists all available APIs, grouped by product family and popularity. If the API you want to enable isn't visible in the list, use search to find it, or click View All in the product family it belongs to. Select the API you want to enable, then click the Enable button. If prompted, enable billing. If prompted, read and accept the API's Terms of Service. Create OAuth2 credentials The following instructions guide you through the process of creating an OAuth 2.0 client ID to use with the installed app flow . Go to the Clients page . Click CREATE CREDENTIALS > OAuth client ID . If you hadn't configured an OAuth consent screen for this project previously, you'll be directed to do so now. Click CONFIGURE CONSENT SCREEN . There are multiple ways to configure your consent screen to use your OAuth 2.0 client ID. Set your user type to External and publishing status to Published . Or, set your user type to External and publishing status to Testing , then add Test users by selecting add users to give them access to use your OAuth 2.0 client ID. See additional information on setting up your OAuth consent screen . Select Desktop app or Web Application as the application type, give it a name, then click Create . When done, you are presented with an OAuth 2.0 client ID and client secret, which you can download in JSON format and save for later use. Make a request The AdMob API is built on HTTP and JSON, so any standard HTTP client can send requests to it and parse the responses. However, the Google API client libraries provide better language integration, improved security, and support for making authorized requests. The client libraries are available in a number of programming languages; by using them you can avoid the need to manually set up HTTP requests and parse the responses. Note: The first time you activate the OAuth flow, you are asked to provide your AdMob publisher ID and accept an authorization prompt in your browser. Before accepting, make sure you're signed in with a Google Account that has access to your AdMob account. Your app is then authorized to access data on behalf of whichever account is currently logged in. With OAuth 2.0 credentials created , you're ready to start using the AdMob API. To request access using OAuth 2.0, your app also needs scope information: Scope Meaning https://www.googleapis.com/auth/admob.readonly See all AdMob data. This may include account information, inventory and mediation settings, reports, and other data. This doesn't include sensitive data, such as payments or campaign details. https://www.googleapis.com/auth/admob.report See ad performance and earnings reports. See publisher ID, timezone, and default currency code. Make your first request to generate a report using examples in Java , PHP , Python or curl . Revoke shared tokens You can revoke shared tokens in two ways: Navigate to your Google account permissions page and revoke access from the relevant project. Alternatively, you can revoke web application tokens using the Google Identity API . Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License , and code samples are licensed under the Apache 2.0 License . For details, see the Google Developers Site Policies . Java is a registered trademark of Oracle and/or its affiliates. Last updated 2025-08-28 UTC. [[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-28 UTC."],[],["To use the Google AdMob API, authorize calls via OAuth2. First, create or select a project in the Google API Console and enable the AdMob API. Next, create OAuth2 credentials, choosing between \"Desktop app\" or \"Web app\" authentication types based on your needs. Configure the OAuth consent screen, download the generated client ID and secret, and then use these credentials to authorize requests with specified scopes, such as `admob.monetization` or `admob.readonly`. To start making requests, you can utilize the Google API client libraries. If you want to revoke access, you can do so from your Google account or using Google Identity API.\n"]] Product info Usage limits Pricing Terms of Service Programs Google Developer Program Google Developer Groups Google Developer Experts Accelerators Google Cloud & NVIDIA Developer consoles Google API Console Google Cloud Platform Console Google Play Console Firebase Console Actions on Google Console Cast SDK Developer Console Chrome Web Store Dashboard Google Home Developer Console Android Chrome Firebase Google Cloud Platform Google AI All products Terms Privacy Manage cookies English Deutsch Español Español – América Latina Français Indonesia Italiano Polski Português – Brasil Tiếng Việt Türkçe Русский עברית العربيّة فارسی हिंदी বাংলা ภาษาไทย 中文 – 简体 中文 – 繁體 日本語 한국어 | 2026-01-13T09:30:11 |
https://developers.cloudflare.com/ai-gateway/features/unified-billing/ | Unified Billing · Cloudflare AI Gateway docs Skip to content Cloudflare Docs Search Docs Directory APIs SDKs Help Log in Select theme Dark Light Auto AI Gateway No results found. Try a different search term, or use our global search . Overview Getting started Using AI Gateway Unified API (OpenAI compat) Provider Native Workers AI Amazon Bedrock Anthropic Azure OpenAI Baseten Cartesia Cerebras Cohere Deepgram DeepSeek ElevenLabs Fal AI Google AI Studio Google Vertex AI Groq HuggingFace Ideogram Mistral AI OpenAI OpenRouter Parallel Perplexity Replicate xAI WebSockets API Beta Overview Realtime WebSockets API Non-realtime WebSockets API Features Overview Unified Billing Caching Rate limiting Dynamic routing Beta Overview Using a dynamic route JSON Configuration Data Loss Prevention (DLP) Beta Overview Set up Data Loss Prevention (DLP) Guardrails Beta Overview Set up Guardrails Supported model types Usage considerations Configuration BYOK (Store Keys) Beta Custom costs Custom Providers Beta Manage gateways Request handling Authenticated Gateway Observability Costs Custom metadata Analytics Logging Overview Workers Logpush Integrations Vercel AI SDK Agents ↗ AI Gateway Binding Methods Workers AI Tutorials Platform Overview Limits Pricing Audit logs Changelog Header Glossary REST API reference ↗ API MCP server ↗ MCP AI Assistant ↗ Architectures LLM resources llms.txt prompt.txt AI Gateway llms-full.txt Developer Platform llms-full.txt GitHub X.com YouTube Select theme Dark Light Auto On this page Overview Pre-requisites Load credits Auto-top up Use Unified Billing Spend limits Supported providers On this page Overview Pre-requisites Load credits Auto-top up Use Unified Billing Spend limits Supported providers Was this helpful? Edit Issue Directory … AI Gateway Features Unified Billing Copy page Unified Billing Unified Billing allows users to connect to various AI providers (such as OpenAI, Anthropic, and Google AI Studio) and receive a single Cloudflare bill. To use Unified Billing, you must purchase and load credits into your Cloudflare account in the Cloudflare dashboard, which you can then spend with AI Gateway. Pre-requisites Ensure your Cloudflare account has sufficient credits loaded . Ensure you have authenticated your AI Gateway. Load credits To load credits for AI Gateway: In the Cloudflare dashboard, go to the AI Gateway page. Go to AI Gateway The Credits Available card on the top right shows how many AI gateway credits you have on your account currently. In Credits Available , select Manage . If your account does not have an available payment method, AI Gateway will prompt you to add a payment method to purchase credits. Add a payment method. Select Top-up credits . Add the amount of credits you want to purchase, then select Confirm and pay . Auto-top up You can configure AI Gateway to automatically replenish your credits when they fall below a certain threshold. To configure auto top-up: In the Cloudflare dashboard, go to the AI Gateway page. Go to AI Gateway In Credits Available , select Manage . Select Setup auto top-up credits . Choose a threshold and a recharge amount for auto top-up. When your balance falls below the set threshold, AI Gateway will automatically apply the auto top-up amount to your account. Use Unified Billing Call any supported provider without passing an API Key. The request will automatically use Cloudflare's key and deduct credits from your account. For example, you can use the Unified API: Terminal window curl -X POST https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions \ --header 'cf-aig-authorization: Bearer {CLOUDFLARE_TOKEN}' \ --header 'Content-Type: application/json' \ --data '{ "model": "google-ai-studio/gemini-2.5-pro", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] }' Spend limits Set spend limits to prevent unexpected charges on your loaded credits. You can define daily, weekly, or monthly limits. When a limit is reached, the AI Gateway automatically stops processing requests until the period resets or you increase the limit. Supported providers Unified Billing supports the following AI providers: OpenAI Anthropic Google AI Studio xAI Groq Was this helpful? Edit page Last updated: Nov 25, 2025 Previous Features Next Caching Resources API New to Cloudflare? Directory Sponsorships Open Source Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Speed Test Is BGP Safe Yet? RPKI Toolkit Certificate Transparency Community X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings | 2026-01-13T09:30:11 |
https://developers.google.com/admob/api/reference/rest/v1beta/accounts.adSources | REST Resource: accounts.adSources | AdMob API | Google for Developers Skip to main content AdMob API / English Deutsch Español Español – América Latina Français Indonesia Italiano Polski Português – Brasil Tiếng Việt Türkçe Русский עברית العربيّة فارسی हिंदी বাংলা ภาษาไทย 中文 – 简体 中文 – 繁體 日本語 한국어 Sign in AdMob Guides Reference Libraries & Examples Support AdMob API AdMob Guides Reference Libraries & Examples Support Release notes AdMob API v1 REST Resources accounts Overview get list accounts.adUnits Overview list accounts.apps Overview list accounts.mediationReport Overview generate accounts.networkReport Overview generate Types DateRange LocalizationSettings ReportFooter ReportHeader ReportRow SortOrder StringList v1beta REST Resources accounts Overview get list accounts.adSources Overview list accounts.adSources.adapters Overview list accounts.adUnitMappings Overview batchCreate accounts.adUnits Overview create list accounts.adUnits.adUnitMappings Overview create list accounts.apps Overview create list accounts.campaignReport Overview generate accounts.mediationGroups Overview create list patch accounts.mediationGroups.mediationAbExperiments Overview create stop accounts.mediationReport Overview generate accounts.networkReport Overview generate Types DateRange LocalizationSettings MediationGroupLine ReportFooter ReportHeader ReportRow SortOrder StringList API dictionary Ad sources Adapters Home Products AdMob API Reference REST Resource: accounts.adSources Stay organized with collections Save and categorize content based on your preferences. Resource Methods Resource There is no persistent data associated with this resource. Methods list List the ad sources. Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License , and code samples are licensed under the Apache 2.0 License . For details, see the Google Developers Site Policies . Java is a registered trademark of Oracle and/or its affiliates. Last updated 2025-08-20 UTC. [[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-20 UTC."],[],["The content describes a resource with no persistent data. The only available method for this resource is the `list` method. This method, accessible via `/admob/api/reference/rest/v1beta/accounts.adSources/list`, enables users to retrieve a list of ad sources. No other actions or data manipulation capabilities are outlined. The resource's functionality is limited to this retrieval operation.\n"]] Product info Usage limits Pricing Terms of Service Programs Google Developer Program Google Developer Groups Google Developer Experts Accelerators Google Cloud & NVIDIA Developer consoles Google API Console Google Cloud Platform Console Google Play Console Firebase Console Actions on Google Console Cast SDK Developer Console Chrome Web Store Dashboard Google Home Developer Console Android Chrome Firebase Google Cloud Platform Google AI All products Terms Privacy Manage cookies English Deutsch Español Español – América Latina Français Indonesia Italiano Polski Português – Brasil Tiếng Việt Türkçe Русский עברית العربيّة فارسی हिंदी বাংলা ภาษาไทย 中文 – 简体 中文 – 繁體 日本語 한국어 | 2026-01-13T09:30:11 |
https://es.wired.com/ciencia/medio-ambiente | Noticias sobre medio ambiente | WIRED Skip to main content Open Navigation Menu Menu Medio ambiente Negocios Cultura Gadgets Ideas Ciencia Medio Ambiente Seguridad Politica Inteligencia Artificial More Chevron Buscar Buscar Negocios Cultura Gadgets Ideas Ciencia Medio Ambiente Seguridad Politica Inteligencia Artificial Buscar RSS Medio ambiente Noticias y novedades sobre medio ambiente, sustentabilidad y sostenibilidad. Salud Espacio Medio Ambiente Clima Energía Biotecnología Robots Neurociencia Medio Ambiente Dos bebés gorilas de montaña gemelos nacen en el Congo y es un acontecimiento extremadamente raro Los dos bebés fueron vistos en brazos de su madre y se encuentran en buen estado de salud. Medio Ambiente Por qué falló esta prometedora tecnología que prometía limpiar el aire con algas Con el apoyo de Microsoft, Stripe y Shopify, Running Tide se promocionó como una empresa pionera en la eliminación de carbono. Al final, recurrió a arrojar miles de toneladas de astillas de madera al mar. Medio Ambiente ¿Cuánta radiación electromagnética genera la red 5G y qué tan peligrosa es? El uso de teléfonos inteligentes para cargar y descargar datos aumenta la exposición, sobre todo en zonas con menor cobertura de señal. Medio Ambiente El Glaciar del Juicio Final está cada vez más cerca de un colapso irreversible Un análisis de la expansión de las grietas del glaciar Thwaites en los últimos 20 años sugiere que un colapso total podría ser solo cuestión de tiempo. Medio Ambiente La mayoría de los perros aún tienen ADN de lobo (hasta el chihuahua) Hasta hace poco, se creía que la hibridación entre lobo y perro era extremadamente rara, pero nuevas investigaciones han revelado que muchas razas de perros modernas aún conservan rastros de genes de lobo, y esta "memoria genómica" parece influir en su físico, personalidad e incluso en su sentido del olfato. Medio Ambiente El jaguar renace en México: la población del felino más grande de América crece 30% gracias a collares GPS satelitales México se consolida como el único país con un censo nacional del felino más grande de América, registrando una recuperación poblacional del 30% en la última década. En el corazón de la selva maya, WIRED es testigo de una alianza entre tecnología satelital, financiamiento internacional y pragmatismo económico busca blindar la segunda reserva tropical más grande del continente antes de que sea demasiado tarde. Medio Ambiente La mitad de las playas podría quedar sumergida, pero el aumento del nivel del mar es solo una de las amenazas Ahora conocemos los detalles sobre la posibilidad de que casi la mitad de las playas arenosas del planeta desaparezcan a finales de siglo. Al parecer, el mecanismo revelado no se debe únicamente a la subida del nivel del mar provocada por el cambio climático. Medio Ambiente El plan que los gobiernos necesitan para detener el tsunami de comida desperdiciada El desperdicio de alimentos en el mundo asciende a un promedio de 132 kg por persona al año. Para combatirlo, salvaguardando al mismo tiempo el bolsillo y el medio ambiente, hay que actuar a varios niveles. Esta es la receta de un equipo de expertos británicos. Medio Ambiente Este es el calamar vampiro, un fósil viviente que nos ayudó a descubrir los antiguos orígenes de los pulpos Pulpos, calamares y sepias se diferenciaron hace más de 300 millones de años. Se trata del mayor genoma de cefalópodos analizado hasta hoy. Medio Ambiente Los gatos llegaron a Europa gracias a los romanos Un reciente estudio paleogenómico indica que los gatos llegaron a Europa desde el norte de África durante el Imperio romano y se expandieron después con notable rapidez. Medio Ambiente Chinampa refugio: Cómo la agricultura ancestral podría salvar al ajolote… y a Xochimilco Xochimilco pasará de ser un área de conservación bajo amenaza a un laboratorio de urbanismo regenerativo y un motor de cambio para la seguridad alimentaria y la gestión hídrica en el Valle de México. Medio Ambiente Descubren en Australia la abeja Lucifer, una nueva especie con “cuernos de diablo” Recientemente se ha descubierto en Australia una nueva especie de abeja con un par de cuernos en la cabeza inspirados en el diablo. ¿Qué aspecto tiene exactamente? Medio Ambiente Design Thinking en la selva: El experimento del BID que busca transformar las fronteras de Latinoamérica El Banco Interamericano de Desarrollo (BID), a través del programa de Bienes Públicos Regionales (BPR), y la consultora Olivia, implementaron un modelo pionero de cooperación binacional centrado en la educación para la sostenibilidad. Medio Ambiente Los océanos subirán por el calentamiento global. La pregunta es: ¿cuándo? La excepcionalmente vulnerable capa de hielo de la Antártida Occidental contiene suficiente agua como para elevar el nivel global del mar en cinco metros. Pero aún no se sabe con certeza cuándo ocurrirá esto ni con qué rapidez. Medio Ambiente Los abejorros pueden descifrar destellos de luz de manera similar al código Morse El abejorro es capaz de detectar la duración de los destellos luminosos. Esta habilidad, antes confirmada únicamente en humanos y algunos vertebrados, también se manifiesta en su diminuto cerebro, de menos de un milímetro cúbico de volumen. Medio Ambiente Cómo los genes han aprovechado la física para el crecimiento de los seres vivos La misma fuerza que provoca las “lágrimas” en una copa de vino da forma a los embriones. Es otro ejemplo de cómo los genes aprovechan las fuerzas mecánicas para el crecimiento y el desarrollo. Medio Ambiente La COP30 cierra con un acuerdo descafeinado al obviar los combustibles fósiles La cumbre climática COP30, que se celebró en Belém (Brasil), consiguió finalmente un acuerdo, un día después de la fecha límite. El texto final no establece una hoja de ruta clara para abandonar los combustibles fósiles, algo que había sido solicitado por más de 80 Estados, incluida la Unión Europea. Medio Ambiente Usan IA para analizar el sonido de los cachalotes: tienen un un alfabeto sorprendentemente complejo La forma de comunicarse de estos cetáceos es sorprendente: sus propiedades acústicas se asemejan potencialmente a las vocales, un rasgo distintivo de nuestro lenguaje. Medio Ambiente El ARN es frágil, pero estas momias de mamut han conservado una muestra de 40,000 años Un estudio reciente sobre mamuts lanudos, publicado en Cell , revela que el ARN puede persistir durante mucho más tiempo de lo que se pensaba. Medio Ambiente Con tecnología, títeres y mucha paciencia, el delicado plan por salvar al cóndor andino Como parte del Programa de Conservación del Cóndor Andino, desde el Centro de Incubación Artificial instalado en Buenos Aires trabajan en la cría sin contacto humano para recuperar la población de estas aves carroñeras. ver más WIRED es donde se hace realidad el mañana. Es la fuente esencial de información e ideas que dan sentido a un mundo en constante cambio. Inspiramos para conectar, cuestionar y transformar. Facebook X YouTube Instagram Tiktok LinkedIn Flipboard Google News Whatsapp Argentina Chile Colombia España México Panamá Perú AD GLAMOUR GQ VOGUE RSS Site Map Aviso de Privacidad Convenio del usuario Política de Afiliación Prensa Media Kit © 2026 Condé Nast México S.A de C.V. Todos los derechos reservados. Convenio del usuario Aviso de Privacidad Términos y condiciones Select international site WIRED LargeChevron México Japón Italia US Czech Republic & Slovakia | 2026-01-13T09:30:11 |
https://extensionworkshop.com/documentation/develop/#what-is-manifest-v3 | Create extensions for Firefox and Firefox for Android | Firefox Extension Workshop Extension Workshop Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Submit or Manage Extensions Search Submit or Manage Extensions Search Select a section Page Name Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage a | 2026-01-13T09:30:11 |
https://github.com/nuxt/nuxt/pull/24954 | feat(nuxt): server-only pages by huang-julien · Pull Request #24954 · nuxt/nuxt · GitHub Skip to content Navigation Menu Toggle navigation Sign in Appearance settings Platform AI CODE CREATION GitHub Copilot Write better code with AI GitHub Spark Build and deploy intelligent apps GitHub Models Manage and compare prompts MCP Registry New Integrate external tools DEVELOPER WORKFLOWS Actions Automate any workflow Codespaces Instant dev environments Issues Plan and track work Code Review Manage code changes APPLICATION SECURITY GitHub Advanced Security Find and fix vulnerabilities Code security Secure your code as you build Secret protection Stop leaks before they start EXPLORE Why GitHub Documentation Blog Changelog Marketplace View all features Solutions BY COMPANY SIZE Enterprises Small and medium teams Startups Nonprofits BY USE CASE App Modernization DevSecOps DevOps CI/CD View all use cases BY INDUSTRY Healthcare Financial services Manufacturing Government View all industries View all solutions Resources EXPLORE BY TOPIC AI Software Development DevOps Security View all topics EXPLORE BY TYPE Customer stories Events & webinars Ebooks & reports Business insights GitHub Skills SUPPORT & SERVICES Documentation Customer support Community forum Trust center Partners Open Source COMMUNITY GitHub Sponsors Fund open source developers PROGRAMS Security Lab Maintainer Community Accelerator Archive Program REPOSITORIES Topics Trending Collections Enterprise ENTERPRISE SOLUTIONS Enterprise platform AI-powered developer platform AVAILABLE ADD-ONS GitHub Advanced Security Enterprise-grade security features Copilot for Business Enterprise-grade AI features Premium Support Enterprise-grade 24/7 support Pricing Search or jump to... Search code, repositories, users, issues, pull requests... --> Search Clear Search syntax tips Provide feedback --> We read every piece of feedback, and take your input very seriously. Include my email address so I can be contacted Cancel Submit feedback Saved searches Use saved searches to filter your results more quickly --> Name Query To see all available qualifiers, see our documentation . Cancel Create saved search Sign in Sign up Appearance settings Resetting focus You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert {{ message }} nuxt / nuxt Public Uh oh! There was an error while loading. Please reload this page . Notifications You must be signed in to change notification settings Fork 5.5k Star 59.3k Code Issues 816 Pull requests 114 Discussions Actions Projects 1 Security Uh oh! There was an error while loading. Please reload this page . Insights Additional navigation options Code Issues Pull requests Discussions Actions Projects Security Insights feat(nuxt): server-only pages #24954 New issue Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Sign up for GitHub By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement . We’ll occasionally send you account related emails. Already on GitHub? Sign in to your account Jump to bottom Merged danielroe merged 51 commits into main from feat/server-page Feb 26, 2024 Merged feat(nuxt): server-only pages #24954 danielroe merged 51 commits into main from feat/server-page Feb 26, 2024 Conversation 20 Commits 51 Checks 0 Files changed Uh oh! There was an error while loading. Please reload this page . Conversation This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters Show hidden characters Copy link Member huang-julien commented Dec 29, 2023 • edited by danielroe Loading Uh oh! There was an error while loading. Please reload this page . 🔗 Linked issue ❓ Type of change #19772 📖 Documentation (updates to the documentation, readme or JSdoc annotations) 🐞 Bug fix (a non-breaking change that fixes an issue) 👌 Enhancement (improving an existing functionality like performance) ✨ New feature (a non-breaking change that adds functionality) 🧹 Chore (updates to the build process or auxiliary tools and libraries) ⚠️ Breaking change (fix or feature that would cause existing functionality to change) 📚 Description Hi 👋 this PR allows users to define pages as server page with definePageMeta() and the .server.vue suffix in the filename. in definePageMeta this PR took #25037 as reference for the field name : mode . For now it only accept undefined or 'server' . For the client only implementation, see #25037 📝 Checklist I have linked an issue or discussion. I have updated the documentation accordingly. test refactor ??? --> Sorry, something went wrong. Uh oh! There was an error while loading. Please reload this page . --> All reactions huang-julien added 8 commits November 22, 2023 19:51 wip test 0097fa4 feat: use current route path and remove component from preload f35b414 Merge branch 'main' into feat/server-page 338d479 fix: fix components.islands template 283096d Merge remote-tracking branch 'origin/main' into feat/server-page a9caf7f test: rename SugarCounter to Counter 2dc1242 Merge remote-tracking branch 'origin/main' into feat/server-page a9d3ae8 fix: stop loading indicator after server page end 10ca60f Copy link bolt-new-by-stackblitz bot commented Dec 29, 2023 Run & review this pull request in StackBlitz Codeflow . --> All reactions --> Sorry, something went wrong. Uh oh! There was an error while loading. Please reload this page . github-actions bot added the 3.x label Dec 29, 2023 danielroe added the enhancement label Jan 5, 2024 danielroe force-pushed the main branch from f78140e to 4168157 Compare January 9, 2024 09:39 huang-julien added 5 commits February 3, 2024 20:06 Merge remote-tracking branch 'origin/main' into feat/server-page 446b67f refactor: test by moving all to build time 8afef3d chore: lint f939108 chore: LINNNTTT 70c9809 chore: LIIIIIIIIIIIIIIIIIIIINNNNNNNNTTTTTTTTTTT a29d5c2 github-advanced-security bot found potential problems Feb 4, 2024 View reviewed changes packages/nuxt/src/pages/utils.ts Fixed Show fixed Hide fixed Uh oh! There was an error while loading. Please reload this page . huang-julien and others added 2 commits February 4, 2024 17:22 fix: correctly laod server page in runtime ce525f5 [autofix.ci] apply automated fixes b0f2f3b github-advanced-security bot found potential problems Feb 4, 2024 View reviewed changes packages/nuxt/src/pages/utils.ts Fixed Show fixed Hide fixed Uh oh! There was an error while loading. Please reload this page . huang-julien and others added 6 commits February 11, 2024 21:56 fix: fix route file generation and introduce createIslandPage to hand… … 0c2844b …le the transition component Merge branch 'feat/server-page' of https://github.com/nuxt/nuxt into … … 4a55e8c …feat/server-page [autofix.ci] apply automated fixes a763824 fix: fix .server route detection 9bc0e9b Merge branch 'feat/server-page' of https://github.com/nuxt/nuxt into … … 6123b66 …feat/server-page [autofix.ci] apply automated fixes 8703c28 huang-julien changed the title feat(nuxt): define island pages with definePageMeta macro feat(nuxt): server only pages Feb 11, 2024 Merge branch 'main' into feat/server-page 9a5c498 github-advanced-security bot found potential problems Feb 14, 2024 View reviewed changes packages/nuxt/src/pages/utils.ts Fixed Show fixed Hide fixed Uh oh! There was an error while loading. Please reload this page . --> 21 hidden items Load more… Apply suggestions from code review … b673a33 Co-authored-by: Daniel Roe <daniel@roe.dev> danielroe reviewed Feb 25, 2024 View reviewed changes packages/nuxt/src/app/components/nuxt-island.ts Outdated // TODO: Validate response // $fetch handles the app.baseURL in dev const r = await eventFetch ( withQuery ( ( ( import . meta . dev && import . meta . client ) || props . source ) ? url : joinURL ( config . app . baseURL ?? '' , url ) , { url : route . fullPath , Copy link Member danielroe Feb 25, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page . There was a problem hiding this comment. Choose a reason for hiding this comment The reason will be displayed to describe this comment to others. Learn more . --> Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Hide comment I think this will make it much harder to cache server islands as the hash we create will vary by path. Could we instead pass this as part of the context via createIslandPage instead (and maybe use route.path to skip query/hash)? --> Sorry, something went wrong. Uh oh! There was an error while loading. Please reload this page . --> All reactions Copy link Member Author huang-julien Feb 25, 2024 There was a problem hiding this comment. Choose a reason for hiding this comment The reason will be displayed to describe this comment to others. Learn more . --> Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Hide comment I think we should not skip query 🤔, userss tend to relly on it within pages composables. Maybe can we pass an object like { path : string , query ?: Record < string , string > } ? --> Sorry, something went wrong. Uh oh! There was an error while loading. Please reload this page . --> All reactions Copy link Member danielroe Feb 25, 2024 There was a problem hiding this comment. Choose a reason for hiding this comment The reason will be displayed to describe this comment to others. Learn more . --> Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Hide comment The issue is (for example) that we will make a separate request for every query variation, which wouldn't be compatible with static sites and allow cache-busting by passing arbitrary query params or hashes ... (We should definitely not pass hash.) We could document this as a limitation of server pages... Or at a minimum, skip passing the full route if the route matches prerender routeRule? --> Sorry, something went wrong. Uh oh! There was an error while loading. Please reload this page . --> All reactions Copy link Member Author huang-julien Feb 25, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page . There was a problem hiding this comment. Choose a reason for hiding this comment The reason will be displayed to describe this comment to others. Learn more . --> Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Hide comment I see, let's start by passing only the path in the context then 🤔. and iterate on it, i'm not sure what kind of side effect we can have if using fullPath with ssg --> Sorry, something went wrong. Uh oh! There was an error while loading. Please reload this page . --> All reactions huang-julien and others added 8 commits February 25, 2024 22:41 fix: move url path to context cfb5708 Merge branch 'feat/server-page' of https://github.com/nuxt/nuxt into … … f40e653 …feat/server-page docs: add warning about query not being send to server pages bff2a85 chore: update import d969135 docs: update slightly 67b697c perf: use single dynamic import 9a29f0c Merge remote-tracking branch 'origin/main' into feat/server-page a01b82e fix: allow setting 'all' as a mode 3207fd6 github-advanced-security bot found potential problems Feb 25, 2024 View reviewed changes packages/nuxt/src/pages/utils.ts Fixed Show fixed Hide fixed Uh oh! There was an error while loading. Please reload this page . perf: simplify 51a30d7 danielroe reviewed Feb 25, 2024 View reviewed changes Copy link Member danielroe left a comment There was a problem hiding this comment. Choose a reason for hiding this comment The reason will be displayed to describe this comment to others. Learn more . --> Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Hide comment this looks great to me. I do think we probably could respect the route query as long as it's not a prerendered page. (We can use isPrerendered to tell us.). And I think we should drop the support for defining server-only pages within definePageMeta , which means that it's impossible to tree-shake this code out of the bundle, if even one page has any metadata at all. --> Sorry, something went wrong. Uh oh! There was an error while loading. Please reload this page . --> All reactions github-advanced-security bot found potential problems Feb 25, 2024 View reviewed changes packages/nuxt/src/pages/utils.ts Fixed Show fixed Hide fixed Uh oh! There was an error while loading. Please reload this page . packages/nuxt/src/pages/utils.ts Fixed Show fixed Hide fixed Uh oh! There was an error while loading. Please reload this page . danielroe added 6 commits February 26, 2024 16:39 refactor: only enable server pages at build with .server.vue and in… … afd8cb8 … `pages:extend` Merge remote-tracking branch 'origin/main' into feat/server-page 2bbef5b fix: pass query for non-prerendered server pages 948c374 fix: use route, not normalised page 3a1262a perf: use more exact import 523d55e fix: don't pass attrs/props 6a64292 github-advanced-security bot found potential problems Feb 26, 2024 View reviewed changes packages/nuxt/src/pages/utils.ts Outdated Check warning Code scanning / CodeQL Improper code sanitization Code construction depends on an [improperly sanitized value](1). danielroe approved these changes Feb 26, 2024 View reviewed changes danielroe changed the title feat(nuxt): server only pages feat(nuxt): server-only pages Feb 26, 2024 danielroe merged commit 196223c into main Feb 26, 2024 danielroe deleted the feat/server-page branch February 26, 2024 17:39 github-actions bot mentioned this pull request Feb 26, 2024 v3.11.0 #25964 Merged Copy link brc-dd commented Feb 29, 2024 There seems to be an issue with this if you try to directly access the server-only page in dev: [nitro] [unhandledRejection] FetchError: [GET] "/_nuxt/builds/meta/dev.json": 404 Page not found: /_nuxt/builds/meta/dev.json at async $fetch2 (file:///Users/brc-dd/nuxt-app/node_modules/.pnpm/ofetch@1.3.3/node_modules/ofetch/dist/shared/ofetch.00501375.mjs:261:15) [Vue warn]: Component foo is missing template or render function. It works fine if you open home first and then go to server-only page via link 👀 --> 👀 1 huang-julien reacted with eyes emoji All reactions 👀 1 reaction --> Sorry, something went wrong. Uh oh! There was an error while loading. Please reload this page . This was referenced Mar 3, 2024 perf(nuxt): don't check for prerendered route in dev for server page #26061 Merged fix(nuxt): import manifest in dev mode #26063 Closed BalaKadiyala mentioned this pull request Jun 22, 2024 [Snyk] Upgrade nuxt from 3.7.0 to 3.11.2 BalaKadiyala/snyk-chat-goof#7 Open --> Sign up for free to join this conversation on GitHub . Already have an account? Sign in to comment --> Reviewers danielroe danielroe approved these changes --> Assignees No one assigned Labels 3.x enhancement --> Projects None yet --> Milestone No milestone --> Development Successfully merging this pull request may close these issues. Uh oh! There was an error while loading. Please reload this page . 5 participants Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later. Footer © 2026 GitHub, Inc. Footer navigation Terms Privacy Security Status Community Docs Contact Manage cookies Do not share my personal information You can’t perform that action at this time. | 2026-01-13T09:30:11 |
https://developers.google.com/admob/api/reference/rest/v1beta/accounts.adUnits/list | Method: accounts.adUnits.list | AdMob API | Google for Developers Skip to main content AdMob API / English Deutsch Español Español – América Latina Français Indonesia Italiano Polski Português – Brasil Tiếng Việt Türkçe Русский עברית العربيّة فارسی हिंदी বাংলা ภาษาไทย 中文 – 简体 中文 – 繁體 日本語 한국어 Sign in AdMob Guides Reference Libraries & Examples Support AdMob API AdMob Guides Reference Libraries & Examples Support Release notes AdMob API v1 REST Resources accounts Overview get list accounts.adUnits Overview list accounts.apps Overview list accounts.mediationReport Overview generate accounts.networkReport Overview generate Types DateRange LocalizationSettings ReportFooter ReportHeader ReportRow SortOrder StringList v1beta REST Resources accounts Overview get list accounts.adSources Overview list accounts.adSources.adapters Overview list accounts.adUnitMappings Overview batchCreate accounts.adUnits Overview create list accounts.adUnits.adUnitMappings Overview create list accounts.apps Overview create list accounts.campaignReport Overview generate accounts.mediationGroups Overview create list patch accounts.mediationGroups.mediationAbExperiments Overview create stop accounts.mediationReport Overview generate accounts.networkReport Overview generate Types DateRange LocalizationSettings MediationGroupLine ReportFooter ReportHeader ReportRow SortOrder StringList API dictionary Ad sources Adapters Home Products AdMob API Reference Method: accounts.adUnits.list Stay organized with collections Save and categorize content based on your preferences. Page Summary outlined_flag The webpage lists ad units under a specified AdMob account using an HTTP GET request. The request requires a parent path parameter specifying the account resource name. Optional query parameters like pageSize and pageToken can control the number of results and pagination. The response body contains an array of ad unit objects and an optional nextPageToken for continuation. The request requires specific OAuth authorization scopes, either for monetization or read-only access. HTTP request Path parameters Query parameters Request body Response body JSON representation Authorization scopes Examples Try it! List the ad units under the specified AdMob account. HTTP request GET https://admob.googleapis.com/v1beta/{parent=accounts/*}/adUnits The URL uses gRPC Transcoding syntax. Path parameters Parameters parent string Required. Resource name of the account to list ad units for. Example: accounts/pub-9876543210987654 Query parameters Parameters pageSize integer The maximum number of ad units to return. If unspecified or 0, at most 10,000 ad units will be returned. The maximum value is 20,000; values above 20,000 will be coerced to 20,000. pageToken string The value returned by the last ListAdUnitsResponse ; indicates that this is a continuation of a prior adUnits.list call, and that the system should return the next page of data. Request body The request body must be empty. Response body Response for the ad units list request. If successful, the response body contains data with the following structure: JSON representation { "adUnits" : [ { object ( AdUnit ) } ] , "nextPageToken" : string } Fields adUnits[] object ( AdUnit ) The resulting ad units for the requested account. nextPageToken string If not empty, indicates that there may be more ad units for the request; this value should be passed in a new ListAdUnitsRequest . Authorization scopes Requires one of the following OAuth scopes: https://www.googleapis.com/auth/admob.monetization https://www.googleapis.com/auth/admob.readonly For more information, see the OAuth 2.0 Overview . Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License , and code samples are licensed under the Apache 2.0 License . For details, see the Google Developers Site Policies . Java is a registered trademark of Oracle and/or its affiliates. Last updated 2025-08-20 UTC. [[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-20 UTC."],[],["This document details how to list ad units associated with a specific AdMob account. The process involves sending a `GET` request to `https://admob.googleapis.com/v1beta/{parent=accounts/*}/adUnits`, where `parent` is the account's resource name. Optional query parameters, `pageSize` (up to 20,000) and `pageToken` (for pagination), can be included. The request body must be empty. The response includes an array of `adUnits` and a `nextPageToken` for further results. Authorization requires specific OAuth scopes.\n"]] Product info Usage limits Pricing Terms of Service Programs Google Developer Program Google Developer Groups Google Developer Experts Accelerators Google Cloud & NVIDIA Developer consoles Google API Console Google Cloud Platform Console Google Play Console Firebase Console Actions on Google Console Cast SDK Developer Console Chrome Web Store Dashboard Google Home Developer Console Android Chrome Firebase Google Cloud Platform Google AI All products Terms Privacy Manage cookies English Deutsch Español Español – América Latina Français Indonesia Italiano Polski Português – Brasil Tiếng Việt Türkçe Русский עברית العربيّة فارسی हिंदी বাংলা ภาษาไทย 中文 – 简体 中文 – 繁體 日本語 한국어 | 2026-01-13T09:30:11 |
https://developers.cloudflare.com/ai-gateway/usage/providers/grok/ | xAI · Cloudflare AI Gateway docs Skip to content Cloudflare Docs Search Docs Directory APIs SDKs Help Log in Select theme Dark Light Auto AI Gateway No results found. Try a different search term, or use our global search . Overview Getting started Using AI Gateway Unified API (OpenAI compat) Provider Native Workers AI Amazon Bedrock Anthropic Azure OpenAI Baseten Cartesia Cerebras Cohere Deepgram DeepSeek ElevenLabs Fal AI Google AI Studio Google Vertex AI Groq HuggingFace Ideogram Mistral AI OpenAI OpenRouter Parallel Perplexity Replicate xAI WebSockets API Beta Overview Realtime WebSockets API Non-realtime WebSockets API Features Overview Unified Billing Caching Rate limiting Dynamic routing Beta Overview Using a dynamic route JSON Configuration Data Loss Prevention (DLP) Beta Overview Set up Data Loss Prevention (DLP) Guardrails Beta Overview Set up Guardrails Supported model types Usage considerations Configuration BYOK (Store Keys) Beta Custom costs Custom Providers Beta Manage gateways Request handling Authenticated Gateway Observability Costs Custom metadata Analytics Logging Overview Workers Logpush Integrations Vercel AI SDK Agents ↗ AI Gateway Binding Methods Workers AI Tutorials Platform Overview Limits Pricing Audit logs Changelog Header Glossary REST API reference ↗ API MCP server ↗ MCP AI Assistant ↗ Architectures LLM resources llms.txt prompt.txt AI Gateway llms-full.txt Developer Platform llms-full.txt GitHub X.com YouTube Select theme Dark Light Auto On this page Overview Endpoint URL structure Prerequisites Examples cURL Use OpenAI SDK with JavaScript Use OpenAI SDK with Python Use Anthropic SDK with JavaScript Use Anthropic SDK with Python OpenAI-Compatible Endpoint On this page Overview Endpoint URL structure Prerequisites Examples cURL Use OpenAI SDK with JavaScript Use OpenAI SDK with Python Use Anthropic SDK with JavaScript Use Anthropic SDK with Python OpenAI-Compatible Endpoint Was this helpful? Edit Issue Directory … AI Gateway Using AI Gateway Provider Native xAI Copy page xAI Endpoint https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/grok URL structure When making requests to Grok ↗ , replace https://api.x.ai/v1 in the URL you are currently using with https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/grok . Prerequisites When making requests to Grok, ensure you have the following: Your AI Gateway Account ID. Your AI Gateway gateway name. An active xAI API token. The name of the xAI model you want to use. Examples cURL Request curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/grok/v1/chat/completions \ --header 'content-type: application/json' \ --header 'Authorization: Bearer {xai_api_token}' \ --data '{ "model": "grok-4", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] }' Use OpenAI SDK with JavaScript If you are using the OpenAI SDK with JavaScript, you can set your endpoint like this: JavaScript import OpenAI from "openai" ; const openai = new OpenAI ( { apiKey : "<api key>" , baseURL : "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/grok" , } ) ; const completion = await openai . chat . completions . create ( { model : "grok-4" , messages : [ { role : "system" , content : "You are Grok, a chatbot inspired by the Hitchhiker's Guide to the Galaxy." , }, { role : "user" , content : "What is the meaning of life, the universe, and everything?" , }, ] , } ) ; console . log ( completion . choices [ 0 ] . message ) ; ", baseURL: "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/grok",});const completion = await openai.chat.completions.create({ model: "grok-4", messages: [ { role: "system", content: "You are Grok, a chatbot inspired by the Hitchhiker's Guide to the Galaxy.", }, { role: "user", content: "What is the meaning of life, the universe, and everything?", }, ],});console.log(completion.choices[0].message);"> Use OpenAI SDK with Python If you are using the OpenAI SDK with Python, you can set your endpoint like this: Python import os from openai import OpenAI XAI_API_KEY = os . getenv ( "XAI_API_KEY" ) client = OpenAI ( api_key = XAI_API_KEY , base_url = "https://gateway.ai.cloudflare.com/v1/ {account_id} / {gateway_id} /grok" , ) completion = client . chat . completions . create ( model = "grok-4" , messages = [ { "role" : "system" , "content" : "You are Grok, a chatbot inspired by the Hitchhiker's Guide to the Galaxy." }, { "role" : "user" , "content" : "What is the meaning of life, the universe, and everything?" }, ], ) print ( completion . choices [ 0 ]. message ) Use Anthropic SDK with JavaScript If you are using the Anthropic SDK with JavaScript, you can set your endpoint like this: JavaScript import Anthropic from "@anthropic-ai/sdk" ; const anthropic = new Anthropic ( { apiKey : "<api key>" , baseURL : "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/grok" , } ) ; const msg = await anthropic . messages . create ( { model : "grok-beta" , max_tokens : 128 , system : "You are Grok, a chatbot inspired by the Hitchhiker's Guide to the Galaxy." , messages : [ { role : "user" , content : "What is the meaning of life, the universe, and everything?" , }, ] , } ) ; console . log ( msg ) ; ", baseURL: "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/grok",});const msg = await anthropic.messages.create({ model: "grok-beta", max_tokens: 128, system: "You are Grok, a chatbot inspired by the Hitchhiker's Guide to the Galaxy.", messages: [ { role: "user", content: "What is the meaning of life, the universe, and everything?", }, ],});console.log(msg);"> Use Anthropic SDK with Python If you are using the Anthropic SDK with Python, you can set your endpoint like this: Python import os from anthropic import Anthropic XAI_API_KEY = os . getenv ( "XAI_API_KEY" ) client = Anthropic ( api_key = XAI_API_KEY , base_url = "https://gateway.ai.cloudflare.com/v1/ {account_id} / {gateway_id} /grok" , ) message = client . messages . create ( model = "grok-beta" , max_tokens = 128 , system = "You are Grok, a chatbot inspired by the Hitchhiker's Guide to the Galaxy." , messages = [ { "role" : "user" , "content" : "What is the meaning of life, the universe, and everything?" , }, ], ) print ( message . content ) OpenAI-Compatible Endpoint You can also use the OpenAI-compatible endpoint ( /ai-gateway/usage/chat-completion/ ) to access Grok models using the OpenAI API schema. To do so, send your requests to: https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions Specify: { " model " : "grok/{model}" } Was this helpful? Edit page Last updated: Nov 24, 2025 Previous Replicate Next WebSockets API Resources API New to Cloudflare? Directory Sponsorships Open Source Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Speed Test Is BGP Safe Yet? RPKI Toolkit Certificate Transparency Community X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings | 2026-01-13T09:30:11 |
https://developers.cloudflare.com/ai-gateway/usage/providers/fal/ | Fal AI · Cloudflare AI Gateway docs Skip to content Cloudflare Docs Search Docs Directory APIs SDKs Help Log in Select theme Dark Light Auto AI Gateway No results found. Try a different search term, or use our global search . Overview Getting started Using AI Gateway Unified API (OpenAI compat) Provider Native Workers AI Amazon Bedrock Anthropic Azure OpenAI Baseten Cartesia Cerebras Cohere Deepgram DeepSeek ElevenLabs Fal AI Google AI Studio Google Vertex AI Groq HuggingFace Ideogram Mistral AI OpenAI OpenRouter Parallel Perplexity Replicate xAI WebSockets API Beta Overview Realtime WebSockets API Non-realtime WebSockets API Features Overview Unified Billing Caching Rate limiting Dynamic routing Beta Overview Using a dynamic route JSON Configuration Data Loss Prevention (DLP) Beta Overview Set up Data Loss Prevention (DLP) Guardrails Beta Overview Set up Guardrails Supported model types Usage considerations Configuration BYOK (Store Keys) Beta Custom costs Custom Providers Beta Manage gateways Request handling Authenticated Gateway Observability Costs Custom metadata Analytics Logging Overview Workers Logpush Integrations Vercel AI SDK Agents ↗ AI Gateway Binding Methods Workers AI Tutorials Platform Overview Limits Pricing Audit logs Changelog Header Glossary REST API reference ↗ API MCP server ↗ MCP AI Assistant ↗ Architectures LLM resources llms.txt prompt.txt AI Gateway llms-full.txt Developer Platform llms-full.txt GitHub X.com YouTube Select theme Dark Light Auto On this page Overview Endpoint URL structure Prerequisites Default synchronous API cURL example Custom target URLs cURL example with custom target URL WebSocket API JavaScript SDK integration JavaScript SDK example On this page Overview Endpoint URL structure Prerequisites Default synchronous API cURL example Custom target URLs cURL example with custom target URL WebSocket API JavaScript SDK integration JavaScript SDK example Was this helpful? Edit Issue Directory … AI Gateway Using AI Gateway Provider Native Fal AI Copy page Fal AI Fal AI ↗ provides access to 600+ production-ready generative media models through a single, unified API. The service offers the world's largest collection of open image, video, voice, and audio generation models, all accessible with one line of code. Endpoint https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/fal URL structure When making requests to Fal AI, replace https://fal.run in the URL you're currently using with https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/fal . Prerequisites When making requests to Fal AI, ensure you have the following: Your AI Gateway Account ID. Your AI Gateway gateway name. An active Fal AI API token. The name of the Fal AI model you want to use. Default synchronous API By default, requests to the Fal AI endpoint will hit the synchronous API at https://fal.run/<path> . cURL example Terminal window curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/fal/fal-ai/fast-sdxl \ --header 'Authorization: Key {fal_ai_token}' \ --header 'Content-Type: application/json' \ --data '{ "prompt": "Make an image of a cat flying an aeroplane" }' Custom target URLs If you need to hit a different target URL, you can supply the entire Fal target URL in the x-fal-target-url header. cURL example with custom target URL Terminal window curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/fal \ --header 'Authorization: Bearer {fal_ai_token}' \ --header 'x-fal-target-url: https://queue.fal.run/fal-ai/bytedance/seedream/v4/edit' \ --header 'Content-Type: application/json' \ --data '{ "prompt": "Dress the model in the clothes and hat. Add a cat to the scene and change the background to a Victorian era building.", "image_urls": [ "https://storage.googleapis.com/falserverless/example_inputs/seedream4_edit_input_1.png", "https://storage.googleapis.com/falserverless/example_inputs/seedream4_edit_input_2.png", "https://storage.googleapis.com/falserverless/example_inputs/seedream4_edit_input_3.png", "https://storage.googleapis.com/falserverless/example_inputs/seedream4_edit_input_4.png" ] }' WebSocket API Fal AI also supports real-time interactions through WebSockets. For WebSocket connections and examples, see the Realtime WebSockets API documentation . JavaScript SDK integration The x-fal-target-url format is compliant with the Fal SDKs, so AI Gateway can be easily passed as a proxyUrl in the SDKs. JavaScript SDK example JavaScript import { fal } from "@fal-ai/client" ; fal . config ( { credentials : "{fal_ai_token}" , // OR pass a cloudflare api token if using BYOK on AI Gateway proxyUrl : "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/fal" } ) ; const result = await fal . subscribe ( "fal-ai/bytedance/seedream/v4/edit" , { "input" : { "prompt" : "Dress the model in the clothes and hat. Add a cat to the scene and change the background to a Victorian era building." , "image_urls" : [ "https://storage.googleapis.com/falserverless/example_inputs/seedream4_edit_input_1.png" , "https://storage.googleapis.com/falserverless/example_inputs/seedream4_edit_input_2.png" , "https://storage.googleapis.com/falserverless/example_inputs/seedream4_edit_input_3.png" , "https://storage.googleapis.com/falserverless/example_inputs/seedream4_edit_input_4.png" ] } } ) ; console . log ( result . data . images [ 0 ]) ; Was this helpful? Edit page Last updated: Sep 22, 2025 Previous ElevenLabs Next Google AI Studio Resources API New to Cloudflare? Directory Sponsorships Open Source Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Speed Test Is BGP Safe Yet? RPKI Toolkit Certificate Transparency Community X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings | 2026-01-13T09:30:11 |
https://developers.cloudflare.com/ai-gateway/reference/limits/ | Limits · Cloudflare AI Gateway docs Skip to content Cloudflare Docs Search Docs Directory APIs SDKs Help Log in Select theme Dark Light Auto AI Gateway No results found. Try a different search term, or use our global search . Overview Getting started Using AI Gateway Unified API (OpenAI compat) Provider Native Workers AI Amazon Bedrock Anthropic Azure OpenAI Baseten Cartesia Cerebras Cohere Deepgram DeepSeek ElevenLabs Fal AI Google AI Studio Google Vertex AI Groq HuggingFace Ideogram Mistral AI OpenAI OpenRouter Parallel Perplexity Replicate xAI WebSockets API Beta Overview Realtime WebSockets API Non-realtime WebSockets API Features Overview Unified Billing Caching Rate limiting Dynamic routing Beta Overview Using a dynamic route JSON Configuration Data Loss Prevention (DLP) Beta Overview Set up Data Loss Prevention (DLP) Guardrails Beta Overview Set up Guardrails Supported model types Usage considerations Configuration BYOK (Store Keys) Beta Custom costs Custom Providers Beta Manage gateways Request handling Authenticated Gateway Observability Costs Custom metadata Analytics Logging Overview Workers Logpush Integrations Vercel AI SDK Agents ↗ AI Gateway Binding Methods Workers AI Tutorials Platform Overview Limits Pricing Audit logs Changelog Header Glossary REST API reference ↗ API MCP server ↗ MCP AI Assistant ↗ Architectures LLM resources llms.txt prompt.txt AI Gateway llms-full.txt Developer Platform llms-full.txt GitHub X.com YouTube Select theme Dark Light Auto On this page Overview On this page Overview Was this helpful? Edit Issue Directory … AI Gateway Platform Limits Copy page Limits The following limits apply to gateway configurations, logs, and related features in Cloudflare's platform. Feature Limit Cacheable request size 25 MB per request Cache TTL 1 month Custom metadata 5 entries per request Datasets 10 per gateway Gateways free plan 10 per account Gateways paid plan 20 per account Gateway name length 64 characters Log storage rate limit 500 logs per second per gateway Logs stored paid plan 10 million per gateway 1 Logs stored free plan 100,000 per account 2 Log size stored 10 MB per log 3 Logpush jobs 4 per account Logpush size limit 1MB per log 1 If you have reached 10 million logs stored per gateway, new logs will stop being saved. To continue saving logs, you must delete older logs in that gateway to free up space or create a new gateway. Refer to Auto Log Cleanup for more details on how to automatically delete logs. 2 If you have reached 100,000 logs stored per account, across all gateways, new logs will stop being saved. To continue saving logs, you must delete older logs. Refer to Auto Log Cleanup for more details on how to automatically delete logs. 3 Logs larger than 10 MB will not be stored. Need a higher limit? To request an increase to a limit, complete the Limit Increase Request Form ↗ . If the limit can be increased, Cloudflare will contact you with next steps. Was this helpful? Edit page Last updated: Aug 19, 2025 Previous Platform Next Pricing Resources API New to Cloudflare? Directory Sponsorships Open Source Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Speed Test Is BGP Safe Yet? RPKI Toolkit Certificate Transparency Community X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings | 2026-01-13T09:30:11 |
https://khoros.com/privacy#how-we-transfer-your-personal-data | Privacy Khoros is now part of the IgniteTech family. Learn More . Search: Search Support Sign in Products AI & Automation AI for every conversation, campaign, and customer Khoros Communities Self-service support, education, and collaboration Khoros Service Agent efficiency, automation, and operational insights Khoros Social Media Management Content management, publishing, and governance Resources Resource Center Guides, tipsheets, ebooks, on-demand webinars, & more Blog Insights, tips, news, and more from our team to yours Developer information Technical overviews and links to developer documentation Events Join us for webinars and in-person events Integrations Integrations to connect with your customers, wherever they are Tech integrations Trust Center Policies, resources, certifications, and updates on our commitment to data security & compliance Customer Stories Join our community Get a demo Logo Support Sign in Products AI & Automation Khoros Communities Khoros Service Khoros Social Media Management Resources Resource Center Blog Developer information Events Integrations Trust Center Customer Stories Privacy Notice Last updated: August 2024 Your privacy is important to us, and so is being transparent about how we collect, use, share, and secure your Personal Data (defined below). This Privacy Notice is intended to help you understand what Personal Data we collect, how we use, share, retain, and transfer it, and your rights regarding your Personal Data. What this Privacy Notice covers What personal data we collect How we use your personal data How we share your personal data How we transfer your personal data How long we keep your personal data How we secure your personal data Your rights and options regarding your personal data How we use cookies and other tracking technologies Changes to this Privacy Notice How to contact us Other important privacy information Information for residents of China Key changes What this Privacy Notice covers This Privacy Notice (or, “Notice”) describes how Khoros collects, uses, shares, and secures your Personal Data when you access this website ( https://khoros.com ) and/or Khoros’s Community ( https://community.khoros.com/ ) (together, this “Site”), use our Services (defined below), or otherwise interact with us. It also explains your rights regarding our use of your Personal Data and your options concerning how we communicate with you. If you do not agree with this Privacy Notice, do not access our Site, use our Services, or interact with any other part of our business. When we say “Personal Data” (or “information” interchangeably throughout this Notice), we mean any data that could directly or indirectly be used to identify you or your household. Personal Data can be anything ranging from your name and email address, to the IP address of your device, and the location from which you access this website. When we refer to “Khoros,” “we,” and “us,” we mean Khoros, LLC and its wholly owned subsidiaries. When we refer to our “Services,” we mean our digital customer engagement platform, our products, and the other services we provide to our Customers. Khoros provides a variety of products via our digital customer engagement platform, which helps our customers (“Customers”) create the best user experience for their end users and customers (“End Users”). These products include: 1. Marketing; 2. Care; and 3. Community. Please note when we are providing Services to our Customers, this Privacy Notice does not apply to the extent that we are acting as a Customer’s data processor or service provider. If you want to know more about how we process Personal Data on behalf of a Customer, you should consult that Customer’s privacy notice and/or contact that customer directly. If you have any questions or concerns regarding the information contained in this Notice, you can contact us by sending your queries to the addresses listed in the “ How to Contact Us ” section below. What personal data we collect We collect a minimal amount of information to make our Site, Services, and business function. We collect information about you when you provide it to us, when you visit our Site, when you use our Services, and when other sources provide it to us. You can read more about the information we collect about you and why in the sections below. Personal Data You Provide Directly to Us . We collect Personal Data from you when you provide it to us directly – for example, when you post it in our Community or apply for a job at Khoros. This information can include your name, email address, phone number, company title, and social media account information. We collect this information from you when you provide it to us in the following contexts: Context Type Legal Basis for Processing Marketing Communications We receive user-submitted information from you when you want to receive additional promotional information about our Services. This can include your name, phone number, company, title, and email address. We collect this information to serve our legitimate interest of communicating effectively with you and our Customers. Our processing may also be based on your consent. Employment Applications We receive information from job applicants as part of our recruiting activities. This information includes anything that you choose to provide, such as information on a resume. As part of this process, we also collect gender, race, and military status to assist us in our equal employment opportunity compliance and related statistical tracking to help our diversity efforts. Prior to hiring, we will also request information needed to conduct a background check. Information collected from job applicants is needed to help us adhere to our legitimate interest of creating an efficient workforce and complying with relevant laws. Account Registration on Our Community We collect information from you when you create an account on our Community, called “Atlas.” We have a legitimate interest in providing account-related functionalities to our users. Information from account registration on Atlas is collected for this purpose. Information Posted in Atlas We collect information provided by you and stored in Atlas. Information shared on Atlas is processed only with your consent. Ethics and Compliance Hotline We retain a third party to maintain our Ethics and Compliance hotline. If you report a complaint via our Ethics and Compliance Hotline (“Hotline”), we collect any information that the Hotline captures. This can include your name and contact information (unless you opt to report anonymously), along with the details of your report. Our legal basis for collecting information from our Hotline is to ensure our compliance with certain laws. Information collected from our Hotline enables us to receive, investigate, and resolve ethics and compliance reports, concerns, and questions. Office Visits If you visit any of our offices, we collect your name, phone number, company, title, and email address. We have a legitimate interest in collecting this information for record retaining purposes. Event Attendance We collect information such as your name, phone number, company, title, and email address when you register for and/or attend our events. We have a legitimate interest in collecting this information to maintain accurate records of individuals who attend our events. Personal Data Collected From Our Services. We collect Personal Data from our Customers (via their authorized users) and their End Users when we provide our Services. We share this information with our service providers to deliver our Services to our Customers and as needed for our own legitimate business and operational purposes (for example, to do the things we need to do to function as a business). Among other things, service providers help us to administer our Site, conduct surveys, provide technical support, process payments, and assist in the fulfillment of orders. When we collect Personal Data on behalf of our Customers, we do so as our Customers’ processor or service provider in accordance with their specific instructions. As such, if you are a Customer’s End User with questions about how your Personal Data is being handled, please reach out directly to that Customer. Our Customers maintain their own policies concerning the collection, use, and storage of the Personal Data of their End Users. You can read more information about what information we collect from our Services and why in the table below. And, a comprehensive list of the Personal Data that we collect from our Customers and their End Users can also be found here . Context Type Legal Basis for Processing Information from Customers We collect information from our Customers and their employees with whom we may interact, which allows them to log onto our platform and use our Services. This data consists of the Personal Data of their authorized users, company information and configuration, content, internal communications, and notes. Our legitimate interest for collecting this information is to provide our Services effectively to our Customers. Cookies and First-Party Tracking We may place tracking technology on our Site that collects analytics, records how you interact with our Site, or allows us to participate in behavior-based advertising. This means that a third party uses technology (e.g., a cookie) to collect information about your use of our Site so that they can report analytics to us or provide advertising about products and services tailored to your interests. That third party might also collect information over time and across different websites in order to serve advertisements on our website or other websites. Please refer to our Khoros Cookies Datasheet for more information. Where required by law, we base the use of third-party cookies upon consent. Account Registration Our Customers can create accounts through our Services. For certain Services, like our Community product, End Users can also create accounts through our Services. We collect this information to serve our legitimate interest in providing account-related functionalities to our Customers and End Users. Accounts can also be used for easy checkouts and to save preferences and transaction history. Information Posted to a Customer’s Community Customers and their End Users can post information in our Customers’ Communities. We process this information based upon consent. Single Sign-On Information You can log in to our Services using single sign-on services, such as Facebook Connect or an Open ID provider. These services will authenticate your identity and provide you the option to share certain your information with us pre-populate our sign-up form. Services like Facebook Connect give you the option to post shareable information about your activities through our Services to your network. Collecting information from single sign-on services upholds our legitimate interest in ensuring that our Customers and End Users can connect to our Services. Social Media We collect information about End Users that is made available to us and other third parties by social media networks such as Twitter, Facebook, Instagram, Pinterest, YouTube, Google, and others through APIs or social media monitoring technology. This data includes names, user IDs, social media handles, gender, and other information that you choose to make publicly available on these sites. We also monitor the public activities of individuals on social media networks, including their posts, blogs, tweets, and profile information, and messages directed at our Customers. Our collection and use of information from third party social media networks allows us to fulfill our legitimate business interests of providing Services to our Customers, assisting our Customers to provide better Services to their End Users, and maintaining the privacy of individuals. Mobile Applications Information collected through our mobile appications can be used for analytical and non-analytical purposes. For analytical purposes, we collect behavioral data through analytics tools to understand how End Users interact with our mobile applications. This includes information about the screens End Users visit, the duration of their sessions, and the actions they take within the application. For non-analytical purposes, we may collect additional data to facilitate general application functionality. The includes features such as the ability to upload and share photos, videos, and documents from the End User’s device to our servers. In some cases, we may request sensitive information with your consent. Our legitimate business interest in collecting this data is to analyze and improve the functionality, usability, and overall user experience of our mobile applications. The data can also be used to troubleshoot and resolve issues. Please note that any direct or indirect use of any social media network or other third-party site through our Services is subject to your consent of the legal terms and conditions of that site. Your continued use of our Services and of those social media networks constitutes your acceptance of both this Privacy Notice and the legal terms and conditions of those social media networks. To read these third party terms and conditions, please refer to the “ Other Important Privacy Information ” section of this Privacy Notice. Personal Data We Collect Automatically From You . When you visit our Site, use our Services, request more information about us, or sign up for one of our events, we collect information automatically using tracking technologies and web forms. Specifically, we use cookies to passively collect information such as browser type and IP address. This means that a third party uses technology (e.g., a cookie) to collect information about your use of our Site so that they can report analytics to us or provide advertising about products and services tailored to your interests. That third party might also collect information over time and across different websites in order to serve advertisements on our website or other websites. We collect this information to provide you with what you request, to learn more about who is interested in our Services, to track usage, to provide a personalized experience, and to improve navigation experience on our pages. Our legal basis and legitimate interest for this processing is to ensure that our Site and Services run smoothly and without interruption. Personal Data From Third Parties . We collect information from partners and other websites pertaining to visitors of our Site and our Customers‘ websites. For example, we will ask or engage these third parties to tell us additional information about their visitors, such as how they respond to our communications or promotions. We do so because we have a legitimate interest in learning more about how our users respond to communications and promotions. Similarly, we partner with a third-party ad network to display advertisements on our Site and to manage our advertisements on other sites. Our ad network partner uses cookies and web beacons to collect information about your activities on this and other websites to provide you targeted ads based upon your interests (excluding sensitive topics, such as political or religious views). If you do not want this information to be used for the purpose of serving you targeted ads, you may opt-out by clicking here . Please note that opting out will remove targeted ads only. You will still receive generic ads. Our legal basis for obtaining this information is to capture Site analytics. How we use your personal data We collect information from several different sources, and where we collect the information from dictates how we use it. Below are high-level descriptions of some of the purposes for which we use the information we collect about you. Provide, Maintain and Improve the Site and Our Services. We collect information about you to ensure optimal functionality of our Site and Services. For example, for our social media management Services (e.g. our Marketing product), information taken from social media helps us to provide context to a brand, such as information about an individual’s interactions with that brand. We can also use information collected from social media to measures a brand’s influence on those platforms. Brands can then use this information to provide better support and service to their customers, since this information helps them better understand what their customers want. Additionally, we use information gathered from other sources to respond to requests for additional information about our Services, to develop and enhance our Services, and to fulfill our legal obligations as needed. We may use a user's email address to send promotional or marketing materials on related Services, such as updates on the product line. This is only the case when a user is a Customer, a Service is requested by the user, or we have some other pre-existing business relationship with the user. We use your IP address and browser-type information in the general administration of our Site. Please be advised that for our Care product, Khoros’s use and transfer of information received from Google’s APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Please refer to that policy for additional information. Marketing and Personalized Advertising . We process your Personal Data to send you marketing information, product recommendations, and other non-transactional communications (e.g., marketing newsletters, telemarketing calls, SMS, or push notifications) about us, our affiliates, and partners. These can include information about our products, promotions, or events as necessary. We also process your Personal Data to conduct marketing research, advertise to you, and provide personalized information about us, both on and off our Site. Further, we use your Personal Data to provide personalized content based upon your activities and interests to the extent necessary for us to achieve our advertising goals. You can read more about your rights when it comes to marketing and advertising in the “ Your Rights and Options Regarding Your Data ” section below. Measure Performance . We are always looking for ways to make our Services smarter, faster, more secure, and useful. To do this, we use information and collective learnings for analytics and measurements to understand how our Services are being used. When this data is aggregated and analyzed, it allows us to troubleshoot, improve, and track trends across our platform. Communicate with You . We use your contact information to send communications via email and within the Services, such as updates and changes. We also provide tailored communications based on your activity and interactions with us. For Safety and Security . We use information about you and your Service use to verify accounts and activity, to detect, prevent, and respond to potential or actual security incidents and to monitor and protect against other malicious, deceptive, fraudulent, or illegal activity. For Employment Evaluations . Information collected during the recruitment process is used to help us evaluate your candidacy for employment. This information is disclosed to our private equity sponsor. You can read more about this in the “ How We Share Your Personal Data ” section below. For Legal Compliance. If we have a legal obligation to process your information, we will do so in cooperation with public and government authorities, courts, or regulators. This is done to protect our rights or as necessary to protect against misuse or abuse of our websites. We will also cooperate with legal authorities to: 1) protect personal property, 2) ensure our safety, 3) pursue all remedies available to us and limit our damages, 4) comply with judicial proceedings, court orders, or legal processes, or 5) respond to lawful requests. For Other Purposes . Please note that we may use your information in these additional scenarios: in accordance with your consent, to complete a merger or sale of assets, to allow social sharing functionality on our Site and through our Services, to manage our contests or promotions, to register visitors to our office, and to protect you, our Customers, and the public. How we share your personal data There are some circumstances where we need to share your information. However, we will never sell your information or the information of End Users . And, we will never share your information or the information of End Users outside of the ways described below. To any third party with your consent We may share your information outside of Khoros when we have your consent. To companies that provide services on our behalf We engage certain third-party vendors and service providers to carry out data processing functions on our behalf. These providers are limited to only accessing or using this data to provide services to us and must provide reasonable assurance that they will appropriately safeguard the data. More information about these third-parties can be found here . Compliance with legal obligations We may share your information if (i) we reasonably believe that disclosure is compelled by applicable law, regulation, legal process, or a government request, (ii) to enforce our agreements and policies, (iii) to protect the security or integrity of our services and products, (iv) to protect ourselves, our customers, or the public from harm or illegal activities, or (v) to respond to an emergency which we believe in good faith requires us to disclose data. This includes information captured by our Ethics and Compliance Hotline. If we are required by law to disclose any Personal Data of you or your End User, we will notify you of the disclosure requirement unless we are prohibited by law. You can read more about our policy on law enforcement requests by clicking here . Vista Equity Partners We may share your information with our private equity sponsor, Vista Equity Partners (“Vista”), and its affiliates. Vista will only use the information for research, database development, workforce analytics, and business operation purposes in accordance with this Policy. Vista collects this information to better manage, administer, and improve its business. If applicable, Vista also utilizes this information to enhance your employment with Khoros. If you consent, we will also share your information with other Vista portfolio companies for the employment consideration in our pooling system. A full list of Vista portfolio companies can be found here . You can also read Vista’s privacy policy here . Employment/recruitment transfers In connection with our recruiting activities, we may transfer your data to our applicant tracking and evaluation providers, such as iCims, Hirebridge, LLC, and Criteria Corp. Hirebridge, LLC and Criteria Corp. have agreed to comply with the European Union Standard Contractual Clauses and the United Kingdom Standard Contractual Clauses to ensure that any of your information that is transferred outside of the European Economic Area is adequately protected. Business transfers Your information may be part of the assets transferred or shared in connection with the due diligence for a corporate sale, merger, reorganization, dissolution, or similar event. In this situation, we may transfer your informaton in a way that constitutes a sale under applicable law. If we do, we will let you know ahead of time, and will continue to ensure that your information is processed in accordance with this Privacy Notice. Aggregated or de-identified data We may sometimes share information about our customers with third parties to determine usage patterns. This data will always be de-identified or aggregated so that you remain unidentifiable. How we transfer your personal data Khoros operates on a global scale. As a result, we may have to transfer your information to our affiliates, contractors, service providers, and other third parties in various countries and jurisdictions around the world. When this happens, we utilize the appropriate safeguards to make sure your information remains protected. The way we safeguard your information is highlighted below. Transfers from the EEA, UK, and Switzerland. To facilitate our global operations, we may transfer information worldwide. If you are located in the European Economic Area (“EEA”), United Kingdom (“UK”), or Switzerland, some of the countries that we transfer, store, and process information in may not have privacy and data protection laws that are equivalent to the laws of the country where you are located. When this is the case, we utilize the European Commission Standard Contractual Data Protection Clauses and the United Kingdom Standard Contractual Data Protection Clauses to safeguard the transfer of information we collect from the EEA, the UK, and Switzerland. Transfers to Other Countries. When we transfer your information to third parties located in countries outside the EEA, the UK, or Switzerland, we comply with the applicable cross-border transfer rules of those countries. For our Customers, we do this by entering into a written agreement with each Customer that meets the data protection requirements of these countries. Additionally, when we collect information about you as part of our Services, it may be transferred, stored, and/or processed in the United States. In these instances, we ensure that the appropriate organizational, contractual, and technical safeguards are in place so that your information is always protected. How long we keep your personal data We will retain your Personal Data for as long as your account is active or as needed to provide our Services to you. We may also retain the Personal Data in an encrypted format for disaster recovery purposes for up to 90 days following the termination or expiration of an agreement, pending routine erasure cycles. Log files held for security reasons may also be retained for up to 12 months. In general, other types of information, like information obtained from your use of this Site or from employment applications, will be retained for the period prescribed by applicable law. For further information on our Personal Data retention practices and policies as it relates to our Services, please see our Data Retention and Media Destruction Policy for Customer Data . If you have any additional questions on this topic, you may contact us using the information contained in the “Contact Us” section below. You may also request us to stop the use of your Personal Data to provide Services at any time. How we secure your personal data We take information security and privacy of Personal Data very seriously. We fully support and abide by the data privacy principals established in the EU Directive on Data Protection as well as all other applicable local privacy laws and regulations. Our security controls and mechanisms are based on the ISO 27001 global security management standard, and we conduct external security audits and independent security testing on an annual basis. You can read more about our security measures here . Please note that no service is completely secure. While we strive to protect your Personal Data, we cannot guarantee that unauthorized access, hacking, data loss or a data breach will never occur. If we are required by law to inform you of a breach to your information, we may notify you electronically, in writing, or by telephone. Your rights and options regarding your personal data You are afforded certain rights when it comes to your information. Below is a summary of those rights, how to exercise them, and any limitations. Your Rights. You have the right to know: what Personal Data of yours we process; to request a copy of your information in a structured, electronic format; to object to our use of your information; or to request deletion or restriction of your information. Additionally, you may request that: we update, correct, or supplement any information that we hold about you; we limit how we process your Personal Data; or we provide information about the consequences of denying consent to processing. You can submit any such requests via this form. You may opt-out of online tracking based targeted advertising (e.g., cookies) by clicking the preference link listed at the bottom of each page on this Site. Please note that if you change browsers or computers, or if you clear your browser’s cache, you may need to click the link again to apply your preference. You may also opt-out of other forms of targeted advertising by submitting a request as described below. If you choose, you may opt-out of having your information used for certain purposes, such as receiving promotional or marketing materials from us. If you no longer wish to receive these updates, you can opt-out by following the instructions listed in the mailer or by emailing us at marketing@khoros.com (please include the term OPT-OUT in the subject line followed by your email address if you choose the latter). Where we collect or process your personal information based upon consent, you may revoke consent. Please note, if you revoke your consent for the processing of personal information then we may no longer be able to provide you services. There are certain circumstances where your requests may be limited. For example, if honoring your request would reveal information about another individual, or if you request us to delete information which we are permitted by law or our legitimate interests to keep, we reserve the right to deny your request. Please note that, as required by law, we will require you to prove your identity whenever you make a request. Depending on the type of request, we will ask for information such as your name, email, or social media profiles. We may also request that you sign a declaration confirming your identity. Once we confirm your identity, we will use reasonable efforts to supply, correct, or delete your information from our files. In some circumstances, you may designate an authorized agent to submit requests to exercise certain privacy rights on your behalf. We will require verification that you provided the authorized agent permission to make a request on your behalf and of your own identity. If you are a business submitting the request, we will require proof that you are registered with the Secretary of State to conduct business in California. If we do not receive both pieces of information, the request will be denied. How we use cookies and other tracking technologies We use common information-gather tools such as cookies and other similar tracking technologies to automatically collect information about you as you navigate our website or interact with any emails we send to you. Cookies. A cookie is a text file with small pieces of data that helps a website remember information about your visit. We use cookies to remember user settings, such as language preference, and for authentication. You can control the use of cookies through your browser settings. Please note, if you reject cookies, you may continue to use our Site, but your ability to use some features may be limited. You can read more about our cookies here . Other Tracking Technologies. As is true of most websites, we gather certain information automatically and store it in log files. This information may include internet protocol (IP) addresses, browser type, referring/exit pages, browser type and operating system, date/time stamp, and/or clickstream data. We do not link this automatically collected data to other information we collect about you. Changes to this Privacy Notice We may change this Notice from time to time. With that in mind, we ask that you continue to review it for any new updates. If we make any material changes to this Notice, we will either contact you via email to the email address specified in your account or place a conspicuous notice on our Site prior to implementation. This Notice also includes an “effective” and “last updated” date, so you can see when this version took effect and when this version was last modified, respectively. We have also included a table of “Key Changes” at the end of this Notice for your reference. How to contact us If you have any questions about this Privacy Notice, the practices of this Site, your dealings with this Site, or if you need to access this Privacy Notice in an alternative format due to having a disability, you can call us at 1 (800) 235-0187, email us at privacy@khoros.com, or write us at the following address: Khoros, LLC 7300 Ranch Road 2222, Building 3, Suite 150 Austin, TX 78730 USA If you’d like to exercise any of your rights, as described in this Privacy Notice, or if you either have an unresolved privacy or data use concern that we have not addressed satisfactorily or you disagree with our denial of a request and would like to appeal, please contact our Data Protection Officer: Jacqueline Coyne Telephone: (512) 201-4090 Email: privacy@khoros.com You may also contact our U.S.-based third party dispute resolution provider (free of charge) at https://feedback-form.truste.com/watchdog/request . If you are located in the EEA and feel that we have not able to address your complaint or concern satisfactorily, you have the right to lodge a complaint with the supervisory authority that oversees Personal Data rules in your jurisdiction. For example, in the United Kingdom, your complaint should be directed to the Information Commissioner’s Office . Other important privacy information Right to Non-Discrimination. We will not discriminate against individuals who exercise their privacy rights under applicable law. Collection of Personal Data from Children . Our Site is not directed at children. We do not knowingly collect Personal Data from children under the age of 16. If you are a parent or guardian and believe your child has provided us with Personal Data without your consent, please contact us by using the information in the “How to Contact Us” section so we can take steps to delete such Personal Data from our systems. Do Not Track. We do not currently recognize automated browser signals, which may include “Do Not Track” instructions. Blogs. Our Site offers publicly accessible blogs and Community forums. You should be aware that any information you provide in these areas may be read, collected, and used by others who access them. To request removal of your Personal Data from our blog or community forum, contact us at privacy@khoros.com. In some cases, we may not be able to remove your Personal Data. If this happens, we will let you know. Social Media Terms . By accessing our Site and using our Services, you agree to abide by the terms and conditions of Facebook , Instagram , Google , YouTube , LinkedIn , Pinterest , Twitter , TikTok , and WhatsApp . Please note that, in addition to the normal procedure for deleting stored data under YouTube's Terms of Service, users can revoke access to their data via the Google security settings page, located here . Please note that the Khoros website and Services are using YouTube API services. Social Media Widgets. Our Site includes social media features, such as buttons and widgets. These features may collect your IP address, which page you are visiting on our site, and set a cookie to enable the feature to function properly. Social media features and widgets are either hosted by a third party or hosted directly on our Site. Your interactions with these features are governed by the privacy notice of the company providing it. Accessibility. This Policy can be accessed using your browser’s audio reader capabilities. Testimonials, Comment, Idea, and Survey Submissions. We display personal testimonials from satisfied Customers and other endorsements on our Site. With your consent, we may post your testimonial along with your name. If you wish to update or delete your testimonial, please contact us at privacy@khoros.com. We consider answers to surveys, comments, ideas, and suggestions to be non-personal and do not classify them as Personal Data. Except as otherwise provided by applicable contracts with our Customers or a third party, we are free to disclose and use such data or information without any obligation. Information for residents of China We generally do not collect or process sensitive information as defined by PIPL Ch. 2 § 2, art. 28. Key changes This Notice was updated on July 20, 2023 to include information about data collected through mobile applications and information for residents of California, China, and Korea. This Notice was updated on August 2, 2024 to include information regarding required disclosures about the use of YouTube's API services. Click here to download a PDF version of this Notice. Effective Date: August 2, 2024 Home Partners Resource Center Blog Customer Stories Newsroom Events Solutions Khoros Service Social Media Management Community Services Strategic Services Professional Services Product Coaching Resources Channel Integrations Tech Integrations Developer information Community Management Software FAQs Company About Khoros Leadership Careers Social Responsibility LinkedIn Facebook Instagram Instagram Get a Demo Contact Us Privacy Disclaimer Trust Center Terms of Use Cookie Preferences IgniteTech © Khoros, LLC | 2026-01-13T09:30:11 |
https://developer.android.com/kotlin?hl=tr | Kotlin ve Android | Android Developers Ana içeriğe atla Kaçırmamanız gereken oyunlar Yapay zeka deneyimleri oluşturma Gemini API'leri ve daha fazlasıyla yapay zeka destekli Android uygulamaları geliştirin. Başlama Başlama İlk uygulamanızı oluşturarak başlayın. Eğitim kurslarımızla daha ayrıntılı bilgi edinin veya uygulama geliştirmeyi kendi kendinize öğrenin. Hello world Eğitim kursları Eğitimler Ekipler için Compose Android için Kotlin Google Play ile para kazanma ↗️ Android Geliştirici Doğrulaması Cihaza göre genişletme Kullanıcılarınıza telefondan tablete, kol saatinden kulaklığa kadar her cihazda sorunsuz deneyimler sunan uygulamalar geliştirin. Uyarlanabilir uygulamalar Android XR Wear OS Arabalar için Android Android TV ChromeOS Kategoriye göre oluşturma Google'ın yönlendirici ve kişisel görüşe dayalı rehberliğini takip ederek kullanım alanınıza uygun çözümler geliştirmeyi öğrenin. Oyunlar Kamera ve medya Sosyal ve mesajlaşma Sağlık ve form koruma Verimlilik Kurumsal uygulamalar En son sürümünü edinin Yıl boyunca yeni çıkanları takip edin, önizleme programlarımıza katılın ve geri bildirimlerinizi bizimle paylaşın. Son güncellemeler Deneysel güncellemeler Android Studio önizlemesi Jetpack ve Compose kitaplıkları Wear OS sürümleri Özel Korumalı Alan ↗️ Tasarım ve Planlama Mükemmel deneyimler En iyi kullanıcılarınız için en iyi deneyimleri oluşturun. Daha fazla bilgi Kullanıcı arayüzü tasarımı Android'deki en iyi uygulamaları kullanarak güzel bir kullanıcı arayüzü tasarlayın. Android için tasarım Cep Uyarlanabilir kullanıcı arayüzü XR Kulaklıklar ve XR Gözlükler Yapay Zeka Gözlükleri Widget'lar Wear OS Android TV Arabalar için Android Mimari Güçlü, test edilebilir ve bakımı yapılabilir uygulama mantığı ve hizmetleri tasarlayın. Giriş Kütüphaneler Gezinme Modülerleştirme Test Kotlin Multiplatform Kalite Uygulama kalitesini planlayın ve Play Store yönergelerine uyun. Genel bakış Temel değer Kullanıcı deneyimi Erişilebilirlik Teknik kalite Mükemmel deneyimler Güvenlik Kullanıcıları tehditlere karşı koruyun ve güvenli bir Android deneyimi sağlayın. Genel bakış Gizlilik İzinler Kimlik Sahtekarlığı önleme Geliştirme Android Studio'da Gemini Android geliştirmede yapay zeka geliştirme arkadaşınız. Daha fazla bilgi Android Studio'yu edinme Temel alanlar İhtiyacınız olan özelliklerle ilgili örnekleri ve dokümanları edinin. Örnekler Kullanıcı arayüzleri Arka plan çalışması Veriler ve dosyalar Bağlanabilirlik Tüm temel alanlar ⤵️ Araçlar ve iş akışı Uygulamanızı yazmak ve oluşturmak için IDE'yi kullanın veya kendi işlem hattınızı oluşturun. Kod yazma ve hata ayıklama Proje oluşturma Uygulamanızı test etme Performans Komut satırı araçları Gradle eklentisi API'si Cihaz teknolojisi Form faktörleri için kod yazma Cihazları bağlayın ve verileri paylaşın. Uyarlanabilir kullanıcı arayüzü Wear OS Android XR Android Health Arabalar için Android Android TV Tüm cihazlar ⤵️ Kütüphaneler Tüm ayrıntıları içeren API referans belgelerine göz atın. Android platformu Jetpack kitaplıkları Compose kitaplıkları Google Play Hizmetleri ↗️ Google Play SDK Dizini ↗️ Google Play Play Console Uygulamanızı veya oyununuzu yayınlayın ve Google Play'de işinizi büyütün. Play Console'a git Daha fazla bilgi ↗️ Temel Bilgiler Kullanıcılarla etkileşim kurmayı, uygulamanızdan para kazanmayı ve uygulamanızı güvenli hale getirmeyi öğrenin. Play'de para kazanma Play Integrity Play Politikaları Play Programları ↗️ Games Dev Center Oyun geliştirme ve yayınlama Araçlar, indirilenler ve örnekler Genel bakış Play Asset Delivery Play Games Hizmetleri PC Üzerinde Play Games Tüm Play rehberleri ⤵️ Kütüphaneler Tüm ayrıntıları içeren API referans belgelerine göz atın. Play Özellik Dağıtımı Play uygulama içi güncellemeleri Play uygulama içi yorumları Play Install Referrer Google Play Hizmetleri ↗️ Google Play SDK Dizini ↗️ Tüm Play kitaplıkları ⤵️ Araçlar ve kaynaklar Uygulamanızı yayınlama, tanıtma ve yönetme araçları. Android App Bundle Marka ve pazarlama Play Console API'leri ↗️ Topluluk / English Deutsch Español – América Latina Français Indonesia Italiano Polski Português – Brasil Tiếng Việt Türkçe Русский עברית العربيّة فارسی हिंदी বাংলা ภาษาไทย 中文 – 简体 中文 – 繁體 日本語 한국어 Android Studio Oturum aç Get started Kotlin Genel bakış Daha İyi Uygulamalar Derleme Örnekler Rehberler Geliştirici Hikayeleri Kaçırmamanız gereken oyunlar Diğer Genel bakış Daha İyi Uygulamalar Derleme Örnekler Rehberler Geliştirici Hikayeleri Tasarım ve Planlama Diğer Geliştirme Diğer Google Play Diğer Topluluk Android Studio Yapay zeka deneyimleri oluşturma Başlama Başlama Hello world Eğitim kursları Eğitimler Ekipler için Compose Android için Kotlin Google Play ile para kazanma ↗️ Android Geliştirici Doğrulaması Cihaza göre genişletme Uyarlanabilir uygulamalar Android XR Wear OS Arabalar için Android Android TV ChromeOS Kategoriye göre oluşturma Oyunlar Kamera ve medya Sosyal ve mesajlaşma Sağlık ve form koruma Verimlilik Kurumsal uygulamalar En son sürümünü edinin Son güncellemeler Deneysel güncellemeler Android Studio önizlemesi Jetpack ve Compose kitaplıkları Wear OS sürümleri Özel Korumalı Alan ↗️ Mükemmel deneyimler Daha fazla bilgi Kullanıcı arayüzü tasarımı Android için tasarım Cep Uyarlanabilir kullanıcı arayüzü XR Kulaklıklar ve XR Gözlükler Yapay Zeka Gözlükleri Widget'lar Wear OS Android TV Arabalar için Android Mimari Giriş Kütüphaneler Gezinme Modülerleştirme Test Kotlin Multiplatform Kalite Genel bakış Temel değer Kullanıcı deneyimi Erişilebilirlik Teknik kalite Mükemmel deneyimler Güvenlik Genel bakış Gizlilik İzinler Kimlik Sahtekarlığı önleme Android Studio'da Gemini Daha fazla bilgi Android Studio'yu edinme Temel alanlar Örnekler Kullanıcı arayüzleri Arka plan çalışması Veriler ve dosyalar Bağlanabilirlik Tüm temel alanlar ⤵️ Araçlar ve iş akışı Kod yazma ve hata ayıklama Proje oluşturma Uygulamanızı test etme Performans Komut satırı araçları Gradle eklentisi API'si Cihaz teknolojisi Uyarlanabilir kullanıcı arayüzü Wear OS Android XR Android Health Arabalar için Android Android TV Tüm cihazlar ⤵️ Kütüphaneler Android platformu Jetpack kitaplıkları Compose kitaplıkları Google Play Hizmetleri ↗️ Google Play SDK Dizini ↗️ Play Console Play Console'a git Daha fazla bilgi ↗️ Temel Bilgiler Play'de para kazanma Play Integrity Play Politikaları Play Programları ↗️ Games Dev Center Genel bakış Play Asset Delivery Play Games Hizmetleri PC Üzerinde Play Games Tüm Play rehberleri ⤵️ Kütüphaneler Play Özellik Dağıtımı Play uygulama içi güncellemeleri Play uygulama içi yorumları Play Install Referrer Google Play Hizmetleri ↗️ Google Play SDK Dizini ↗️ Tüm Play kitaplıkları ⤵️ Araçlar ve kaynaklar Android App Bundle Marka ve pazarlama Play Console API'leri ↗️ Android Developers Get started Kotlin Koleksiyonlar ile düzeninizi koruyun İçeriği tercihlerinize göre kaydedin ve kategorilere ayırın. Kotlin ile Android uygulamaları geliştirme Kotlin ile daha iyi Android uygulamalarını daha hızlı yazın. Kotlin, profesyonel Android geliştiricilerinin% 60'ından fazlası tarafından kullanılan ve üretkenliği, geliştirici memnuniyetini ve kod güvenliğini artırmaya yardımcı olan, statik olarak yazılmış modern bir programlama dilidir. Başlama Anlamlı ve kısa Kotlin'in modern dil özellikleri, fikirlerinizi ifade etmeye odaklanmanıza ve daha az ortak metin kod yazmanıza olanak tanır. Daha fazla bilgi Daha güvenli kod Tür sistemine null değer eklenmesi sayesinde Kotlin, NullPointerExceptions'dan kaçınmanıza yardımcı olur. Kotlin kullanan Android uygulamalarının kilitlenme olasılığı% 20 daha düşüktür. Daha fazla bilgi Jetpack Compose Android'in modern kullanıcı arayüzü araç seti Kotlin üzerine kuruludur. Bu sayede güçlü ve sezgisel API'lerle uyarlanabilir kullanıcı arayüzlerini hızlı bir şekilde oluşturabilirsiniz. Daha fazla bilgi Kotlin Multiplatform Kotlin Multiplatform ile Android, iOS ve masaüstü platformlarında kod paylaşın. Daha fazla bilgi Başlangıç gün başlıyor Android ve Kotlin'i sıfırdan öğrenme Kotlin ve Jetpack Compose ile Android uygulamaları geliştirmeyi öğreten, yeni başlayanlara yönelik kılavuzlarımızı inceleyin. gün başlıyor Android Java geliştiricileri için Kotlin Java'yı zaten biliyorsanız birlikte çalışabilirlik kılavuzlarımız ve dokümanlarımız, başlamanıza yardımcı olabilir. gün başlıyor Gelişmiş Kotlin kılavuzları Kotlin'e aşinaysanız becerilerinizi geliştirmek için gelişmiş belgelerimizi okuyun. gün başlıyor Kotlin'i ekibinize getirin Kotlin ile yazmanın ekibinizin üretkenliğini nasıl artırabileceğini, uygulama kalitesini nasıl iyileştirebileceğini ve geliştirici memnuniyetini nasıl artırabileceğini öğrenin. Kotlin için optimize edildi Kotlin, başarılı olmanıza yardımcı olacak araçlar ve kaynaklarla Android geliştirme için tamamen desteklenmektedir. Android Studio Android Studio, Kotlin için birinci sınıf destek sağlar. Java tabanlı kodu Kotlin'e dönüştürmenize yardımcı olacak yerleşik araçlar bile içerir. Kotlin Bytecode'u Göster aracı, Kotlin'i öğrenirken eşdeğer Java tabanlı kodu görmenizi sağlar. İndir Android KTX Android KTX, Kotlin dili özelliklerinden yararlanarak Kotlin ile Android geliştirme sürecini daha kısa ve öz, daha hoş ve deyimsel hale getiriyor. Daha fazla bilgi Kotlin uyumlu SDK Android 9'dan (API düzeyi 28) başlayarak Android SDK, NullPointerExceptions'ı önlemeye yardımcı olmak için null değer ek açıklamaları içerir. API referans belgeleri Kotlin'de de mevcuttur. Belgeleri göster Eğitici kaynaklar Kotlin'i öğrenmeye hızlı bir başlangıç yapmanız için çeşitli biçimlerde özenle seçilmiş bir dizi kaynağı keşfedin. Kaynakları inceleyin Kotlin kodu neye benzer? Kotlin ile geliştirilen uygulamalar En yeni startup'lardan Fortune 500 şirketlerine kadar birçok uygulama Kotlin ile geliştirilmiştir. Kotlin'in, ekiplerinin daha üretken olmasına ve daha kaliteli uygulamalar yazmasına nasıl yardımcı olduğunu öğrenin. Geliştirici hikayelerini göster Geliştirici hikayesi Zomato, daha güvenli ve kısa ve öz kod yazmak için Kotlin'i kullanıyor Kotlin, Zomato'nun uygulamasındaki kod satırının sayısını önemli ölçüde azaltmasına ve derleme sırasında uygulamasında önemli kusurlar bulmasına da yardımcı oldu. Ürün Yönetimi Başkan Yardımcısı Rahul, Ürün Yönetimi Başkan Yardımcısı ve Android geliştiricisi Prateek Sharma'nın Zomato'nun Kotlin'i benimsemeye nasıl başladığını ve bu özelliği tüm yeni özellik sürümlerinde nasıl kullandıklarını izleyin. Öne çıkanlar Kotlin açık kaynaktır Kotlin, Apache 2.0 lisansı kapsamında ücretsiz olarak kullanılabilen açık kaynaklı bir projedir. Proje kodu, öncelikli olarak JetBrains'de çalışan ekip tarafından, Google ve diğer kuruluşların katkılarıyla GitHub'da açık bir şekilde geliştirilmiştir. Kotlin'i seçmemiz, Android platformunu geliştirip büyütürken açık geliştirici ekosistemine olan bağlılığımızı bir kez daha gösteriyor ve dilin evrildiğini görmek için sabırsızlanıyoruz. GitHub'da Kotlin'i görün Öne çıkan kaynaklar Kotlin'de Android codelab'leri Kotlin'de Android codelab'leri ile güncel en iyi uygulamaları ve API'leri öğrenin. Eş yordamlar Manzaralı oda Kotlin'e göre yeniden düzenleme Medium'da Android ve Kotlin Android ekibi tarafından Kotlin hakkında teknik makaleler. Makaleleri keşfedin E-posta Yazma ile İlgili Temel Bilgiler kursu Programlama deneyimi olmayanlar, Kotlin programlama dilinin temellerini ve basit Android uygulamaları geliştirmeyi öğrenebilir. Kursu başlat Kotlin dili belgeleri Kotlin oyun alanı Kotlin'i hemen web tarayıcınızda kullanmayı deneyin. Hemen Dene Resmi dil referansı Resmi dil referans sitesinden Kotlin öğrenmeye başlayın. Kaynağı görüntüle [[["Anlaması kolay","easyToUnderstand","thumb-up"],["Sorunumu çözdü","solvedMyProblem","thumb-up"],["Diğer","otherUp","thumb-up"]],[["İhtiyacım olan bilgiler yok","missingTheInformationINeed","thumb-down"],["Çok karmaşık / çok fazla adım var","tooComplicatedTooManySteps","thumb-down"],["Güncel değil","outOfDate","thumb-down"],["Çeviri sorunu","translationIssue","thumb-down"],["Örnek veya kod sorunu","samplesCodeIssue","thumb-down"],["Diğer","otherDown","thumb-down"]],[],[],[]] X X'te @AndroidDev'i takip edin YouTube YouTube'da Android Developers'a göz atın LinkedIn Connect with the Android Developers community on LinkedIn Android hakkında daha fazla Android İşletmeler için Android Güvenlik Kaynak Haber Blog Podcast'ler Keşfet Oyun Makine Öğrenimi Sağlık ve Fitness Kamera ve Medya Gizlilik 5G Android Cihazlar Büyük ekranlar Wear OS ChromeOS cihazlar Arabalar için Android Android TV Sürümler Android 15 Android 14 Android 13 Android 12 Android 11 Android 10 Pie Belgeler ve İndirmeler Android Studio kılavuzu Geliştirici kılavuzları API referansı Studio'yu indir Android NDK Destek Platform hatası bildir Belge hatası bildir Google Play support Araştırma çalışmalarına katıl Android Chrome Firebase Google Cloud Platform Tüm ürünler Gizlilik Lisans Marka kuralları Manage cookies E-postayla haberler ve ipuçları al Abone ol English Deutsch Español – América Latina Français Indonesia Italiano Polski Português – Brasil Tiếng Việt Türkçe Русский עברית العربيّة فارسی हिंदी বাংলা ภาษาไทย 中文 – 简体 中文 – 繁體 日本語 한국어 | 2026-01-13T09:30:11 |
https://developers.google.com/admob/api/reference/rest/v1beta/accounts.adUnits/create | Method: accounts.adUnits.create | AdMob API | Google for Developers Skip to main content AdMob API / English Deutsch Español Español – América Latina Français Indonesia Italiano Polski Português – Brasil Tiếng Việt Türkçe Русский עברית العربيّة فارسی हिंदी বাংলা ภาษาไทย 中文 – 简体 中文 – 繁體 日本語 한국어 Sign in AdMob Guides Reference Libraries & Examples Support AdMob API AdMob Guides Reference Libraries & Examples Support Release notes AdMob API v1 REST Resources accounts Overview get list accounts.adUnits Overview list accounts.apps Overview list accounts.mediationReport Overview generate accounts.networkReport Overview generate Types DateRange LocalizationSettings ReportFooter ReportHeader ReportRow SortOrder StringList v1beta REST Resources accounts Overview get list accounts.adSources Overview list accounts.adSources.adapters Overview list accounts.adUnitMappings Overview batchCreate accounts.adUnits Overview create list accounts.adUnits.adUnitMappings Overview create list accounts.apps Overview create list accounts.campaignReport Overview generate accounts.mediationGroups Overview create list patch accounts.mediationGroups.mediationAbExperiments Overview create stop accounts.mediationReport Overview generate accounts.networkReport Overview generate Types DateRange LocalizationSettings MediationGroupLine ReportFooter ReportHeader ReportRow SortOrder StringList API dictionary Ad sources Adapters Home Products AdMob API Reference Method: accounts.adUnits.create Stay organized with collections Save and categorize content based on your preferences. Page Summary outlined_flag This method creates an ad unit under a specified AdMob account. The HTTP request uses a POST method to the specified URL. The request requires a parent parameter in the path, which is the resource name of the account. The request body contains an instance of AdUnit , and the successful response body contains a newly created AdUnit . The method requires the https://www.googleapis.com/auth/admob.monetization authorization scope. HTTP request Path parameters Request body Response body Authorization scopes Examples Try it! Creates an ad unit under the specified AdMob account. This method has limited access. If you see a 403 permission denied error, please reach out to your account manager for access. HTTP request POST https://admob.googleapis.com/v1beta/{parent=accounts/*}/adUnits The URL uses gRPC Transcoding syntax. Path parameters Parameters parent string Required. Resource name of the account to create the specified ad unit for. Example: accounts/pub-9876543210987654 Request body The request body contains an instance of AdUnit . Response body If successful, the response body contains a newly created instance of AdUnit . Authorization scopes Requires the following OAuth scope: https://www.googleapis.com/auth/admob.monetization For more information, see the OAuth 2.0 Overview . Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License , and code samples are licensed under the Apache 2.0 License . For details, see the Google Developers Site Policies . Java is a registered trademark of Oracle and/or its affiliates. Last updated 2025-08-20 UTC. [[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-20 UTC."],[],["This document details the process for creating an ad unit within an AdMob account. It uses a `POST` HTTP request to `https://admob.googleapis.com/v1beta/{parent=accounts/*}/adUnits`, where `parent` specifies the account. The request body requires an `AdUnit` instance, and a successful request returns a new `AdUnit` instance in the response body. Authorization requires the `https://www.googleapis.com/auth/admob.monetization` OAuth scope. Access is limited, potentially requiring account manager intervention for permission.\n"]] Product info Usage limits Pricing Terms of Service Programs Google Developer Program Google Developer Groups Google Developer Experts Accelerators Google Cloud & NVIDIA Developer consoles Google API Console Google Cloud Platform Console Google Play Console Firebase Console Actions on Google Console Cast SDK Developer Console Chrome Web Store Dashboard Google Home Developer Console Android Chrome Firebase Google Cloud Platform Google AI All products Terms Privacy Manage cookies English Deutsch Español Español – América Latina Français Indonesia Italiano Polski Português – Brasil Tiếng Việt Türkçe Русский עברית العربيّة فارسی हिंदी বাংলা ภาษาไทย 中文 – 简体 中文 – 繁體 日本語 한국어 | 2026-01-13T09:30:11 |
https://developers.google.com/admob/api/reference/rest/v1beta/accounts.campaignReport/generate | Method: accounts.campaignReport.generate | AdMob API | Google for Developers Skip to main content AdMob API / English Deutsch Español Español – América Latina Français Indonesia Italiano Polski Português – Brasil Tiếng Việt Türkçe Русский עברית العربيّة فارسی हिंदी বাংলা ภาษาไทย 中文 – 简体 中文 – 繁體 日本語 한국어 Sign in AdMob Guides Reference Libraries & Examples Support AdMob API AdMob Guides Reference Libraries & Examples Support Release notes AdMob API v1 REST Resources accounts Overview get list accounts.adUnits Overview list accounts.apps Overview list accounts.mediationReport Overview generate accounts.networkReport Overview generate Types DateRange LocalizationSettings ReportFooter ReportHeader ReportRow SortOrder StringList v1beta REST Resources accounts Overview get list accounts.adSources Overview list accounts.adSources.adapters Overview list accounts.adUnitMappings Overview batchCreate accounts.adUnits Overview create list accounts.adUnits.adUnitMappings Overview create list accounts.apps Overview create list accounts.campaignReport Overview generate accounts.mediationGroups Overview create list patch accounts.mediationGroups.mediationAbExperiments Overview create stop accounts.mediationReport Overview generate accounts.networkReport Overview generate Types DateRange LocalizationSettings MediationGroupLine ReportFooter ReportHeader ReportRow SortOrder StringList API dictionary Ad sources Adapters Home Products AdMob API Reference Method: accounts.campaignReport.generate Stay organized with collections Save and categorize content based on your preferences. Page Summary outlined_flag The endpoint POST https://admob.googleapis.com/v1beta/{parent=accounts/*}/campaignReport:generate is used to generate a campaign report. The report generation requires specifying a reportSpec in the request body, which includes details like date range, dimensions, and metrics. The dimensions define how the report data is sliced (e.g., by campaign ID, date, country). The metrics define the performance indicators included in the report (e.g., impressions, clicks, installs). The response body contains the generated report data in rows, with each row representing a combination of the specified dimensions and their corresponding metric values. HTTP request Path parameters Request body JSON representation Response body JSON representation Authorization scopes CampaignReportSpec JSON representation Dimension Metric Examples Try it! Generates Campaign Report based on provided specifications. HTTP request POST https://admob.googleapis.com/v1beta/{parent=accounts/*}/campaignReport:generate The URL uses gRPC Transcoding syntax. Path parameters Parameters parent string Resource name of the account to generate the report for. Example: accounts/pub-9876543210987654 Request body The request body contains data with the following structure: JSON representation { "reportSpec" : { object ( CampaignReportSpec ) } } Fields reportSpec object ( CampaignReportSpec ) Campaign report specification. Response body Campaign Report API response. If successful, the response body contains data with the following structure: JSON representation { "rows" : [ { object ( ReportRow ) } ] } Fields rows[] object ( ReportRow ) The campaign report data from the specified publisher. At most 100000 rows will be returned from the API. Authorization scopes Requires one of the following OAuth scopes: https://www.googleapis.com/auth/admob.readonly https://www.googleapis.com/auth/admob.report For more information, see the OAuth 2.0 Overview . CampaignReportSpec The specification for generating a Campaign report. For example, the specification to get IMPRESSIONS and CLICKS sliced by CAMPAIGN_ID can look like the following example: { "dateRange": { "startDate": {"year": 2021, "month": 12, "day": 1}, "endDate": {"year": 2021, "month": 12, "day": 30} }, "dimensions": ["CAMPAIGN_ID"], "metrics": ["IMPRESSIONS", "CLICKS"], } JSON representation { "dateRange" : { object ( DateRange ) } , "dimensions" : [ enum ( Dimension ) ] , "metrics" : [ enum ( Metric ) ] , "languageCode" : string } Fields dateRange object ( DateRange ) The date range for which the report is generated. The max range is 30 days. dimensions[] enum ( Dimension ) List of dimensions of the report. The value combination of these dimensions determines the row of the report. If no dimensions are specified, the report returns a single row of requested metrics for the entire account. metrics[] enum ( Metric ) List of metrics of the report. A report must specify at least one metric. languageCode string Language used for any localized text, such as certain applicable dimension values. The language tag is defined in the IETF BCP47. Defaults to 'en-US' if unspecified or invalid. Dimension The dimensions of the campaign report. Enums DIMENSION_UNSPECIFIED Default value of an unspecified dimension. Do not use. DATE A date in the YYYYMMDD format (for example, "20210701"). CAMPAIGN_ID The unique ID of the campaign, for example "123456789", which is consistent with the campaign id from campaign list api. CAMPAIGN_NAME The name of the campaign. AD_ID The unique ID of the ad, for example "123456789". AD_NAME The name of the ad, which may not be unique. PLACEMENT_ID The vendor-specific unique ID of the app where the ad is placed. For example, com.goog.bar for Android and 123456789 for iOS apps. PLACEMENT_NAME The name of the app where the ad is placed. PLACEMENT_PLATFORM The platform of the app where the ad is placed. COUNTRY The name of the targeted country. FORMAT Format of the ad unit (for example, "banner", "native"), an ad delivery dimension. Metric The metrics of the campaign report. Enums METRIC_UNSPECIFIED Default value for an unset field. Do not use. IMPRESSIONS The number of times an ad is shown to the user. CLICKS The number of times a user clicks an ad. CLICK_THROUGH_RATE The number of clicks an ad receives divided by the number of times the ad is shown. INSTALLS The number of times apps were downloaded to devices. ESTIMATED_COST The estimated cost of serving a campaign ad instead of an ad that earns revenue. The currency is the reporting currency for campaigns. AVERAGE_CPI The average cost per install. This means the average amount that was spent to acquire a new user. The currency is the reporting currency for campaigns. INTERACTIONS The number of times a user interacts with an ad. This consists of clicks and engagements. Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License , and code samples are licensed under the Apache 2.0 License . For details, see the Google Developers Site Policies . Java is a registered trademark of Oracle and/or its affiliates. Last updated 2025-08-20 UTC. [[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-20 UTC."],[],["This document outlines the process for generating a Campaign Report via an API. A `POST` request is sent to a specified URL with a `parent` path parameter (account ID). The request body includes a `reportSpec` object containing `dateRange`, `dimensions` (e.g., `CAMPAIGN_ID`, `DATE`), `metrics` (e.g., `IMPRESSIONS`, `CLICKS`), and optional `languageCode`. The response provides an array of `rows` containing the report data, with up to 100,000 rows. The request requires specific authorization scopes.\n"]] Product info Usage limits Pricing Terms of Service Programs Google Developer Program Google Developer Groups Google Developer Experts Accelerators Google Cloud & NVIDIA Developer consoles Google API Console Google Cloud Platform Console Google Play Console Firebase Console Actions on Google Console Cast SDK Developer Console Chrome Web Store Dashboard Google Home Developer Console Android Chrome Firebase Google Cloud Platform Google AI All products Terms Privacy Manage cookies English Deutsch Español Español – América Latina Français Indonesia Italiano Polski Português – Brasil Tiếng Việt Türkçe Русский עברית العربيّة فارسی हिंदी বাংলা ภาษาไทย 中文 – 简体 中文 – 繁體 日本語 한국어 | 2026-01-13T09:30:11 |
https://developers.cloudflare.com/ai-gateway/observability/logging/logpush/ | Workers Logpush · Cloudflare AI Gateway docs Skip to content Cloudflare Docs Search Docs Directory APIs SDKs Help Log in Select theme Dark Light Auto AI Gateway No results found. Try a different search term, or use our global search . Overview Getting started Using AI Gateway Unified API (OpenAI compat) Provider Native Workers AI Amazon Bedrock Anthropic Azure OpenAI Baseten Cartesia Cerebras Cohere Deepgram DeepSeek ElevenLabs Fal AI Google AI Studio Google Vertex AI Groq HuggingFace Ideogram Mistral AI OpenAI OpenRouter Parallel Perplexity Replicate xAI WebSockets API Beta Overview Realtime WebSockets API Non-realtime WebSockets API Features Overview Unified Billing Caching Rate limiting Dynamic routing Beta Overview Using a dynamic route JSON Configuration Data Loss Prevention (DLP) Beta Overview Set up Data Loss Prevention (DLP) Guardrails Beta Overview Set up Guardrails Supported model types Usage considerations Configuration BYOK (Store Keys) Beta Custom costs Custom Providers Beta Manage gateways Request handling Authenticated Gateway Observability Costs Custom metadata Analytics Logging Overview Workers Logpush Integrations Vercel AI SDK Agents ↗ AI Gateway Binding Methods Workers AI Tutorials Platform Overview Limits Pricing Audit logs Changelog Header Glossary REST API reference ↗ API MCP server ↗ MCP AI Assistant ↗ Architectures LLM resources llms.txt prompt.txt AI Gateway llms-full.txt Developer Platform llms-full.txt GitHub X.com YouTube Select theme Dark Light Auto On this page Overview How logs are encrypted Setting up Workers Logpush 1. Generate an RSA key pair locally 2. Upload public key to gateway settings 3. Set up Logpush 4. Receive encrypted logs 5. Decrypt logs On this page Overview How logs are encrypted Setting up Workers Logpush 1. Generate an RSA key pair locally 2. Upload public key to gateway settings 3. Set up Logpush 4. Receive encrypted logs 5. Decrypt logs Was this helpful? Edit Issue Directory … AI Gateway Observability Logging Workers Logpush Copy page Workers Logpush AI Gateway allows you to securely export logs to an external storage location, where you can decrypt and process them. You can toggle Workers Logpush on and off in the Cloudflare dashboard ↗ settings. This product is available on the Workers Paid plan. For pricing information, refer to Pricing . This guide explains how to set up Workers Logpush for AI Gateway, generate an RSA key pair for encryption, and decrypt the logs once they are received. You can store up to 10 million logs per gateway. If your limit is reached, new logs will stop being saved and will not be exported through Workers Logpush. To continue saving and exporting logs, you must delete older logs to free up space for new logs. Workers Logpush has a limit of 4 jobs and a maximum request size of 1 MB per log. Note To export logs using Workers Logpush, you must have logs turned on for the gateway. Need a higher limit? To request an increase to a limit, complete the Limit Increase Request Form ↗ . If the limit can be increased, Cloudflare will contact you with next steps. How logs are encrypted We employ a hybrid encryption model efficiency and security. Initially, an AES key is generated for each log. This AES key is what actually encrypts the bulk of your data, chosen for its speed and security in handling large datasets efficiently. Now, for securely sharing this AES key, we use RSA encryption. Here's what happens: the AES key, although lightweight, needs to be transmitted securely to the recipient. We encrypt this key with the recipient's RSA public key. This step leverages RSA's strength in secure key distribution, ensuring that only someone with the corresponding RSA private key can decrypt and use the AES key. Once encrypted, both the AES-encrypted data and the RSA-encrypted AES key are sent together. Upon arrival, the recipient's system uses the RSA private key to decrypt the AES key. With the AES key now accessible, it is straightforward to decrypt the main data payload. This method combines the best of both worlds: the efficiency of AES for data encryption with the secure key exchange capabilities of RSA, ensuring data integrity, confidentiality, and performance are all optimally maintained throughout the data lifecycle. Setting up Workers Logpush To configure Workers Logpush for AI Gateway, follow these steps: 1. Generate an RSA key pair locally You need to generate a key pair to encrypt and decrypt the logs. This script will output your RSA privateKey and publicKey. Keep the private key secure, as it will be used to decrypt the logs. Below is a sample script to generate the keys using Node.js and OpenSSL. JavaScript OpenSSL JavaScript const crypto = require ( "crypto" ) ; const { privateKey , publicKey } = crypto . generateKeyPairSync ( "rsa" , { modulusLength : 4096 , publicKeyEncoding : { type : "spki" , format : "pem" , }, privateKeyEncoding : { type : "pkcs8" , format : "pem" , }, } ) ; console . log ( publicKey ) ; console . log ( privateKey ) ; Run the script by executing the below code on your terminal. Replace file name with the name of your JavaScript file. Terminal window node {file name} Generate private key: Use the following command to generate a RSA private key: Terminal window openssl genpkey -algorithm RSA -out private_key.pem -pkeyopt rsa_keygen_bits:4096 Generate public key: After generating the private key, you can extract the corresponding public key using: Terminal window openssl rsa -pubout -in private_key.pem -out public_key.pem 2. Upload public key to gateway settings Once you have generated the key pair, upload the public key to your AI Gateway settings. This key will be used to encrypt your logs. In order to enable Workers Logpush, you will need logs enabled for that gateway. 3. Set up Logpush To set up Logpush, refer to Logpush documentation. 4. Receive encrypted logs After configuring Workers Logpush, logs will be sent encrypted using the public key you uploaded. To access the data, you will need to decrypt it using your private key. The logs will be sent to the object storage provider that you have selected. 5. Decrypt logs To decrypt the encrypted log bodies and metadata from AI Gateway, you can use the following Node.js script or OpenSSL: JavaScript OpenSSL To decrypt the encrypted log bodies and metadata from AI Gateway, download the logs to a folder, in this case its named my_log.log.gz . Then copy this JavaScript file into the same folder and place your private key in the top variable. JavaScript const privateKeyStr = `-----BEGIN RSA PRIVATE KEY----- .... -----END RSA PRIVATE KEY-----` ; const crypto = require ( "crypto" ) ; const privateKey = crypto . createPrivateKey ( privateKeyStr ) ; const fs = require ( "fs" ) ; const zlib = require ( "zlib" ) ; const readline = require ( "readline" ) ; async function importAESGCMKey ( keyBuffer ) { try { // Ensure the key length is valid for AES if ([ 128 , 192 , 256 ] . includes ( 256 )) { return await crypto . webcrypto . subtle . importKey ( "raw" , keyBuffer , { name : "AES-GCM" , length : 256 , }, true , // Whether the key is extractable (true in this case to allow for export later if needed) [ "encrypt" , "decrypt" ] , // Use for encryption and decryption ) ; } else { throw new Error ( "Invalid AES key length. Must be 128, 12, or 256 bits." ) ; } } catch ( error ) { console . error ( "Failed to import key:" , error ) ; throw error ; } } async function decryptData ( encryptedData , aesKey , iv ) { const decryptedData = await crypto . subtle . decrypt ( { name : "AES-GCM" , iv : iv }, aesKey , encryptedData , ) ; return new TextDecoder () . decode ( decryptedData ) ; } async function decryptBase64 ( privateKey , data ) { if ( data . key === undefined ) { return data ; } const aesKeyBuf = crypto . privateDecrypt ( { key : privateKey , oaepHash : "SHA256" , }, Buffer . from ( data . key , "base64" ) , ) ; const aesKey = await importAESGCMKey ( aesKeyBuf ) ; const decryptedData = await decryptData ( Buffer . from ( data . data , "base64" ) , aesKey , Buffer . from ( data . iv , "base64" ) , ) ; return decryptedData . toString () ; } async function run () { let lineReader = readline . createInterface ( { input : fs . createReadStream ( "my_log.log.gz" ) . pipe ( zlib . createGunzip ()) , } ) ; lineReader . on ( "line" , async ( line ) => { line = JSON . parse ( line ) ; const { Metadata , RequestBody , ResponseBody , ... remaining } = line ; console . log ( { ... remaining , Metadata : await decryptBase64 ( privateKey , Metadata ) , RequestBody : await decryptBase64 ( privateKey , RequestBody ) , ResponseBody : await decryptBase64 ( privateKey , ResponseBody ) , } ) ; console . log ( "--" ) ; } ) ; } run () ; { line = JSON.parse(line); const { Metadata, RequestBody, ResponseBody, ...remaining } = line; console.log({ ...remaining, Metadata: await decryptBase64(privateKey, Metadata), RequestBody: await decryptBase64(privateKey, RequestBody), ResponseBody: await decryptBase64(privateKey, ResponseBody), }); console.log("--"); });}run();"> Run the script by executing the below code on your terminal. Replace file name with the name of your JavaScript file. Terminal window node {file name} The script reads the encrypted log file (my_log.log.gz) , decrypts the metadata, request body, and response body, and prints the decrypted data. Ensure you replace the privateKey variable with your actual private RSA key that you generated in step 1. Decrypt the encrypted log file using the private key. Assuming that the logs were encrypted with the public key (for example public_key.pem ), you can use the private key ( private_key.pem ) to decrypt the log file. For example, if the encrypted logs are in a file named encrypted_logs.bin , you can decrypt it like this: Terminal window openssl rsautl -decrypt -inkey private_key.pem -in encrypted_logs.bin -out decrypted_logs.txt -decrypt tells OpenSSL that we want to decrypt the file. -inkey private_key.pem specifies the private key that will be used to decrypt the logs. -in encrypted_logs.bin is the encrypted log file. -out decrypted_logs.txt decrypted logs will be saved into this file. View the decrypted logs Once decrypted, you can view the logs by simply running: Terminal window cat decrypted_logs.txt This command will output the decrypted logs to the terminal. Was this helpful? Edit page Last updated: Jul 24, 2025 Previous Logging Next Vercel AI SDK Resources API New to Cloudflare? Directory Sponsorships Open Source Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Speed Test Is BGP Safe Yet? RPKI Toolkit Certificate Transparency Community X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings | 2026-01-13T09:30:11 |
https://developers.google.com/admob/api/reference/rest/v1beta/accounts.adUnitMappings | REST Resource: accounts.adUnitMappings | AdMob API | Google for Developers Skip to main content AdMob API / English Deutsch Español Español – América Latina Français Indonesia Italiano Polski Português – Brasil Tiếng Việt Türkçe Русский עברית العربيّة فارسی हिंदी বাংলা ภาษาไทย 中文 – 简体 中文 – 繁體 日本語 한국어 Sign in AdMob Guides Reference Libraries & Examples Support AdMob API AdMob Guides Reference Libraries & Examples Support Release notes AdMob API v1 REST Resources accounts Overview get list accounts.adUnits Overview list accounts.apps Overview list accounts.mediationReport Overview generate accounts.networkReport Overview generate Types DateRange LocalizationSettings ReportFooter ReportHeader ReportRow SortOrder StringList v1beta REST Resources accounts Overview get list accounts.adSources Overview list accounts.adSources.adapters Overview list accounts.adUnitMappings Overview batchCreate accounts.adUnits Overview create list accounts.adUnits.adUnitMappings Overview create list accounts.apps Overview create list accounts.campaignReport Overview generate accounts.mediationGroups Overview create list patch accounts.mediationGroups.mediationAbExperiments Overview create stop accounts.mediationReport Overview generate accounts.networkReport Overview generate Types DateRange LocalizationSettings MediationGroupLine ReportFooter ReportHeader ReportRow SortOrder StringList API dictionary Ad sources Adapters Home Products AdMob API Reference REST Resource: accounts.adUnitMappings Stay organized with collections Save and categorize content based on your preferences. Resource Methods Resource There is no persistent data associated with this resource. Methods batchCreate Batch create the ad unit mappings under the specific AdMob account. Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License , and code samples are licensed under the Apache 2.0 License . For details, see the Google Developers Site Policies . Java is a registered trademark of Oracle and/or its affiliates. Last updated 2025-08-20 UTC. [[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-20 UTC."],[],["The content describes a resource with no persistent data. The key action presented is the ability to batch create ad unit mappings under a specific AdMob account. This functionality is accessed via the `batchCreate` method, detailed under `accounts.adUnitMappings`. The resource itself lacks stored information, serving primarily as a container for managing these ad unit mappings.\n"]] Product info Usage limits Pricing Terms of Service Programs Google Developer Program Google Developer Groups Google Developer Experts Accelerators Google Cloud & NVIDIA Developer consoles Google API Console Google Cloud Platform Console Google Play Console Firebase Console Actions on Google Console Cast SDK Developer Console Chrome Web Store Dashboard Google Home Developer Console Android Chrome Firebase Google Cloud Platform Google AI All products Terms Privacy Manage cookies English Deutsch Español Español – América Latina Français Indonesia Italiano Polski Português – Brasil Tiếng Việt Türkçe Русский עברית العربيّة فارسی हिंदी বাংলা ภาษาไทย 中文 – 简体 中文 – 繁體 日本語 한국어 | 2026-01-13T09:30:12 |
https://developers.cloudflare.com/ai-gateway/features/dynamic-routing/json-configuration/ | JSON Configuration · Cloudflare AI Gateway docs Skip to content Cloudflare Docs Search Docs Directory APIs SDKs Help Log in Select theme Dark Light Auto AI Gateway No results found. Try a different search term, or use our global search . Overview Getting started Using AI Gateway Unified API (OpenAI compat) Provider Native Workers AI Amazon Bedrock Anthropic Azure OpenAI Baseten Cartesia Cerebras Cohere Deepgram DeepSeek ElevenLabs Fal AI Google AI Studio Google Vertex AI Groq HuggingFace Ideogram Mistral AI OpenAI OpenRouter Parallel Perplexity Replicate xAI WebSockets API Beta Overview Realtime WebSockets API Non-realtime WebSockets API Features Overview Unified Billing Caching Rate limiting Dynamic routing Beta Overview Using a dynamic route JSON Configuration Data Loss Prevention (DLP) Beta Overview Set up Data Loss Prevention (DLP) Guardrails Beta Overview Set up Guardrails Supported model types Usage considerations Configuration BYOK (Store Keys) Beta Custom costs Custom Providers Beta Manage gateways Request handling Authenticated Gateway Observability Costs Custom metadata Analytics Logging Overview Workers Logpush Integrations Vercel AI SDK Agents ↗ AI Gateway Binding Methods Workers AI Tutorials Platform Overview Limits Pricing Audit logs Changelog Header Glossary REST API reference ↗ API MCP server ↗ MCP AI Assistant ↗ Architectures LLM resources llms.txt prompt.txt AI Gateway llms-full.txt Developer Platform llms-full.txt GitHub X.com YouTube Select theme Dark Light Auto On this page Overview Supported elements Start Element Conditional Element (If/Else) Percentage Split Rate/Budget Limit Model End element On this page Overview Supported elements Start Element Conditional Element (If/Else) Percentage Split Rate/Budget Limit Model End element Was this helpful? Edit Issue Directory … AI Gateway Features Dynamic routing JSON Configuration Copy page JSON Configuration Instead of using the dashboard editor UI to define the route graph, you can do it using the REST API. Routes are internally represented using a simple JSON structure: { " id " : "<route id>" , " name " : "<route name>" , " elements " : [ <array of elements> ] } ", "name": " ", "elements": [ ]}"> Supported elements Dynamic routing supports several types of elements that you can combine to create sophisticated routing flows. Each element has specific inputs, outputs, and configuration options. Start Element Marks the beginning of a route. Every route must start with a Start element. Inputs : None Outputs : next : Forwards the unchanged request to the next element { " id " : "<id>" , " type " : "start" , " outputs " : { " next " : { " elementId " : "<id>" } } } ", "type": "start", "outputs": { "next": { "elementId": " " } }}"> Conditional Element (If/Else) Evaluates a condition based on request parameters and routes the request accordingly. Inputs : Request Outputs : true : Forwards request to provided element if condition evaluates to true false : Forwards request to provided element if condition evaluates to false { " id " : "<id>" , " type " : "conditional" , " properties " : { " condition " : { " metadata.plan " : { " $eq " : "free" } // Supports MongoDB-like operators } }, " outputs " : { " true " : { " elementId " : "<id>" }, " false " : { " elementId " : "<id>" } } } ", "type": "conditional", "properties": { "condition": { "metadata.plan": { "$eq": "free" } // Supports MongoDB-like operators } }, "outputs": { "true": { "elementId": " " }, "false": { "elementId": " " } }}"> Percentage Split Routes requests probabilistically across multiple outputs, useful for A/B testing and gradual rollouts. Inputs : Request Outputs : Up to 5 named percentage outputs, plus an optional else fallback Each output has a fractional probability (must total 100%) else output handles remaining percentage if other branches don't sum to 100% { " id " : "<id>" , " type " : "percentage" , " outputs " : { " 10% " : { " elementId " : "<id>" }, " 50% " : { " elementId " : "<id>" }, " else " : { " elementId " : "<id>" } } } ", "type": "percentage", "outputs": { "10%": { "elementId": " " }, "50%": { "elementId": " " }, "else": { "elementId": " " } }}"> Rate/Budget Limit Apply limits based on request metadata. Supports both count-based and cost-based limits. Inputs : Request Outputs : success : Forwards request to provided element if request is not rate limited fallback : Optional output for rate-limited requests (route terminates if not provided) Properties : limitType : "count" or "cost" key : Request field to use for rate limiting (e.g. "metadata.user_id") limit : Maximum allowed requests/cost interval : Time window in seconds technique : "sliding" or "fixed" window { " id " : "<id>" , " type " : "rate_limit" , " properties " : { " limitType " : "count" , " key " : "metadata.user_id" , " limit " : 100 , " interval " : 3600 , " technique " : "sliding" }, " outputs " : { " success " : { " elementId " : "node_model_workers_ai" }, " fallback " : { " elementId " : "node_model_openai_mini" } } } ", "type": "rate_limit", "properties": { "limitType": "count", "key": "metadata.user_id", "limit": 100, "interval": 3600, "technique": "sliding" }, "outputs": { "success": { "elementId": "node_model_workers_ai" }, "fallback": { "elementId": "node_model_openai_mini" } }}"> Model Executes inference using a specified model and provider with configurable timeout and retry settings. Inputs : Request Outputs : success : Forwards request to provided element if model successfully starts streaming a response fallback : Optional output if model fails after all retries or times out Properties : provider : AI provider (e.g. "openai", "anthropic") model : Specific model name timeout : Request timeout in milliseconds retries : Number of retry attempts { " id " : "<id>" , " type " : "model" , " properties " : { " provider " : "openai" , " model " : "gpt-4o-mini" , " timeout " : 60000 , " retries " : 4 }, " outputs " : { " success " : { " elementId " : "<id>" }, " fallback " : { " elementId " : "<id>" } } } ", "type": "model", "properties": { "provider": "openai", "model": "gpt-4o-mini", "timeout": 60000, "retries": 4 }, "outputs": { "success": { "elementId": " " }, "fallback": { "elementId": " " } }}"> End element Marks the end of a route. Returns the last successful model response, or an error if no model response was generated. Inputs : Request Outputs : None { " id " : "<id>" , " type " : "end" } ", "type": "end"}"> Was this helpful? Edit page Last updated: Aug 19, 2025 Previous Using a dynamic route Next Data Loss Prevention (DLP) Resources API New to Cloudflare? Directory Sponsorships Open Source Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Speed Test Is BGP Safe Yet? RPKI Toolkit Certificate Transparency Community X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings | 2026-01-13T09:30:12 |
https://extensionworkshop.com/documentation/develop/#migration-checklist | Create extensions for Firefox and Firefox for Android | Firefox Extension Workshop Extension Workshop Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Submit or Manage Extensions Search Submit or Manage Extensions Search Select a section Page Name Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage a | 2026-01-13T09:30:12 |
https://developers.cloudflare.com/ai-gateway/features/dlp/ | Data Loss Prevention (DLP) · Cloudflare AI Gateway docs Skip to content Cloudflare Docs Search Docs Directory APIs SDKs Help Log in Select theme Dark Light Auto AI Gateway No results found. Try a different search term, or use our global search . Overview Getting started Using AI Gateway Unified API (OpenAI compat) Provider Native Workers AI Amazon Bedrock Anthropic Azure OpenAI Baseten Cartesia Cerebras Cohere Deepgram DeepSeek ElevenLabs Fal AI Google AI Studio Google Vertex AI Groq HuggingFace Ideogram Mistral AI OpenAI OpenRouter Parallel Perplexity Replicate xAI WebSockets API Beta Overview Realtime WebSockets API Non-realtime WebSockets API Features Overview Unified Billing Caching Rate limiting Dynamic routing Beta Overview Using a dynamic route JSON Configuration Data Loss Prevention (DLP) Beta Overview Set up Data Loss Prevention (DLP) Guardrails Beta Overview Set up Guardrails Supported model types Usage considerations Configuration BYOK (Store Keys) Beta Custom costs Custom Providers Beta Manage gateways Request handling Authenticated Gateway Observability Costs Custom metadata Analytics Logging Overview Workers Logpush Integrations Vercel AI SDK Agents ↗ AI Gateway Binding Methods Workers AI Tutorials Platform Overview Limits Pricing Audit logs Changelog Header Glossary REST API reference ↗ API MCP server ↗ MCP AI Assistant ↗ Architectures LLM resources llms.txt prompt.txt AI Gateway llms-full.txt Developer Platform llms-full.txt GitHub X.com YouTube Select theme Dark Light Auto On this page Overview How it works Key benefits Supported AI traffic Integration with Cloudflare DLP Getting started Related resources On this page Overview How it works Key benefits Supported AI traffic Integration with Cloudflare DLP Getting started Related resources Was this helpful? Edit Issue Directory … AI Gateway Features Data Loss Prevention (DLP) Copy page Data Loss Prevention (DLP) Data Loss Prevention (DLP) for AI Gateway helps protect your organization from inadvertent exposure of sensitive data through AI interactions. By integrating with Cloudflare's proven DLP technology, AI Gateway can scan both incoming prompts and outgoing AI responses for sensitive information, ensuring your AI applications maintain security and compliance standards. How it works AI Gateway DLP leverages the same powerful detection engines used in Cloudflare's Data Loss Prevention solution to scan AI traffic in real-time. The system analyzes both user prompts sent to AI models and responses received from AI providers, identifying sensitive data patterns and taking appropriate protective actions. Key benefits Prevent data leakage : Stop sensitive information from being inadvertently shared with AI providers or exposed in AI responses Maintain compliance : Help meet regulatory requirements like GDPR, HIPAA, and PCI DSS Consistent protection : Apply the same DLP policies across all AI providers and models Audit visibility : Comprehensive logging and reporting for security and compliance teams Zero-code integration : Enable protection without modifying existing AI applications Supported AI traffic AI Gateway DLP can scan: User prompts - Content submitted to AI models, including text, code, and structured data AI responses - Output generated by AI models before being returned to users The system works with all AI providers supported by AI Gateway, providing consistent protection regardless of which models or services you use. Integration with Cloudflare DLP AI Gateway DLP uses the same detection profiles and policies as Cloudflare's enterprise DLP solution. This means: Unified management - Configure DLP policies once and apply them across web traffic, email, SaaS applications, and AI interactions Consistent detection - The same sensitive data patterns are detected across all channels Centralized reporting - All DLP events appear in the same dashboard and logs Shared profiles - Reuse existing DLP detection profiles for AI traffic For more information about Cloudflare's DLP capabilities, refer to the Data Loss Prevention documentation . Getting started To enable DLP for your AI Gateway: Set up DLP policies for your AI Gateway Configure detection profiles and response actions Monitor DLP events through the Cloudflare dashboard Related resources Set up DLP for AI Gateway Cloudflare Data Loss Prevention AI Gateway Security Features DLP Detection Profiles Was this helpful? Edit page Last updated: Oct 22, 2025 Previous JSON Configuration Next Set up Data Loss Prevention (DLP) Resources API New to Cloudflare? Directory Sponsorships Open Source Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Speed Test Is BGP Safe Yet? RPKI Toolkit Certificate Transparency Community X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings | 2026-01-13T09:30:12 |
https://developers.google.com/admob/api/reference/rest/v1beta/accounts.adUnits.adUnitMappings/create | Method: accounts.adUnits.adUnitMappings.create | AdMob API | Google for Developers Skip to main content AdMob API / English Deutsch Español Español – América Latina Français Indonesia Italiano Polski Português – Brasil Tiếng Việt Türkçe Русский עברית العربيّة فارسی हिंदी বাংলা ภาษาไทย 中文 – 简体 中文 – 繁體 日本語 한국어 Sign in AdMob Guides Reference Libraries & Examples Support AdMob API AdMob Guides Reference Libraries & Examples Support Release notes AdMob API v1 REST Resources accounts Overview get list accounts.adUnits Overview list accounts.apps Overview list accounts.mediationReport Overview generate accounts.networkReport Overview generate Types DateRange LocalizationSettings ReportFooter ReportHeader ReportRow SortOrder StringList v1beta REST Resources accounts Overview get list accounts.adSources Overview list accounts.adSources.adapters Overview list accounts.adUnitMappings Overview batchCreate accounts.adUnits Overview create list accounts.adUnits.adUnitMappings Overview create list accounts.apps Overview create list accounts.campaignReport Overview generate accounts.mediationGroups Overview create list patch accounts.mediationGroups.mediationAbExperiments Overview create stop accounts.mediationReport Overview generate accounts.networkReport Overview generate Types DateRange LocalizationSettings MediationGroupLine ReportFooter ReportHeader ReportRow SortOrder StringList API dictionary Ad sources Adapters Home Products AdMob API Reference Method: accounts.adUnits.adUnitMappings.create Stay organized with collections Save and categorize content based on your preferences. Page Summary outlined_flag This method allows you to create an ad unit mapping under a specific AdMob account and ad unit. The method requires specific authorization scopes and may have limited access. The request uses a POST HTTP method and specifies required path parameters including the parent ad unit. The request and response bodies contain instances of AdUnitMapping. HTTP request Path parameters Request body Response body Authorization scopes Examples Try it! Create an ad unit mapping under the specific AdMob account and ad unit. This method has limited access. If you see a 403 permission denied error, please reach out to your account manager for access. HTTP request POST https://admob.googleapis.com/v1beta/{parent=accounts/*/adUnits/*}/adUnitMappings The URL uses gRPC Transcoding syntax. Path parameters Parameters parent string Required. The parent which owns the ad unit mapping. Format: accounts/{publisherId}/adUnits/{adUnitId} Request body The request body contains an instance of AdUnitMapping . Response body If successful, the response body contains a newly created instance of AdUnitMapping . Authorization scopes Requires the following OAuth scope: https://www.googleapis.com/auth/admob.monetization For more information, see the OAuth 2.0 Overview . Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License , and code samples are licensed under the Apache 2.0 License . For details, see the Google Developers Site Policies . Java is a registered trademark of Oracle and/or its affiliates. Last updated 2025-08-20 UTC. [[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-20 UTC."],[],["This describes how to create an ad unit mapping within AdMob. A `POST` HTTP request is sent to the specified URL, including the `parent` path parameter (account and ad unit IDs). The request body requires an `AdUnitMapping` instance. A successful response returns the newly created `AdUnitMapping`. Access requires the `admob.monetization` OAuth scope. Access may be restricted, needing permission from an account manager.\n"]] Product info Usage limits Pricing Terms of Service Programs Google Developer Program Google Developer Groups Google Developer Experts Accelerators Google Cloud & NVIDIA Developer consoles Google API Console Google Cloud Platform Console Google Play Console Firebase Console Actions on Google Console Cast SDK Developer Console Chrome Web Store Dashboard Google Home Developer Console Android Chrome Firebase Google Cloud Platform Google AI All products Terms Privacy Manage cookies English Deutsch Español Español – América Latina Français Indonesia Italiano Polski Português – Brasil Tiếng Việt Türkçe Русский עברית العربيّة فارسی हिंदी বাংলা ภาษาไทย 中文 – 简体 中文 – 繁體 日本語 한국어 | 2026-01-13T09:30:12 |
https://extensionworkshop.com/documentation/publish/add-on-policies/#migration-checklist | Add-on Policies | Firefox Extension Workshop Extension Workshop Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Submit or Manage Extensions Search Submit or Manage Extensions Search Select a section Page Name Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise <a href="https://support.mozilla.org/kb | 2026-01-13T09:30:12 |
https://developers.cloudflare.com/ai-gateway/usage/providers/bedrock/ | Amazon Bedrock · Cloudflare AI Gateway docs Skip to content Cloudflare Docs Search Docs Directory APIs SDKs Help Log in Select theme Dark Light Auto AI Gateway No results found. Try a different search term, or use our global search . Overview Getting started Using AI Gateway Unified API (OpenAI compat) Provider Native Workers AI Amazon Bedrock Anthropic Azure OpenAI Baseten Cartesia Cerebras Cohere Deepgram DeepSeek ElevenLabs Fal AI Google AI Studio Google Vertex AI Groq HuggingFace Ideogram Mistral AI OpenAI OpenRouter Parallel Perplexity Replicate xAI WebSockets API Beta Overview Realtime WebSockets API Non-realtime WebSockets API Features Overview Unified Billing Caching Rate limiting Dynamic routing Beta Overview Using a dynamic route JSON Configuration Data Loss Prevention (DLP) Beta Overview Set up Data Loss Prevention (DLP) Guardrails Beta Overview Set up Guardrails Supported model types Usage considerations Configuration BYOK (Store Keys) Beta Custom costs Custom Providers Beta Manage gateways Request handling Authenticated Gateway Observability Costs Custom metadata Analytics Logging Overview Workers Logpush Integrations Vercel AI SDK Agents ↗ AI Gateway Binding Methods Workers AI Tutorials Platform Overview Limits Pricing Audit logs Changelog Header Glossary REST API reference ↗ API MCP server ↗ MCP AI Assistant ↗ Architectures LLM resources llms.txt prompt.txt AI Gateway llms-full.txt Developer Platform llms-full.txt GitHub X.com YouTube Select theme Dark Light Auto On this page Overview Endpoint Prerequisites Make a request Examples Use aws4fetch SDK with TypeScript On this page Overview Endpoint Prerequisites Make a request Examples Use aws4fetch SDK with TypeScript Was this helpful? Edit Issue Directory … AI Gateway Using AI Gateway Provider Native Amazon Bedrock Copy page Amazon Bedrock Amazon Bedrock ↗ allows you to build and scale generative AI applications with foundation models. Endpoint https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/aws-bedrock` Prerequisites When making requests to Amazon Bedrock, ensure you have the following: Your AI Gateway Account ID. Your AI Gateway gateway name. An active Amazon Bedrock API token. The name of the Amazon Bedrock model you want to use. Make a request When making requests to Amazon Bedrock, replace https://bedrock-runtime.us-east-1.amazonaws.com/ in the URL you're currently using with https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/aws-bedrock/bedrock-runtime/us-east-1/ , then add the model you want to run at the end of the URL. With Bedrock, you will need to sign the URL before you make requests to AI Gateway. You can try using the aws4fetch ↗ SDK. Examples Use aws4fetch SDK with TypeScript TypeScript import { AwsClient } from "aws4fetch" ; interface Env { accessKey : string ; secretAccessKey : string ; } export default { async fetch ( request : Request , env : Env , ctx : ExecutionContext , ) : Promise < Response > { // replace with your configuration const cfAccountId = "{account_id}" ; const gatewayName = "{gateway_id}" ; const region = "us-east-1" ; // added as secrets (https://developers.cloudflare.com/workers/configuration/secrets/) const accessKey = env . accessKey ; const secretKey = env . secretAccessKey ; const awsClient = new AwsClient ( { accessKeyId : accessKey , secretAccessKey : secretKey , region : region , service : "bedrock" , } ) ; const requestBodyString = JSON . stringify ( { inputText : "What does ethereal mean?" , } ) ; const stockUrl = new URL ( `https://bedrock-runtime. ${ region } .amazonaws.com/model/amazon.titan-embed-text-v1/invoke` , ) ; const headers = { "Content-Type" : "application/json" , }; // sign the original request const presignedRequest = await awsClient . sign ( stockUrl . toString () , { method : "POST" , headers : headers , body : requestBodyString , } ) ; // Gateway Url const gatewayUrl = new URL ( `https://gateway.ai.cloudflare.com/v1/ ${ cfAccountId } / ${ gatewayName } /aws-bedrock/bedrock-runtime/ ${ region } /model/amazon.titan-embed-text-v1/invoke` , ) ; // make the request through the gateway url const response = await fetch ( gatewayUrl , { method : "POST" , headers : presignedRequest . headers , body : requestBodyString , } ) ; if ( response . ok && response . headers . get ( "content-type" ) ?. includes ( "application/json" ) ) { const data = await response . json () ; return new Response ( JSON . stringify ( data )) ; } return new Response ( "Invalid response" , { status : 500 } ) ; }, }; { // replace with your configuration const cfAccountId = "{account_id}"; const gatewayName = "{gateway_id}"; const region = "us-east-1"; // added as secrets (https://developers.cloudflare.com/workers/configuration/secrets/) const accessKey = env.accessKey; const secretKey = env.secretAccessKey; const awsClient = new AwsClient({ accessKeyId: accessKey, secretAccessKey: secretKey, region: region, service: "bedrock", }); const requestBodyString = JSON.stringify({ inputText: "What does ethereal mean?", }); const stockUrl = new URL( `https://bedrock-runtime.${region}.amazonaws.com/model/amazon.titan-embed-text-v1/invoke`, ); const headers = { "Content-Type": "application/json", }; // sign the original request const presignedRequest = await awsClient.sign(stockUrl.toString(), { method: "POST", headers: headers, body: requestBodyString, }); // Gateway Url const gatewayUrl = new URL( `https://gateway.ai.cloudflare.com/v1/${cfAccountId}/${gatewayName}/aws-bedrock/bedrock-runtime/${region}/model/amazon.titan-embed-text-v1/invoke`, ); // make the request through the gateway url const response = await fetch(gatewayUrl, { method: "POST", headers: presignedRequest.headers, body: requestBodyString, }); if ( response.ok && response.headers.get("content-type")?.includes("application/json") ) { const data = await response.json(); return new Response(JSON.stringify(data)); } return new Response("Invalid response", { status: 500 }); },};"> Was this helpful? Edit page Last updated: Oct 4, 2025 Previous Workers AI Next Anthropic Resources API New to Cloudflare? Directory Sponsorships Open Source Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Speed Test Is BGP Safe Yet? RPKI Toolkit Certificate Transparency Community X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings | 2026-01-13T09:30:12 |
https://developers.cloudflare.com/ai-gateway/usage/websockets-api/realtime-api/ | Realtime WebSockets API · Cloudflare AI Gateway docs Skip to content Cloudflare Docs Search Docs Directory APIs SDKs Help Log in Select theme Dark Light Auto AI Gateway No results found. Try a different search term, or use our global search . Overview Getting started Using AI Gateway Unified API (OpenAI compat) Provider Native Workers AI Amazon Bedrock Anthropic Azure OpenAI Baseten Cartesia Cerebras Cohere Deepgram DeepSeek ElevenLabs Fal AI Google AI Studio Google Vertex AI Groq HuggingFace Ideogram Mistral AI OpenAI OpenRouter Parallel Perplexity Replicate xAI WebSockets API Beta Overview Realtime WebSockets API Non-realtime WebSockets API Features Overview Unified Billing Caching Rate limiting Dynamic routing Beta Overview Using a dynamic route JSON Configuration Data Loss Prevention (DLP) Beta Overview Set up Data Loss Prevention (DLP) Guardrails Beta Overview Set up Guardrails Supported model types Usage considerations Configuration BYOK (Store Keys) Beta Custom costs Custom Providers Beta Manage gateways Request handling Authenticated Gateway Observability Costs Custom metadata Analytics Logging Overview Workers Logpush Integrations Vercel AI SDK Agents ↗ AI Gateway Binding Methods Workers AI Tutorials Platform Overview Limits Pricing Audit logs Changelog Header Glossary REST API reference ↗ API MCP server ↗ MCP AI Assistant ↗ Architectures LLM resources llms.txt prompt.txt AI Gateway llms-full.txt Developer Platform llms-full.txt GitHub X.com YouTube Select theme Dark Light Auto On this page Overview Supported Providers Authentication Examples OpenAI Google AI Studio Cartesia ElevenLabs Fal AI Deepgram (Workers AI) On this page Overview Supported Providers Authentication Examples OpenAI Google AI Studio Cartesia ElevenLabs Fal AI Deepgram (Workers AI) Was this helpful? Edit Issue Directory … AI Gateway Using AI Gateway WebSockets API Realtime WebSockets API Copy page Realtime WebSockets API Some AI providers support real-time, low-latency interactions over WebSockets. AI Gateway allows seamless integration with these APIs, supporting multimodal interactions such as text, audio, and video. Supported Providers OpenAI ↗ Google AI Studio ↗ Cartesia ↗ ElevenLabs ↗ Fal AI ↗ Deepgram (Workers AI) ↗ Authentication For real-time WebSockets, authentication can be done using: Headers (for non-browser environments) sec-websocket-protocol (for browsers) Note Provider specific API Keys can also be alternatively configured on AI Gateway using our BYOK feature. You must still include the cf-aig-authorization header in the websocket request. Examples OpenAI JavaScript import WebSocket from "ws" ; const url = "wss://gateway.ai.cloudflare.com/v1/<account_id>/<gateway>/openai?model=gpt-4o-realtime-preview-2024-12-17" ; const ws = new WebSocket ( url , { headers : { "cf-aig-authorization" : process . env . CLOUDFLARE_API_KEY , Authorization : "Bearer " + process . env . OPENAI_API_KEY , "OpenAI-Beta" : "realtime=v1" , }, } ) ; ws . on ( "open" , () => console . log ( "Connected to server." )) ; ws . on ( "message" , ( message ) => console . log ( JSON . parse ( message . toString ()))) ; ws . send ( JSON . stringify ( { type : "response.create" , response : { modalities : [ "text" ] , instructions : "Tell me a joke" }, } ) , ) ; / /openai?model=gpt-4o-realtime-preview-2024-12-17";const ws = new WebSocket(url, { headers: { "cf-aig-authorization": process.env.CLOUDFLARE_API_KEY, Authorization: "Bearer " + process.env.OPENAI_API_KEY, "OpenAI-Beta": "realtime=v1", },});ws.on("open", () => console.log("Connected to server."));ws.on("message", (message) => console.log(JSON.parse(message.toString())));ws.send( JSON.stringify({ type: "response.create", response: { modalities: ["text"], instructions: "Tell me a joke" }, }),);"> Google AI Studio JavaScript const ws = new WebSocket ( "wss://gateway.ai.cloudflare.com/v1/<account_id>/<gateway>/google?api_key=<google_api_key>" , [ "cf-aig-authorization.<cloudflare_token>" ] , ) ; ws . on ( "open" , () => console . log ( "Connected to server." )) ; ws . on ( "message" , ( message ) => console . log ( message . data )) ; ws . send ( JSON . stringify ( { setup : { model : "models/gemini-2.5-flash" , generationConfig : { responseModalities : [ "TEXT" ] }, }, } ) , ) ; / /google?api_key= ", ["cf-aig-authorization. "],);ws.on("open", () => console.log("Connected to server."));ws.on("message", (message) => console.log(message.data));ws.send( JSON.stringify({ setup: { model: "models/gemini-2.5-flash", generationConfig: { responseModalities: ["TEXT"] }, }, }),);"> Cartesia JavaScript const ws = new WebSocket ( "wss://gateway.ai.cloudflare.com/v1/<account_id>/<gateway>/cartesia?cartesia_version=2024-06-10&api_key=<cartesia_api_key>" , [ "cf-aig-authorization.<cloudflare_token>" ] , ) ; ws . on ( "open" , function open () { console . log ( "Connected to server." ) ; } ) ; ws . on ( "message" , function incoming ( message ) { console . log ( message . data ) ; } ) ; ws . send ( JSON . stringify ( { model_id : "sonic" , transcript : "Hello, world! I'm generating audio on " , voice : { mode : "id" , id : "a0e99841-438c-4a64-b679-ae501e7d6091" }, language : "en" , context_id : "happy-monkeys-fly" , output_format : { container : "raw" , encoding : "pcm_s16le" , sample_rate : 8000 , }, add_timestamps : true , continue : true , } ) , ) ; / /cartesia?cartesia_version=2024-06-10&api_key= ", ["cf-aig-authorization. "],);ws.on("open", function open() { console.log("Connected to server.");});ws.on("message", function incoming(message) { console.log(message.data);});ws.send( JSON.stringify({ model_id: "sonic", transcript: "Hello, world! I'm generating audio on ", voice: { mode: "id", id: "a0e99841-438c-4a64-b679-ae501e7d6091" }, language: "en", context_id: "happy-monkeys-fly", output_format: { container: "raw", encoding: "pcm_s16le", sample_rate: 8000, }, add_timestamps: true, continue: true, }),);"> ElevenLabs JavaScript const ws = new WebSocket ( "wss://gateway.ai.cloudflare.com/v1/<account_id>/<gateway>/elevenlabs?agent_id=<elevenlabs_agent_id>" , [ "xi-api-key.<elevenlabs_api_key>" , "cf-aig-authorization.<cloudflare_token>" , ] , ) ; ws . on ( "open" , function open () { console . log ( "Connected to server." ) ; } ) ; ws . on ( "message" , function incoming ( message ) { console . log ( message . data ) ; } ) ; ws . send ( JSON . stringify ( { text : "This is a sample text " , voice_settings : { stability : 0.8 , similarity_boost : 0.8 }, generation_config : { chunk_length_schedule : [ 120 , 160 , 250 , 290 ] }, } ) , ) ; / /elevenlabs?agent_id= ", [ "xi-api-key. ", "cf-aig-authorization. ", ],);ws.on("open", function open() { console.log("Connected to server.");});ws.on("message", function incoming(message) { console.log(message.data);});ws.send( JSON.stringify({ text: "This is a sample text ", voice_settings: { stability: 0.8, similarity_boost: 0.8 }, generation_config: { chunk_length_schedule: [120, 160, 250, 290] }, }),);"> Fal AI Fal AI supports WebSocket connections for real-time model interactions through their HTTP over WebSocket API. JavaScript const ws = new WebSocket ( "wss://gateway.ai.cloudflare.com/v1/<account_id>/<gateway>/fal/fal-ai/fast-lcm-diffusion" , [ "fal-api-key.<fal_api_key>" , "cf-aig-authorization.<cloudflare_token>" ] , ) ; ws . on ( "open" , function open () { console . log ( "Connected to server." ) ; } ) ; ws . on ( "message" , function incoming ( message ) { console . log ( message . data ) ; } ) ; ws . send ( JSON . stringify ( { prompt : "generate an image of a cat flying an aeroplane" , } ) , ) ; / /fal/fal-ai/fast-lcm-diffusion", ["fal-api-key. ", "cf-aig-authorization. "],);ws.on("open", function open() { console.log("Connected to server.");});ws.on("message", function incoming(message) { console.log(message.data);});ws.send( JSON.stringify({ prompt: "generate an image of a cat flying an aeroplane", }),);"> For more information on Fal AI's WebSocket API, see their HTTP over WebSocket documentation ↗ . Deepgram (Workers AI) Workers AI provides Deepgram models for real-time speech-to-text (STT) and text-to-speech (TTS) capabilities through WebSocket connections. Speech-to-Text (STT) Workers AI supports two Deepgram STT models: @cf/deepgram/nova-3 and @cf/deepgram/flux . The following example demonstrates real-time audio transcription from a microphone: JavaScript import WebSocket from "ws" ; import mic from "mic" ; const ws = new WebSocket ( "wss://gateway.ai.cloudflare.com/v1/<account_id>/<gateway>/workers-ai?model=@cf/deepgram/nova-3&encoding=linear16&sample_rate=16000&interim_results=true" , { headers : { "cf-aig-authorization" : process . env . CLOUDFLARE_API_KEY , }, }, ) ; // Configure microphone const micInstance = mic ( { rate : "16000" , channels : "1" , debug : false , exitOnSilence : 6 , } ) ; const micInputStream = micInstance . getAudioStream () ; micInputStream . on ( "data" , ( data ) => { if ( ws . readyState === WebSocket . OPEN ) { ws . send ( data ) ; } } ) ; micInputStream . on ( "error" , ( error ) => { console . error ( "Microphone error:" , error ) ; } ) ; ws . onopen = () => { console . log ( "Connected to WebSocket" ) ; console . log ( "Starting microphone..." ) ; micInstance . start () ; }; ws . onmessage = ( event ) => { try { const parse = JSON . parse ( event . data ) ; if ( parse . channel ?. alternatives ?. [ 0 ] ?. transcript ) { if ( parse . is_final ) { console . log ( "Final transcript:" , parse . channel . alternatives [ 0 ] . transcript , ) ; } else { console . log ( "Interim transcript:" , parse . channel . alternatives [ 0 ] . transcript , ) ; } } } catch ( error ) { console . error ( "Error parsing message:" , error ) ; } }; ws . onerror = ( error ) => { console . error ( "WebSocket error:" , error ) ; }; ws . onclose = () => { console . log ( "WebSocket closed" ) ; micInstance . stop () ; }; / /workers-ai?model=@cf/deepgram/nova-3&encoding=linear16&sample_rate=16000&interim_results=true", { headers: { "cf-aig-authorization": process.env.CLOUDFLARE_API_KEY, }, },);// Configure microphoneconst micInstance = mic({ rate: "16000", channels: "1", debug: false, exitOnSilence: 6,});const micInputStream = micInstance.getAudioStream();micInputStream.on("data", (data) => { if (ws.readyState === WebSocket.OPEN) { ws.send(data); }});micInputStream.on("error", (error) => { console.error("Microphone error:", error);});ws.onopen = () => { console.log("Connected to WebSocket"); console.log("Starting microphone..."); micInstance.start();};ws.onmessage = (event) => { try { const parse = JSON.parse(event.data); if (parse.channel?.alternatives?.[0]?.transcript) { if (parse.is_final) { console.log( "Final transcript:", parse.channel.alternatives[0].transcript, ); } else { console.log( "Interim transcript:", parse.channel.alternatives[0].transcript, ); } } } catch (error) { console.error("Error parsing message:", error); }};ws.onerror = (error) => { console.error("WebSocket error:", error);};ws.onclose = () => { console.log("WebSocket closed"); micInstance.stop();};"> Text-to-Speech (TTS) Workers AI supports the Deepgram @cf/deepgram/aura-1 model for TTS. The following example demonstrates converting text input to audio: JavaScript import WebSocket from "ws" ; import readline from "readline" ; import Speaker from "speaker" ; const ws = new WebSocket ( "wss://gateway.ai.cloudflare.com/v1/<account_id>/<gateway>/workers-ai?model=@cf/deepgram/aura-1" , { headers : { "cf-aig-authorization" : process . env . CLOUDFLARE_API_KEY , }, }, ) ; // Speaker management let currentSpeaker = null ; let isPlayingAudio = false ; // Setup readline for text input const rl = readline . createInterface ( { input : process . stdin , output : process . stdout , prompt : "Enter text to speak (or \" quit \" to exit): " , } ) ; ws . onopen = () => { console . log ( "Connected to Deepgram TTS WebSocket" ) ; rl . prompt () ; }; ws . onmessage = ( event ) => { // Check if message is JSON (metadata, flushed, etc.) or raw audio if ( event . data instanceof Buffer || event . data instanceof ArrayBuffer ) { // Raw audio data - create new speaker if needed if ( ! currentSpeaker ) { currentSpeaker = new Speaker ( { channels : 1 , bitDepth : 16 , sampleRate : 24000 , } ) ; isPlayingAudio = true ; } currentSpeaker . write ( Buffer . from ( event . data )) ; } else { try { const message = JSON . parse ( event . data ) ; switch ( message . type ) { case "Metadata" : console . log ( "Model info:" , message . model_name , message . model_version ) ; break ; case "Flushed" : console . log ( "Audio complete" ) ; // End speaker after flush to prevent buffer underflow if ( currentSpeaker && isPlayingAudio ) { currentSpeaker . end () ; currentSpeaker = null ; isPlayingAudio = false ; } rl . prompt () ; break ; case "Cleared" : console . log ( "Audio cleared, sequence:" , message . sequence_id ) ; break ; case "Warning" : console . warn ( "Warning:" , message . description ) ; break ; } } catch ( error ) { // Not JSON, might be raw audio as string if ( ! currentSpeaker ) { currentSpeaker = new Speaker ( { channels : 1 , bitDepth : 16 , sampleRate : 24000 , } ) ; isPlayingAudio = true ; } currentSpeaker . write ( Buffer . from ( event . data )) ; } } }; ws . onerror = ( error ) => { console . error ( "WebSocket error:" , error ) ; }; ws . onclose = () => { console . log ( "WebSocket closed" ) ; if ( currentSpeaker ) { currentSpeaker . end () ; } rl . close () ; process . exit ( 0 ) ; }; // Handle user input rl . on ( "line" , ( input ) => { const text = input . trim () ; if ( text . toLowerCase () === "quit" ) { // Send Close message ws . send ( JSON . stringify ( { type : "Close" } )) ; ws . close () ; return ; } if ( text . length > 0 ) { // Send text to TTS ws . send ( JSON . stringify ( { type : "Speak" , text : text , } ) , ) ; // Flush to get audio immediately ws . send ( JSON . stringify ( { type : "Flush" } )) ; console . log ( "Flushing audio" ) ; } rl . prompt () ; } ) ; rl . on ( "close" , () => { if ( ws . readyState === WebSocket . OPEN ) { ws . close () ; } } ) ; / /workers-ai?model=@cf/deepgram/aura-1", { headers: { "cf-aig-authorization": process.env.CLOUDFLARE_API_KEY, }, },);// Speaker managementlet currentSpeaker = null;let isPlayingAudio = false;// Setup readline for text inputconst rl = readline.createInterface({ input: process.stdin, output: process.stdout, prompt: "Enter text to speak (or \"quit\" to exit): ",});ws.onopen = () => { console.log("Connected to Deepgram TTS WebSocket"); rl.prompt();};ws.onmessage = (event) => { // Check if message is JSON (metadata, flushed, etc.) or raw audio if (event.data instanceof Buffer || event.data instanceof ArrayBuffer) { // Raw audio data - create new speaker if needed if (!currentSpeaker) { currentSpeaker = new Speaker({ channels: 1, bitDepth: 16, sampleRate: 24000, }); isPlayingAudio = true; } currentSpeaker.write(Buffer.from(event.data)); } else { try { const message = JSON.parse(event.data); switch (message.type) { case "Metadata": console.log("Model info:", message.model_name, message.model_version); break; case "Flushed": console.log("Audio complete"); // End speaker after flush to prevent buffer underflow if (currentSpeaker && isPlayingAudio) { currentSpeaker.end(); currentSpeaker = null; isPlayingAudio = false; } rl.prompt(); break; case "Cleared": console.log("Audio cleared, sequence:", message.sequence_id); break; case "Warning": console.warn("Warning:", message.description); break; } } catch (error) { // Not JSON, might be raw audio as string if (!currentSpeaker) { currentSpeaker = new Speaker({ channels: 1, bitDepth: 16, sampleRate: 24000, }); isPlayingAudio = true; } currentSpeaker.write(Buffer.from(event.data)); } }};ws.onerror = (error) => { console.error("WebSocket error:", error);};ws.onclose = () => { console.log("WebSocket closed"); if (currentSpeaker) { currentSpeaker.end(); } rl.close(); process.exit(0);};// Handle user inputrl.on("line", (input) => { const text = input.trim(); if (text.toLowerCase() === "quit") { // Send Close message ws.send(JSON.stringify({ type: "Close" })); ws.close(); return; } if (text.length > 0) { // Send text to TTS ws.send( JSON.stringify({ type: "Speak", text: text, }), ); // Flush to get audio immediately ws.send(JSON.stringify({ type: "Flush" })); console.log("Flushing audio"); } rl.prompt();});rl.on("close", () => { if (ws.readyState === WebSocket.OPEN) { ws.close(); }});"> Was this helpful? Edit page Last updated: Oct 9, 2025 Previous WebSockets API Next Non-realtime WebSockets API Resources API New to Cloudflare? Directory Sponsorships Open Source Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Speed Test Is BGP Safe Yet? RPKI Toolkit Certificate Transparency Community X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings | 2026-01-13T09:30:12 |
https://developers.cloudflare.com/ai-gateway/usage/providers/replicate/ | Replicate · Cloudflare AI Gateway docs Skip to content Cloudflare Docs Search Docs Directory APIs SDKs Help Log in Select theme Dark Light Auto AI Gateway No results found. Try a different search term, or use our global search . Overview Getting started Using AI Gateway Unified API (OpenAI compat) Provider Native Workers AI Amazon Bedrock Anthropic Azure OpenAI Baseten Cartesia Cerebras Cohere Deepgram DeepSeek ElevenLabs Fal AI Google AI Studio Google Vertex AI Groq HuggingFace Ideogram Mistral AI OpenAI OpenRouter Parallel Perplexity Replicate xAI WebSockets API Beta Overview Realtime WebSockets API Non-realtime WebSockets API Features Overview Unified Billing Caching Rate limiting Dynamic routing Beta Overview Using a dynamic route JSON Configuration Data Loss Prevention (DLP) Beta Overview Set up Data Loss Prevention (DLP) Guardrails Beta Overview Set up Guardrails Supported model types Usage considerations Configuration BYOK (Store Keys) Beta Custom costs Custom Providers Beta Manage gateways Request handling Authenticated Gateway Observability Costs Custom metadata Analytics Logging Overview Workers Logpush Integrations Vercel AI SDK Agents ↗ AI Gateway Binding Methods Workers AI Tutorials Platform Overview Limits Pricing Audit logs Changelog Header Glossary REST API reference ↗ API MCP server ↗ MCP AI Assistant ↗ Architectures LLM resources llms.txt prompt.txt AI Gateway llms-full.txt Developer Platform llms-full.txt GitHub X.com YouTube Select theme Dark Light Auto On this page Overview Endpoint URL structure Prerequisites Example cURL On this page Overview Endpoint URL structure Prerequisites Example cURL Was this helpful? Edit Issue Directory … AI Gateway Using AI Gateway Provider Native Replicate Copy page Replicate Replicate ↗ runs and fine tunes open-source models. Endpoint https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/replicate URL structure When making requests to Replicate, replace https://api.replicate.com/v1 in the URL you're currently using with https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/replicate . Prerequisites When making requests to Replicate, ensure you have the following: Your AI Gateway Account ID. Your AI Gateway gateway name. An active Replicate API token. You can create one at replicate.com/settings/api-tokens ↗ The name of the Replicate model you want to use, like anthropic/claude-4.5-haiku or google/nano-banana . Example cURL Request curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/replicate/predictions \ --header 'Authorization: Bearer {replicate_api_token}' \ --header 'Content-Type: application/json' \ --data '{ "version": "anthropic/claude-4.5-haiku", "input": { "prompt": "Write a haiku about Cloudflare" } }' Was this helpful? Edit page Last updated: Oct 29, 2025 Previous Perplexity Next xAI Resources API New to Cloudflare? Directory Sponsorships Open Source Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Speed Test Is BGP Safe Yet? RPKI Toolkit Certificate Transparency Community X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings | 2026-01-13T09:30:12 |
https://extensionworkshop.com/documentation/publish/add-on-policies/#getting-started | Add-on Policies | Firefox Extension Workshop Extension Workshop Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Submit or Manage Extensions Search Submit or Manage Extensions Search Select a section Page Name Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Add-on Policies Add-ons extend the core capabilities of Firefox, enabling users to modify and personalize their web experience. A healthy ecosystem, built on trust, is vital for developers to be successful and users to feel safe making Firefox their own. For these reasons, Mozilla requires all add-ons to comply with the following policies. These policies are not intended to serve as legal advice: depending on where you are located, additional requirements may apply. All add-ons are subject to these policies, regardless of how they are distributed. When an add-on is given human review or otherwise assessed by Mozilla, these policies act as guiding principles for those reviews. Add-ons that do not comply with these policies may be rejected or disabled by Mozilla. Contents No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking No Surprises Users should be able to easily discern the functionality of your add-on based on the listing, and should not be presented with unexpected user experiences after installing it. The listing should include an easy-to-read description of what the add-on does, and what information it transmits. Please consult our best practices guide for creating an appealing listing . Unexpected features “Unexpected” features are those that are unrelated to the add-on’s primary function, and are not clearly indicated by the add-on name or description. This may include features that impact user privacy or security, make unexpected changes to web content, or change default settings like the new tab page, homepage, or search engine. Any “unexpected” feature(s) must adhere to all of the following requirements: The add-on description must clearly state any changes made by these features. The features must be “opt-in”, meaning the user has to take non-default action to enact the change. Changes prompted by Firefox after the add-on is installed do not require an additional opt-in. The permissions prompt shown when installing an add-on does not alleviate the need for an opt-in. The opt-in interface must clearly state the name of the add-on requesting the change. Content Add-ons that make use of Mozilla trademarks must comply with the Mozilla Trademark Guidelines . If the add-on uses “Firefox” in its name, the naming standard the add-on is expected to follow is “<Add-on name> for Firefox”. In addition, add-ons listed on addons.mozilla.org must adhere to the following policies: All add-ons submitted for listing on addons.mozilla.org are subject to Mozilla’s Acceptable Use Policy . Listings must disclose when payment is required to enable any add-on functionality. Add-ons and their content must conform to the laws of the United States. (Add-ons that violate or have content that violates the law in other jurisdictions may also be removed or have access limited.) If the add-on is a fork of another add-on, the name must clearly distinguish it from the original and provide a significant difference in functionality and/or code. Add-ons with the sole purpose of promoting, installing, loading or launching an outside website, application or add-on are not permitted. Themes that feature low-quality, stretched, or blank images, as well as those themes in which the header image is misaligned, are not permitted. Duplicate themes are not permitted. Submission Guidelines Add-ons must function only as described. During review, the add-on undergoes basic functional testing in addition to code review. To facilitate the functional testing, the add-on author must provide testing information and, if an account is needed for any part of the add-on’s functionality, testing credentials to allow use of the add-on. If corrections have been requested and are submitted as part of a new version, the new version should not contain unrelated changes, as this complicates the review process and can lead to further delays or rejections. Source Code Submission Code must be provided in a way that is reviewable. Add-ons may contain transpiled, minified or otherwise machine-generated code, but Mozilla needs to review a copy of the source code before any of these steps have been applied. The author must provide this information to Mozilla during submission along with instructions on how to reproduce the build. All dependencies must either be included in the source code package directly or downloaded only through the respective official package managers during the build process. Build tools or environments that no longer appear to be supported by their maintainers are not accepted. Reviewers may ask you to refactor parts of the code if it is not reviewable. The provided source code is reviewed by an administrator and is not redistributed in any way. The code is only used for the purpose of reviewing the add-on. Failure to provide this information results in rejection or blocking. Add-ons are not allowed to contain obfuscated code, nor code that hides the purpose of the functionality involved. If external resources are used in combination with add-on code, the functionality of the code must not be obscured. Minification of code with the intent to reduce file size is permitted. Please read our Source Code Submission guidelines to avoid unexpected rejections or blocks. Development Practices In general, developers are free to maintain their add-ons in the manner they choose. However, in order to maintain appropriate data security measures and allow us to effectively review code, we have certain technical requirements that all add-ons must meet. In particular, potentially dangerous APIs may only be used in ways that are demonstrably safe, and code within add-ons that cannot be verified as behaving safely and correctly may need to be refactored. The following requirements are of particular importance: Add-ons must only request those permissions that are necessary for them to function. Add-ons must be self-contained and not load remote code for execution. Add-ons must not load or redirect to a remote new tab page. The new tab page must be contained within the add-on. Add-ons must not relax web page security headers, such as the Content Security Policy. Add-ons must use encryption when transporting data remotely. Add-ons should avoid including redundant code or files. Add-ons must not negatively impact the performance or stability of Firefox. Only release versions of third-party libraries and/or frameworks may be included with an add-on. Modifications to these libraries/frameworks are not permitted. Please read our third party library guidelines to better understand related requirements. User Scripts Usage of the userScripts API is allowed for user script managers only. A user script manager is an extension that allows users to manage website-specific scripts. The userScripts API cannot be used to extend or modify the functionality of the user script manager itself. The user must: Proactively install a user script using an explicit action, for instance a click on a button labeled “Install this user script”. Be able to see which user scripts are currently installed and remove scripts without impacting the extension. Data Collection and Transmission Disclosure and Control Add-ons must limit data transmission to what is necessary for functionality, and must use the data only for the purpose for which it was transmitted. For the purposes of this policy, data transmission refers to any data that is collected, used, transferred, shared, or handled outside of the add-on or the local browser. If the add-on uses native messaging, the Add-on Policies (including those related to user consent and control) apply to any data sent to the native application as well. Prohibited Data Collection and Transmission Search functionality provided or loaded by the add-on must not transmit search terms or intercept searches that are going to a third-party search provider. Transmitting or facilitating the transmission of ancillary information (e.g. any data not required for the add-on’s functionality as stated in the description) is prohibited. The transmission of browsing activity is only permitted as part of the add-on’s primary function. User Consent and Control The user must be provided with a clear way to control the add-on’s data transmission, either through a consent experience created by the add-on developer, or by using Firefox’s built in data collection and transmission consent experience. In the case of add-ons that qualify for implicit consent, under the “Implicit Consent for Self-Evident, Single-Use Extension” policy, installation is the consent. Add-ons installed in an enterprise environment can bypass asking for data collection consent when they are installed by enterprise policy. For more information, refer to the enterprise documentation . If the add-on uses Firefox’s built-in data collection and transmission consent experience, then the browser will bypass this by default. If the add-on is only compatible with Firefox 140 or later and uses Firefox’s built-in data collection and transmission consent experience: It must accurately state the data collection practices in the extension manifest, including when it does not collect data, in line with the Firefox add-on data classification taxonomy . If the add-on is compatible with Firefox 139 and earlier or does not use Firefox’s built-in data collection and transmission consent experience: The user must be provided with a clear way to control the add-on’s data transmission immediately after installation of the add-on. If data transmission starts or changes in an add-on update, or the consent and control is introduced in an update, it must be shown to all new and upgrading users immediately after the update. The data transmission consent and control must be contained within the add-on. The consent experience must: Be unmissable. It is recommended to present it in a new focused tab in the current window. Other ways that could be missed or accidentally hidden, like a popup window, will result in a rejection. Be presented on a single page, including all choices and decision options. Present users with a clear, readable data transmission consent. Information explaining the data transmitted must be prominently stated and not buried or hidden. Avoid deceptive design patterns that make it harder to understand your data transmission policy, including, but not limited to, illegible font sizes, reduced color contrast, hidden options, multi-step consent decline flows, and similar techniques indicative of deceptive design. Clearly state what type of data is being transmitted. Inform about the impact of accepting or declining the data transmission If both personal and technical data is being transmitted, the user must be provided separate choices. If the user declines the transmission, any resulting impact on their experience or use of the add-on must be limited to the data not being available. Please refer to our best practices for advice and examples on how to design and implement a data transmission consent prompt. Personal Data (opt-in) Personally identifiable information can be actively provided by the user or obtained through extension APIs. It includes, but is not limited to names, email addresses, search terms and browsing activity data, as well as access to and placement of cookies. Before an add-on may transmit personal information, it must clearly describe, and the user must affirmatively consent (i.e., explicitly opt-in) to the type of personal data being transmitted. If the primary function of the add-on does not work without transmitting personal data, the add-on must provide a choice for the user to either accept the data transmission or uninstall the add-on. Implicit Consent for Self-Evident, Single-Use Extension Implicit consent applies only to add-ons hosted on addons.mozilla.org when all of the following conditions are satisfied. Otherwise the standard explicit consent rules apply. Conditions Purpose-bounded and user-initiated – Data may be transmitted only as a direct, immediate consequence of a single, deliberate user command (for example, a click or tap) on a clearly labelled control supplied by the browser or the add-on. Any passive, continuous, or background transmission requires explicit consent. Self-evident listing disclosure – The add-ons name and addons.mozilla.org listing must, in combination, make it clear what data will be transmitted and why, consistent with the “No Surprises” policy. Self-evident user interface – At the point of interaction, the in-product UI must plainly signal which data will be sent and to what type of service, so the user can foresee the consequence of their action without additional prompts. Purpose-limited data scope – The transmission: a. is strictly limited to the content element the user acted upon (for example, selected text, current page URL, chosen file or image); and b. must not include persistent identifiers, analytics beacons, cookies, advertising IDs, or any data unrelated to completing the primary function of the add-on. Transmission of certain data requires explicit consent, regardless of the above. For more information, refer to the Firefox add-on data classification taxonomy . Review authority – Mozilla reviewers may require the add-on to obtain explicit user consent if they judge an add-on’s disclosure inadequate or detect attempts to broaden data collection. When all the above conditions are met, invoking the primary function is deemed implicit consent for transmitting the user-supplied data needed to perform that function. No additional dialog needs to be shown at install time. If any other data is transmitted, explicit consent at time of install is required. Technical & User Interaction Data (opt-out) Technical data describes information about the environment the user is running, such as browser settings, platform information and hardware properties. User interaction data includes how the user interacts with Firefox and the installed add-ons, metrics for product improvement, and error information. When an add-on transmits either of these types of information, it must allow the user to disable that data transmission (opt-out) during the initial consent experience. The add-on functionality must not be restricted if the user declines transmission of this data. Additional Privacy Protocols Leaking local or user-specific information to websites or other applications (e.g. through native messaging) is prohibited. Data from private browsing sessions must not be stored. Information that identifies a user across browsing sessions or containers must not be made available to web content. Monetization An add-on injecting advertising into web page content must clearly identify the injected content as originating from the add-on. The inclusion of any cryptocurrency miners in an add-on is prohibited. Modifying web content or facilitating redirects to include affiliate promotion tags is not permitted. Conversely, the inclusion of affiliate promotions in user interface elements that are clearly identified as belonging to the add-on are acceptable. Security, Compliance and Blocking We expect all add-ons, whether hosted on addons.mozilla.org or not, to be secure and well-maintained in how they handle both their own data and their users’ data. They must also securely manage all of their interactions with the web and the browser and the operating system. Policy Enforcement Mozilla may reject or block affected versions or entire add-ons that don’t comply with the above policies, depending on the extent of their non-compliance. Mozilla may attempt to contact the add-on’s developer(s) and provide a reasonable time frame for the problems to be corrected before a block is deployed. If an add-on appears to intentionally or repeatedly violate the policies, or its developers have proven unreachable, unresponsive, or uncooperative, blocking may be immediate. Mozilla reserves the right to block or delete any developer’s account on addons.mozilla.org, thereby preventing further use of the service, for certain violations of Mozilla’s policies. For more information about rejection and blocking, see What does review rejection mean to users? Tags: add-ons review policies Contributors: kewisch rebloor wagnerand atsay jvillalobos wbamberg kmaglione dotproto Last update: dotproto Sep 17, 2025 Up Next Publish Add-on Policies FAQ Publish Firefox Add-on Distribution Agreement Publish Add-ons Blocking Process Documentation Topics Develop Publish Manage Enterprise Themes Connect With Us Twitter For developers: @mozamo For end users: @rockyourfirefox More Matrix Community forum Extensions Developer Newsletter Stay up-to-date on news and events for Firefox extension developers. Email Address I’m okay with Mozilla handling my info as explained in this Privacy Notice . Sign up Thanks! Please check your inbox to confirm your subscription. If you haven’t previously confirmed a subscription to a Mozilla-related newsletter you may have to do so. Please check your inbox or your spam filter for an email from us. Mozilla Add-ons About Blog Developer Hub Developer Policies Forum Firefox Download Firefox Desktop Mobile Features Beta, Nightly, Developer Edition Twitter (@firefox) YouTube (firefoxchannel) Github (mozilla) Website Privacy Notice Cookies Legal Edit this page on GitHub Portions of this content are ©1998–2025 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T09:30:12 |
https://github.com/nuxt/nuxt/pull/27520 | feat(kit,schema): improve type safety of `defineNuxtModule` options by DamianGlowala · Pull Request #27520 · nuxt/nuxt · GitHub Skip to content Navigation Menu Toggle navigation Sign in Appearance settings Platform AI CODE CREATION GitHub Copilot Write better code with AI GitHub Spark Build and deploy intelligent apps GitHub Models Manage and compare prompts MCP Registry New Integrate external tools DEVELOPER WORKFLOWS Actions Automate any workflow Codespaces Instant dev environments Issues Plan and track work Code Review Manage code changes APPLICATION SECURITY GitHub Advanced Security Find and fix vulnerabilities Code security Secure your code as you build Secret protection Stop leaks before they start EXPLORE Why GitHub Documentation Blog Changelog Marketplace View all features Solutions BY COMPANY SIZE Enterprises Small and medium teams Startups Nonprofits BY USE CASE App Modernization DevSecOps DevOps CI/CD View all use cases BY INDUSTRY Healthcare Financial services Manufacturing Government View all industries View all solutions Resources EXPLORE BY TOPIC AI Software Development DevOps Security View all topics EXPLORE BY TYPE Customer stories Events & webinars Ebooks & reports Business insights GitHub Skills SUPPORT & SERVICES Documentation Customer support Community forum Trust center Partners Open Source COMMUNITY GitHub Sponsors Fund open source developers PROGRAMS Security Lab Maintainer Community Accelerator Archive Program REPOSITORIES Topics Trending Collections Enterprise ENTERPRISE SOLUTIONS Enterprise platform AI-powered developer platform AVAILABLE ADD-ONS GitHub Advanced Security Enterprise-grade security features Copilot for Business Enterprise-grade AI features Premium Support Enterprise-grade 24/7 support Pricing Search or jump to... Search code, repositories, users, issues, pull requests... --> Search Clear Search syntax tips Provide feedback --> We read every piece of feedback, and take your input very seriously. Include my email address so I can be contacted Cancel Submit feedback Saved searches Use saved searches to filter your results more quickly --> Name Query To see all available qualifiers, see our documentation . Cancel Create saved search Sign in Sign up Appearance settings Resetting focus You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert {{ message }} nuxt / nuxt Public Uh oh! There was an error while loading. Please reload this page . Notifications You must be signed in to change notification settings Fork 5.5k Star 59.3k Code Issues 816 Pull requests 114 Discussions Actions Projects 1 Security Uh oh! There was an error while loading. Please reload this page . Insights Additional navigation options Code Issues Pull requests Discussions Actions Projects Security Insights feat(kit,schema): improve type safety of defineNuxtModule options #27520 New issue Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Sign up for GitHub By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement . We’ll occasionally send you account related emails. Already on GitHub? Sign in to your account Jump to bottom Merged danielroe merged 15 commits into main from feat/define-nuxt-module-overhaul Jun 21, 2024 Merged feat(kit,schema): improve type safety of defineNuxtModule options #27520 danielroe merged 15 commits into main from feat/define-nuxt-module-overhaul Jun 21, 2024 Conversation 2 Commits 15 Checks 0 Files changed Uh oh! There was an error while loading. Please reload this page . Conversation This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters Show hidden characters Copy link Member DamianGlowala commented Jun 11, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page . 🔗 Linked issue 📚 Description Currently, defining the defaults for options in defineNuxtModule does not impact the type of resolvedOptions param within the setup function. Their types are disconnected, which this PR aims to address. As of today, TypeScript does not support partial inference of generic type params. Due to this fact, I'd like to suggest adding an extra function call (named with ), which can handle merging inferred defaults with the module options generic type param and therefore improve both the type safety and DX: type ModuleOptions = { option1: string option2: number } defineNuxtModule<ModuleOptions>().with({ defaults: { option1: 'foo' }, setup: (resolvedOptions) => {} // ^? { option1: string, option2?: number | undefined } }) --> Sorry, something went wrong. Uh oh! There was an error while loading. Please reload this page . --> ❤️ 3 ineshbose, serkodev, and who-jonson reacted with heart emoji All reactions ❤️ 3 reactions DamianGlowala and others added 10 commits April 19, 2024 08:40 feat(kit,schema): improve type inference in defineNuxtModule a528cdd refactor: remove obsolete union with undefined fe5d905 fix: remove test calls 5307fe3 refactor: rename ResolvedOptions to ResolvedModuleOptions 91daaa2 Merge branch 'main' into feat/define-nuxt-module-overhaul 8ef7d80 Merge branch 'main' into feat/define-nuxt-module-overhaul b573900 feat: prettify type of resolved options bf06480 feat: add type test cc0b934 Merge branch 'main' into feat/define-nuxt-module-overhaul da28c80 chore: add fallback d4317f0 Copy link bolt-new-by-stackblitz bot commented Jun 11, 2024 Run & review this pull request in StackBlitz Codeflow . --> All reactions --> Sorry, something went wrong. Uh oh! There was an error while loading. Please reload this page . github-actions bot added 3.x enhancement labels Jun 11, 2024 Merge remote-tracking branch 'origin/main' into feat/define-nuxt-modu… … 37941d8 …le-overhaul DamianGlowala self-assigned this Jun 11, 2024 DamianGlowala added 2 commits June 12, 2024 19:57 fix: correctly resolve options for defineNuxtModule without .with() 272ec74 fix: add defaults for NuxtModule generic type parameters 96e2083 DamianGlowala requested a review from danielroe June 12, 2024 18:23 danielroe approved these changes Jun 12, 2024 View reviewed changes Copy link Member danielroe left a comment There was a problem hiding this comment. Choose a reason for hiding this comment The reason will be displayed to describe this comment to others. Learn more . --> Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Hide comment Thank you! ❤️ --> Sorry, something went wrong. Uh oh! There was an error while loading. Please reload this page . --> ❤️ 1 DamianGlowala reacted with heart emoji All reactions ❤️ 1 reaction danielroe added 2 commits June 20, 2024 23:31 Merge remote-tracking branch 'origin/main' into feat/define-nuxt-modu… … 1074809 …le-overhaul chore: add default return value 4eabcab danielroe merged commit e374474 into main Jun 21, 2024 danielroe deleted the feat/define-nuxt-module-overhaul branch June 21, 2024 08:33 github-actions bot mentioned this pull request Jun 21, 2024 v4.0.0 #27716 Merged danielroe pushed a commit that referenced this pull request Aug 8, 2024 feat(kit,schema): add .with for better module options types ( #27520 ) 5609250 github-actions bot mentioned this pull request Aug 8, 2024 v3.13.0 #28466 Merged 5 tasks mjbullman mentioned this pull request Sep 13, 2024 [Snyk] Upgrade: , nuxt mjbullman/martin-bulllman-app#29 Merged Abhishek-Mallick mentioned this pull request Sep 14, 2024 [Snyk] Upgrade nuxt from 3.12.4 to 3.13.0 Abhishek-Mallick/universal-box#54 Merged gretchelin mentioned this pull request Sep 26, 2024 [Snyk] Upgrade nuxt from 3.13.0 to 3.13.1 gretchelin/poc-nuxt-ddd#1 Merged Kamsou pushed a commit to Kamsou/nuxt that referenced this pull request Feb 5, 2025 feat(kit,schema): add .with for better module options types ( nuxt#2… … a101261 …7520 ) This was referenced Jul 25, 2025 Modules: Allow author to define separate typing for user-config and resulting runtime-config #20264 Closed docs: add example for module .with() #32757 Merged --> Sign up for free to join this conversation on GitHub . Already have an account? Sign in to comment --> Reviewers danielroe danielroe approved these changes --> Assignees DamianGlowala Labels 3.x enhancement --> Projects None yet --> Milestone No milestone --> Development Successfully merging this pull request may close these issues. Uh oh! There was an error while loading. Please reload this page . 3 participants Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later. Footer © 2026 GitHub, Inc. Footer navigation Terms Privacy Security Status Community Docs Contact Manage cookies Do not share my personal information You can’t perform that action at this time. | 2026-01-13T09:30:12 |
https://developers.google.com/admob/api/reference/rest/v1beta/accounts.mediationGroups/create | Method: accounts.mediationGroups.create | AdMob API | Google for Developers Skip to main content AdMob API / English Deutsch Español Español – América Latina Français Indonesia Italiano Polski Português – Brasil Tiếng Việt Türkçe Русский עברית العربيّة فارسی हिंदी বাংলা ภาษาไทย 中文 – 简体 中文 – 繁體 日本語 한국어 Sign in AdMob Guides Reference Libraries & Examples Support AdMob API AdMob Guides Reference Libraries & Examples Support Release notes AdMob API v1 REST Resources accounts Overview get list accounts.adUnits Overview list accounts.apps Overview list accounts.mediationReport Overview generate accounts.networkReport Overview generate Types DateRange LocalizationSettings ReportFooter ReportHeader ReportRow SortOrder StringList v1beta REST Resources accounts Overview get list accounts.adSources Overview list accounts.adSources.adapters Overview list accounts.adUnitMappings Overview batchCreate accounts.adUnits Overview create list accounts.adUnits.adUnitMappings Overview create list accounts.apps Overview create list accounts.campaignReport Overview generate accounts.mediationGroups Overview create list patch accounts.mediationGroups.mediationAbExperiments Overview create stop accounts.mediationReport Overview generate accounts.networkReport Overview generate Types DateRange LocalizationSettings MediationGroupLine ReportFooter ReportHeader ReportRow SortOrder StringList API dictionary Ad sources Adapters Home Products AdMob API Reference Method: accounts.mediationGroups.create Stay organized with collections Save and categorize content based on your preferences. Page Summary outlined_flag This document provides a reference for creating a mediation group under a specific AdMob account using the AdMob API. The HTTP request method is POST to the specified URL, which uses gRPC Transcoding syntax. The only required path parameter is parent , which specifies the AdMob account owner using the format accounts/{publisherId} . The request body should contain an instance of MediationGroup , and a successful response will contain a newly created MediationGroup instance in the response body. Creating a mediation group requires authorization with the https://www.googleapis.com/auth/admob.monetization OAuth scope and may require reaching out to your account manager for access if a 403 permission denied error is encountered. HTTP request Path parameters Request body Response body Authorization scopes Examples Try it! Create a mediation group under the specific AdMob account. This method has limited access. If you see a 403 permission denied error, please reach out to your account manager for access. HTTP request POST https://admob.googleapis.com/v1beta/{parent=accounts/*}/mediationGroups The URL uses gRPC Transcoding syntax. Path parameters Parameters parent string Required. The parent which owns the mediation group. Format: accounts/{publisherId} Request body The request body contains an instance of MediationGroup . Response body If successful, the response body contains a newly created instance of MediationGroup . Authorization scopes Requires the following OAuth scope: https://www.googleapis.com/auth/admob.monetization For more information, see the OAuth 2.0 Overview . Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License , and code samples are licensed under the Apache 2.0 License . For details, see the Google Developers Site Policies . Java is a registered trademark of Oracle and/or its affiliates. Last updated 2025-08-20 UTC. [[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-20 UTC."],[],["This describes how to create a mediation group within an AdMob account using a POST request. The request is sent to a specific URL including the account's publisher ID, and requires OAuth authorization. The request body should contain a `MediationGroup` instance. Upon success, the response body returns the newly created `MediationGroup`. Note: Access to this method is limited and may need special permissions from the account manager.\n"]] Product info Usage limits Pricing Terms of Service Programs Google Developer Program Google Developer Groups Google Developer Experts Accelerators Google Cloud & NVIDIA Developer consoles Google API Console Google Cloud Platform Console Google Play Console Firebase Console Actions on Google Console Cast SDK Developer Console Chrome Web Store Dashboard Google Home Developer Console Android Chrome Firebase Google Cloud Platform Google AI All products Terms Privacy Manage cookies English Deutsch Español Español – América Latina Français Indonesia Italiano Polski Português – Brasil Tiếng Việt Türkçe Русский עברית العربيّة فارسی हिंदी বাংলা ภาษาไทย 中文 – 简体 中文 – 繁體 日本語 한국어 | 2026-01-13T09:30:12 |
https://developer.android.com/security/fraud-prevention?hl=tr | Sahtekarlığı Önleme {7/}|{6/} Android Geliştiricileri | Fraud prevention | Android Developers Ana içeriğe atla Kaçırmamanız gereken oyunlar Yapay zeka deneyimleri oluşturma Gemini API'leri ve daha fazlasıyla yapay zeka destekli Android uygulamaları geliştirin. Başlama Başlama İlk uygulamanızı oluşturarak başlayın. Eğitim kurslarımızla daha ayrıntılı bilgi edinin veya uygulama geliştirmeyi kendi kendinize öğrenin. Hello world Eğitim kursları Eğitimler Ekipler için Compose Android için Kotlin Google Play ile para kazanma ↗️ Android Geliştirici Doğrulaması Cihaza göre genişletme Kullanıcılarınıza telefondan tablete, kol saatinden kulaklığa kadar her cihazda sorunsuz deneyimler sunan uygulamalar geliştirin. Uyarlanabilir uygulamalar Android XR Wear OS Arabalar için Android Android TV ChromeOS Kategoriye göre oluşturma Google'ın yönlendirici ve kişisel görüşe dayalı rehberliğini takip ederek kullanım alanınıza uygun çözümler geliştirmeyi öğrenin. Oyunlar Kamera ve medya Sosyal ve mesajlaşma Sağlık ve form koruma Verimlilik Kurumsal uygulamalar En son sürümünü edinin Yıl boyunca yeni çıkanları takip edin, önizleme programlarımıza katılın ve geri bildirimlerinizi bizimle paylaşın. Son güncellemeler Deneysel güncellemeler Android Studio önizlemesi Jetpack ve Compose kitaplıkları Wear OS sürümleri Özel Korumalı Alan ↗️ Tasarım ve Planlama Mükemmel deneyimler En iyi kullanıcılarınız için en iyi deneyimleri oluşturun. Daha fazla bilgi Kullanıcı arayüzü tasarımı Android'deki en iyi uygulamaları kullanarak güzel bir kullanıcı arayüzü tasarlayın. Android için tasarım Cep Uyarlanabilir kullanıcı arayüzü XR Kulaklıklar ve XR Gözlükler Yapay Zeka Gözlükleri Widget'lar Wear OS Android TV Arabalar için Android Mimari Güçlü, test edilebilir ve bakımı yapılabilir uygulama mantığı ve hizmetleri tasarlayın. Giriş Kütüphaneler Gezinme Modülerleştirme Test Kotlin Multiplatform Kalite Uygulama kalitesini planlayın ve Play Store yönergelerine uyun. Genel bakış Temel değer Kullanıcı deneyimi Erişilebilirlik Teknik kalite Mükemmel deneyimler Güvenlik Kullanıcıları tehditlere karşı koruyun ve güvenli bir Android deneyimi sağlayın. Genel bakış Gizlilik İzinler Kimlik Sahtekarlığı önleme Geliştirme Android Studio'da Gemini Android geliştirmede yapay zeka geliştirme arkadaşınız. Daha fazla bilgi Android Studio'yu edinme Temel alanlar İhtiyacınız olan özelliklerle ilgili örnekleri ve dokümanları edinin. Örnekler Kullanıcı arayüzleri Arka plan çalışması Veriler ve dosyalar Bağlanabilirlik Tüm temel alanlar ⤵️ Araçlar ve iş akışı Uygulamanızı yazmak ve oluşturmak için IDE'yi kullanın veya kendi işlem hattınızı oluşturun. Kod yazma ve hata ayıklama Proje oluşturma Uygulamanızı test etme Performans Komut satırı araçları Gradle eklentisi API'si Cihaz teknolojisi Form faktörleri için kod yazma Cihazları bağlayın ve verileri paylaşın. Uyarlanabilir kullanıcı arayüzü Wear OS Android XR Android Health Arabalar için Android Android TV Tüm cihazlar ⤵️ Kütüphaneler Tüm ayrıntıları içeren API referans belgelerine göz atın. Android platformu Jetpack kitaplıkları Compose kitaplıkları Google Play Hizmetleri ↗️ Google Play SDK Dizini ↗️ Google Play Play Console Uygulamanızı veya oyununuzu yayınlayın ve Google Play'de işinizi büyütün. Play Console'a git Daha fazla bilgi ↗️ Temel Bilgiler Kullanıcılarla etkileşim kurmayı, uygulamanızdan para kazanmayı ve uygulamanızı güvenli hale getirmeyi öğrenin. Play'de para kazanma Play Integrity Play Politikaları Play Programları ↗️ Games Dev Center Oyun geliştirme ve yayınlama Araçlar, indirilenler ve örnekler Genel bakış Play Asset Delivery Play Games Hizmetleri PC Üzerinde Play Games Tüm Play rehberleri ⤵️ Kütüphaneler Tüm ayrıntıları içeren API referans belgelerine göz atın. Play Özellik Dağıtımı Play uygulama içi güncellemeleri Play uygulama içi yorumları Play Install Referrer Google Play Hizmetleri ↗️ Google Play SDK Dizini ↗️ Tüm Play kitaplıkları ⤵️ Araçlar ve kaynaklar Uygulamanızı yayınlama, tanıtma ve yönetme araçları. Android App Bundle Marka ve pazarlama Play Console API'leri ↗️ Topluluk / English Deutsch Español – América Latina Français Indonesia Italiano Polski Português – Brasil Tiếng Việt Türkçe Русский العربيّة فارسی বাংলা 中文 – 简体 中文 – 繁體 日本語 한국어 Android Studio Oturum aç Security Fraud prevention Genel bakış Temel değer Kullanıcı deneyimi Teknik kalite Gizlilik ve Güvenlik Kaçırmamanız gereken oyunlar Diğer Tasarım ve Planlama Diğer Genel bakış Temel değer Kullanıcı deneyimi Teknik kalite Gizlilik ve Güvenlik Geliştirme Diğer Google Play Diğer Topluluk Android Studio Genel bakış Android uygulamalarınızın güvenliğini sağlama ⍈ Gizlilik için tasarım ⍈ Kullanıcı kimliğini yönetme ⍈ Kullanıcıları sahtekarlıktan koruma ⍈ Yapay zeka deneyimleri oluşturma Başlama Başlama Hello world Eğitim kursları Eğitimler Ekipler için Compose Android için Kotlin Google Play ile para kazanma ↗️ Android Geliştirici Doğrulaması Cihaza göre genişletme Uyarlanabilir uygulamalar Android XR Wear OS Arabalar için Android Android TV ChromeOS Kategoriye göre oluşturma Oyunlar Kamera ve medya Sosyal ve mesajlaşma Sağlık ve form koruma Verimlilik Kurumsal uygulamalar En son sürümünü edinin Son güncellemeler Deneysel güncellemeler Android Studio önizlemesi Jetpack ve Compose kitaplıkları Wear OS sürümleri Özel Korumalı Alan ↗️ Mükemmel deneyimler Daha fazla bilgi Kullanıcı arayüzü tasarımı Android için tasarım Cep Uyarlanabilir kullanıcı arayüzü XR Kulaklıklar ve XR Gözlükler Yapay Zeka Gözlükleri Widget'lar Wear OS Android TV Arabalar için Android Mimari Giriş Kütüphaneler Gezinme Modülerleştirme Test Kotlin Multiplatform Kalite Genel bakış Temel değer Kullanıcı deneyimi Erişilebilirlik Teknik kalite Mükemmel deneyimler Güvenlik Genel bakış Gizlilik İzinler Kimlik Sahtekarlığı önleme Android Studio'da Gemini Daha fazla bilgi Android Studio'yu edinme Temel alanlar Örnekler Kullanıcı arayüzleri Arka plan çalışması Veriler ve dosyalar Bağlanabilirlik Tüm temel alanlar ⤵️ Araçlar ve iş akışı Kod yazma ve hata ayıklama Proje oluşturma Uygulamanızı test etme Performans Komut satırı araçları Gradle eklentisi API'si Cihaz teknolojisi Uyarlanabilir kullanıcı arayüzü Wear OS Android XR Android Health Arabalar için Android Android TV Tüm cihazlar ⤵️ Kütüphaneler Android platformu Jetpack kitaplıkları Compose kitaplıkları Google Play Hizmetleri ↗️ Google Play SDK Dizini ↗️ Play Console Play Console'a git Daha fazla bilgi ↗️ Temel Bilgiler Play'de para kazanma Play Integrity Play Politikaları Play Programları ↗️ Games Dev Center Genel bakış Play Asset Delivery Play Games Hizmetleri PC Üzerinde Play Games Tüm Play rehberleri ⤵️ Kütüphaneler Play Özellik Dağıtımı Play uygulama içi güncellemeleri Play uygulama içi yorumları Play Install Referrer Google Play Hizmetleri ↗️ Google Play SDK Dizini ↗️ Tüm Play kitaplıkları ⤵️ Araçlar ve kaynaklar Android App Bundle Marka ve pazarlama Play Console API'leri ↗️ Android Developers Tasarım ve Planlama Security Fraud prevention Gizlilik ve Güvenlik Koleksiyonlar ile düzeninizi koruyun İçeriği tercihlerinize göre kaydedin ve kategorilere ayırın. Kullanıcıları sahtekarlıktan koruma Güvenlik alanında hiçbir çözüm veya taktik, sahtekarlığı ve hırsızlığı tamamen önleyemez. Bir cihaz çalındığında kullanıcılar, cihaz uzaktan kilitlenmeden önce uygulamalarını kötüye kullanmaya ve kişisel verilerini çıkarmaya çalışan saldırganlara karşı bir zaman yarışına girer. Kullanıcılarınız sahtekarlık riski altında mı? Telefon hırsızlığının kötüye kullanımını azaltabilir misiniz? Uygulama güvenliğiyle ilgili dikkate alınması gereken önemli sorular Uygulama yürütme ortamı güvenilir mi? Cihazın kriptografik olarak doğrulanabileceğinden emin olun. Yayınlanan uygulamanızın gerçek olduğunu ve üzerinde oynanmadığını doğrulayın. Cihazda riski artıran ayarlar veya uygulamalar olup olmadığını kontrol edin. Cihazdaki başka uygulamaların, uygulamanızı kontrol etme riski olup olmadığını inceleyin. Sunucunuzun, aldığı isteğin özgünlüğünü ve bütünlüğünü doğrulayabildiğinden emin olun. Daha fazla bilgi Hassas içerik korunuyor mu? Kullanıcının hassas işlemlerinin güvenilmeyen uygulamalar tarafından açığa çıkarılmadığından veya izlenmediğinden emin olun. Bildirimlere, kilitli ekran üzerinde gösterilebilecek hassas içerikler eklemekten kaçının. Şifre sıfırlama mekanizmalarını yerel saldırılara karşı daha dayanıklı olacak şekilde tasarlayın. Kullanıcının cihazına fiziksel erişimi olan kişilerin yetkisiz hesap sıfırlamalarını ve veri erişimini engellemek için önlemler alın. Daha fazla bilgi Bu, beklenen kullanıcı ve kullanıcı davranışı mı? Giriş yapmış olan kullanıcının hesabın gerçek sahibi olduğundan emin olmak için sağlam kimlik doğrulama mekanizmaları uygulayın. Kullanıcıları kimlik avı saldırılarının nasıl tespit edip önleyecekleri konusunda eğitin. Yetkisiz erişimi ve kullanımı önlemek için cihaz güvenlik önlemleri uygulayın. Yetkisiz işlem riskini azaltmak amacıyla kritik işlemler için kullanıcılardan açıkça onay isteyin. Finans uygulamaları, işlemlerin değerli ve kolay bir şekilde yürütülmesi nedeniyle sahtekarlık konusunda en önemli hedeflerden biridir. Telefon hırsızlığı durumunda finansal uygulamalar, hırsızlıklarından para kazanmak isteyen saldırganlar için değerli bir hedef işlevi görür. Bu belgede, telefon hırsızlığı ve sahtekarlığı tespit etmenize, ele almanıza ve azaltmanıza yardımcı olacak araçlara ve kaynaklara genel bir bakış sunulmaktadır. Uygulama geliştiricilerin uygulamalarında mali sahtekarlığı azaltmaları için önerdiğimiz farklı ürünler, API'ler, kod örnekleri ve en iyi uygulamalar etrafında düzenlenmiştir. Daha fazla bilgi Kullanıcı korumaları Play Protect Play Protect artık daha önce taranmamış uygulamaları yüklerken artık gerçek zamanlı uygulama taraması yapılmasını öneriyor. Güvenli ekran paylaşımı Android 15'ten itibaren Ekran Paylaşımı artık varsayılan olarak tek bir uygulama paylaşacak. Kullanıcılar gerekirse tüm ekranlarını paylaşmak için bu ayarı düzenleyebilirler. Ekran paylaşımı sırasında, bildirimlerin geliştirici tarafından sağlanan herkese açık sürümü veya bildirim içeriğinin kaldırılmış gizli sürümü gösterilir. Gizli verileri akıllı maskeleme Tek kullanımlık şifreler ve giriş ekranlarıyla bildirim yayınlayan uygulamalar da ekran paylaşımı sırasında uzaktaki izleyicilerden gizlenir. Android 15'ten itibaren bildirim dinleyici hizmetine sahip çoğu uygulama, tek kullanımlık şifre içeriği kaldırıldığında bildirim alacaktır. Hırsızlığa karşı korumalar Son olarak, Android 15'te kapma koruması ve uzaktan hızlı kilit gibi cihaz hırsızlığına karşı yeni korumalar bulunur. Kaplama koruması, birisi kullanıcının telefonunu aldığında veya aldığında ekranı kilitler. Uzaktan hızlı kilit özelliği, kullanıcıların Google şifresini hatırlamasalar bile cihazlarını uzaktan kolayca kilitlemelerini sağlar. Daha fazla bilgi En iyi uygulamalarla ilgili daha fazla bilgi edinmek için aşağıdaki kaynaklara göz atın. Güvenlikle ilgili Android dokümanları Varsayılan olarak güvenli ve gizlilik odaklı tasarıma sahip bu uygulamada Android'in güvenlikle ilgili en iyi uygulamalarını öğrenin. Güvenli ve özel uygulamalar tasarlayın, uygulayın ve dağıtın. Devamı Play bütünlük dokümanları Play Integrity API, uygulamaları sahtekarlık ve kötüye kullanıma karşı korumaya yardımcı olur. Uygulama etkileşimlerinizin yetkili cihazlardan ve uygulamalardan kaynaklandığını doğrulayın. Devamı Android 15 değişiklikleri Değişiklikler arasında arka plan etkinliği başlatmalarının kısıtlanması, amaçların daha güvenli hale getirilmesi ve kullanıcıları, Rahatsız Etmeyin durumunu değiştirmeye çalışan kötü amaçlı uygulamalardan koruma yer alıyor. Devamı Monzo'dan dolandırıcılık amaçlı aramaları önlemek için en iyi uygulamalar Monzo, gerçek temsilcileri doğrulamaya yarayan yeni arama durumu özelliği sayesinde kimliğe bürünme dolandırıcılıklarıyla mücadele ediyor. Devamı Bu sayfadaki içerik ve kod örnekleri, İçerik Lisansı sayfasında açıklanan lisanslara tabidir. Java ve OpenJDK, Oracle ve/veya satış ortaklarının tescilli ticari markasıdır. Son güncelleme tarihi: 2024-07-02 UTC. [[["Anlaması kolay","easyToUnderstand","thumb-up"],["Sorunumu çözdü","solvedMyProblem","thumb-up"],["Diğer","otherUp","thumb-up"]],[["İhtiyacım olan bilgiler yok","missingTheInformationINeed","thumb-down"],["Çok karmaşık / çok fazla adım var","tooComplicatedTooManySteps","thumb-down"],["Güncel değil","outOfDate","thumb-down"],["Çeviri sorunu","translationIssue","thumb-down"],["Örnek veya kod sorunu","samplesCodeIssue","thumb-down"],["Diğer","otherDown","thumb-down"]],["Son güncelleme tarihi: 2024-07-02 UTC."],[],[]] X X'te @AndroidDev'i takip edin YouTube YouTube'da Android Developers'a göz atın LinkedIn Connect with the Android Developers community on LinkedIn Android hakkında daha fazla Android İşletmeler için Android Güvenlik Kaynak Haber Blog Podcast'ler Keşfet Oyun Makine Öğrenimi Sağlık ve Fitness Kamera ve Medya Gizlilik 5G Android Cihazlar Büyük ekranlar Wear OS ChromeOS cihazlar Arabalar için Android Android TV Sürümler Android 15 Android 14 Android 13 Android 12 Android 11 Android 10 Pie Belgeler ve İndirmeler Android Studio kılavuzu Geliştirici kılavuzları API referansı Studio'yu indir Android NDK Destek Platform hatası bildir Belge hatası bildir Google Play support Araştırma çalışmalarına katıl Android Chrome Firebase Google Cloud Platform Tüm ürünler Gizlilik Lisans Marka kuralları Manage cookies E-postayla haberler ve ipuçları al Abone ol English Deutsch Español – América Latina Français Indonesia Italiano Polski Português – Brasil Tiếng Việt Türkçe Русский العربيّة فارسی বাংলা 中文 – 简体 中文 – 繁體 日本語 한국어 | 2026-01-13T09:30:12 |
https://www.linkedin.com/products/semiologic-graphcomment-system/?trk=products_seo_search#main-content | GraphComment | LinkedIn Skip to main content LinkedIn Semiologic in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in GraphComment Commenting Systems by Semiologic See who's skilled in this Add as skill Learn more Report this product About GraphComment est un système de commentaire qui vous aide à bâtir une communauté active à partir de l’audience d’un site web. Elle possède des fonctionnalités innovantes, des outils puissants, et est facile à installer. Media Products media viewer No more previous content Interface BubbleFlow FR Profils utilisateurs Personnalisation Plugin WordPress Admin facile No more next content Featured customers of GraphComment Reworld Media Technology, Information and Internet 19,346 followers Orange Telecommunications 1,195,427 followers FRANCE-ANTILLES / FRANCE-GUYANE Book and Periodical Publishing 19,364 followers LE PHOCEEN Technology, Information and Internet 816 followers 20 Minutes France Newspaper Publishing 94,741 followers franceinfo Radio and Television Broadcasting 14,462 followers Il Post Book and Periodical Publishing 28,492 followers Les Echos Newspaper Publishing 906,645 followers Basket USA Internet News 502 followers Show more Show less Similar products Coral Coral Commenting Systems IntenseDebate IntenseDebate Commenting Systems ProjectHuddle ProjectHuddle Commenting Systems CommentSold CommentSold Commenting Systems Superflow Superflow Commenting Systems Thrive Comments Thrive Comments Commenting Systems Sign in to see more Show more Show less Semiologic products GraphDebate GraphDebate Online Community Software LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:30:12 |
https://extensionworkshop.com/documentation/publish/add-on-policies/#firefox-tools | Add-on Policies | Firefox Extension Workshop Extension Workshop Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Submit or Manage Extensions Search Submit or Manage Extensions Search Select a section Page Name Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise <a href="https://support.mozilla.org/kb | 2026-01-13T09:30:12 |
https://developers.cloudflare.com/ai-gateway/usage/providers/workersai/ | Workers AI · Cloudflare AI Gateway docs Skip to content Cloudflare Docs Search Docs Directory APIs SDKs Help Log in Select theme Dark Light Auto AI Gateway No results found. Try a different search term, or use our global search . Overview Getting started Using AI Gateway Unified API (OpenAI compat) Provider Native Workers AI Amazon Bedrock Anthropic Azure OpenAI Baseten Cartesia Cerebras Cohere Deepgram DeepSeek ElevenLabs Fal AI Google AI Studio Google Vertex AI Groq HuggingFace Ideogram Mistral AI OpenAI OpenRouter Parallel Perplexity Replicate xAI WebSockets API Beta Overview Realtime WebSockets API Non-realtime WebSockets API Features Overview Unified Billing Caching Rate limiting Dynamic routing Beta Overview Using a dynamic route JSON Configuration Data Loss Prevention (DLP) Beta Overview Set up Data Loss Prevention (DLP) Guardrails Beta Overview Set up Guardrails Supported model types Usage considerations Configuration BYOK (Store Keys) Beta Custom costs Custom Providers Beta Manage gateways Request handling Authenticated Gateway Observability Costs Custom metadata Analytics Logging Overview Workers Logpush Integrations Vercel AI SDK Agents ↗ AI Gateway Binding Methods Workers AI Tutorials Platform Overview Limits Pricing Audit logs Changelog Header Glossary REST API reference ↗ API MCP server ↗ MCP AI Assistant ↗ Architectures LLM resources llms.txt prompt.txt AI Gateway llms-full.txt Developer Platform llms-full.txt GitHub X.com YouTube Select theme Dark Light Auto On this page Overview Prerequisites REST API Examples OpenAI compatible endpoints Workers Binding OpenAI-Compatible Endpoint On this page Overview Prerequisites REST API Examples OpenAI compatible endpoints Workers Binding OpenAI-Compatible Endpoint Tags AI Was this helpful? Edit Issue Directory … AI Gateway Using AI Gateway Provider Native Workers AI Copy page Workers AI Use AI Gateway for analytics, caching, and security on requests to Workers AI . Workers AI integrates seamlessly with AI Gateway, allowing you to execute AI inference via API requests or through an environment binding for Workers scripts. The binding simplifies the process by routing requests through your AI Gateway with minimal setup. Prerequisites When making requests to Workers AI, ensure you have the following: Your AI Gateway Account ID. Your AI Gateway gateway name. An active Workers AI API token. The name of the Workers AI model you want to use. REST API To interact with a REST API, update the URL used for your request: Previous : https://api.cloudflare.com/client/v4/accounts/{account_id}/ai/run/{model_id} New : https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/workers-ai/{model_id} For these parameters: {account_id} is your Cloudflare account ID . {gateway_id} refers to the name of your existing AI Gateway . {model_id} refers to the model ID of the Workers AI model . Examples First, generate an API token with Workers AI Read access and use it in your request. Request to Workers AI llama model curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/workers-ai/@cf/meta/llama-3.1-8b-instruct \ --header 'Authorization: Bearer {cf_api_token}' \ --header 'Content-Type: application/json' \ --data '{"prompt": "What is Cloudflare?"}' Request to Workers AI text classification model curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/workers-ai/@cf/huggingface/distilbert-sst-2-int8 \ --header 'Authorization: Bearer {cf_api_token}' \ --header 'Content-Type: application/json' \ --data '{ "text": "Cloudflare docs are amazing!" }' OpenAI compatible endpoints Workers AI supports OpenAI compatible endpoints for text generation ( /v1/chat/completions ) and text embedding models ( /v1/embeddings ). This allows you to use the same code as you would for your OpenAI commands, but swap in Workers AI easily. Request to OpenAI compatible endpoint curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/workers-ai/v1/chat/completions \ --header 'Authorization: Bearer {cf_api_token}' \ --header 'Content-Type: application/json' \ --data '{ "model": "@cf/meta/llama-3.1-8b-instruct", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] } ' Workers Binding You can integrate Workers AI with AI Gateway using an environment binding. To include an AI Gateway within your Worker, add the gateway as an object in your Workers AI request. JavaScript TypeScript JavaScript export default { async fetch ( request , env ) { const response = await env . AI . run ( "@cf/meta/llama-3.1-8b-instruct" , { prompt : "Why should you use Cloudflare for your AI inference?" , }, { gateway : { id : "{gateway_id}" , skipCache : false , cacheTtl : 3360 , }, }, ) ; return new Response ( JSON . stringify ( response )) ; }, }; TypeScript export interface Env { AI : Ai ; } export default { async fetch ( request : Request , env : Env ) : Promise < Response > { const response = await env . AI . run ( "@cf/meta/llama-3.1-8b-instruct" , { prompt : "Why should you use Cloudflare for your AI inference?" , }, { gateway : { id : "{gateway_id}" , skipCache : false , cacheTtl : 3360 , }, }, ) ; return new Response ( JSON . stringify ( response )) ; }, } satisfies ExportedHandler < Env >; { const response = await env.AI.run( "@cf/meta/llama-3.1-8b-instruct", { prompt: "Why should you use Cloudflare for your AI inference?", }, { gateway: { id: "{gateway_id}", skipCache: false, cacheTtl: 3360, }, }, ); return new Response(JSON.stringify(response)); },} satisfies ExportedHandler ;"> For a detailed step-by-step guide on integrating Workers AI with AI Gateway using a binding, see Integrations in AI Gateway . Workers AI supports the following parameters for AI gateways: id string Name of your existing AI Gateway . Must be in the same account as your Worker. skipCache boolean(default: false) Controls whether the request should skip the cache . cacheTtl number Controls the Cache TTL . OpenAI-Compatible Endpoint You can also use the OpenAI-compatible endpoint ( /ai-gateway/usage/chat-completion/ ) to access Workers AI models using the OpenAI API schema. To do so, send your requests to: https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions Specify: { " model " : "workers-ai/{model}" } Was this helpful? Edit page Last updated: Aug 19, 2025 Previous Unified API (OpenAI compat) Next Amazon Bedrock Resources API New to Cloudflare? Directory Sponsorships Open Source Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Speed Test Is BGP Safe Yet? RPKI Toolkit Certificate Transparency Community X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings | 2026-01-13T09:30:12 |
https://developers.cloudflare.com/ai-gateway/usage/providers/perplexity/ | Perplexity · Cloudflare AI Gateway docs Skip to content Cloudflare Docs Search Docs Directory APIs SDKs Help Log in Select theme Dark Light Auto AI Gateway No results found. Try a different search term, or use our global search . Overview Getting started Using AI Gateway Unified API (OpenAI compat) Provider Native Workers AI Amazon Bedrock Anthropic Azure OpenAI Baseten Cartesia Cerebras Cohere Deepgram DeepSeek ElevenLabs Fal AI Google AI Studio Google Vertex AI Groq HuggingFace Ideogram Mistral AI OpenAI OpenRouter Parallel Perplexity Replicate xAI WebSockets API Beta Overview Realtime WebSockets API Non-realtime WebSockets API Features Overview Unified Billing Caching Rate limiting Dynamic routing Beta Overview Using a dynamic route JSON Configuration Data Loss Prevention (DLP) Beta Overview Set up Data Loss Prevention (DLP) Guardrails Beta Overview Set up Guardrails Supported model types Usage considerations Configuration BYOK (Store Keys) Beta Custom costs Custom Providers Beta Manage gateways Request handling Authenticated Gateway Observability Costs Custom metadata Analytics Logging Overview Workers Logpush Integrations Vercel AI SDK Agents ↗ AI Gateway Binding Methods Workers AI Tutorials Platform Overview Limits Pricing Audit logs Changelog Header Glossary REST API reference ↗ API MCP server ↗ MCP AI Assistant ↗ Architectures LLM resources llms.txt prompt.txt AI Gateway llms-full.txt Developer Platform llms-full.txt GitHub X.com YouTube Select theme Dark Light Auto On this page Overview Endpoint Prerequisites Examples cURL Use Perplexity through OpenAI SDK with JavaScript OpenAI-Compatible Endpoint On this page Overview Endpoint Prerequisites Examples cURL Use Perplexity through OpenAI SDK with JavaScript OpenAI-Compatible Endpoint Was this helpful? Edit Issue Directory … AI Gateway Using AI Gateway Provider Native Perplexity Copy page Perplexity Perplexity ↗ is an AI powered answer engine. Endpoint https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/perplexity-ai Prerequisites When making requests to Perplexity, ensure you have the following: Your AI Gateway Account ID. Your AI Gateway gateway name. An active Perplexity API token. The name of the Perplexity model you want to use. Examples cURL Example fetch request curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/perplexity-ai/chat/completions \ --header 'accept: application/json' \ --header 'content-type: application/json' \ --header 'Authorization: Bearer {perplexity_token}' \ --data '{ "model": "mistral-7b-instruct", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] }' Use Perplexity through OpenAI SDK with JavaScript Perplexity does not have their own SDK, but they have compatibility with the OpenAI SDK. You can use the OpenAI SDK to make a Perplexity call through AI Gateway as follows: JavaScript import OpenAI from "openai" ; const apiKey = env . PERPLEXITY_API_KEY ; const accountId = "{account_id}" ; const gatewayId = "{gateway_id}" ; const baseURL = `https://gateway.ai.cloudflare.com/v1/ ${ accountId } / ${ gatewayId } /perplexity-ai` ; const perplexity = new OpenAI ( { apiKey , baseURL , } ) ; const model = "mistral-7b-instruct" ; const messages = [ { role : "user" , content : "What is Cloudflare?" } ] ; const maxTokens = 20 ; const chatCompletion = await perplexity . chat . completions . create ( { model , messages , max_tokens : maxTokens , } ) ; OpenAI-Compatible Endpoint You can also use the OpenAI-compatible endpoint ( /ai-gateway/usage/chat-completion/ ) to access Perplexity models using the OpenAI API schema. To do so, send your requests to: https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions Specify: { " model " : "perplexity/{model}" } Was this helpful? Edit page Last updated: Nov 24, 2025 Previous Parallel Next Replicate Resources API New to Cloudflare? Directory Sponsorships Open Source Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Speed Test Is BGP Safe Yet? RPKI Toolkit Certificate Transparency Community X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings | 2026-01-13T09:30:12 |
https://developers.cloudflare.com/ai-gateway/features/guardrails/usage-considerations/ | Usage considerations · Cloudflare AI Gateway docs Skip to content Cloudflare Docs Search Docs Directory APIs SDKs Help Log in Select theme Dark Light Auto AI Gateway No results found. Try a different search term, or use our global search . Overview Getting started Using AI Gateway Unified API (OpenAI compat) Provider Native Workers AI Amazon Bedrock Anthropic Azure OpenAI Baseten Cartesia Cerebras Cohere Deepgram DeepSeek ElevenLabs Fal AI Google AI Studio Google Vertex AI Groq HuggingFace Ideogram Mistral AI OpenAI OpenRouter Parallel Perplexity Replicate xAI WebSockets API Beta Overview Realtime WebSockets API Non-realtime WebSockets API Features Overview Unified Billing Caching Rate limiting Dynamic routing Beta Overview Using a dynamic route JSON Configuration Data Loss Prevention (DLP) Beta Overview Set up Data Loss Prevention (DLP) Guardrails Beta Overview Set up Guardrails Supported model types Usage considerations Configuration BYOK (Store Keys) Beta Custom costs Custom Providers Beta Manage gateways Request handling Authenticated Gateway Observability Costs Custom metadata Analytics Logging Overview Workers Logpush Integrations Vercel AI SDK Agents ↗ AI Gateway Binding Methods Workers AI Tutorials Platform Overview Limits Pricing Audit logs Changelog Header Glossary REST API reference ↗ API MCP server ↗ MCP AI Assistant ↗ Architectures LLM resources llms.txt prompt.txt AI Gateway llms-full.txt Developer Platform llms-full.txt GitHub X.com YouTube Select theme Dark Light Auto On this page Overview Additional considerations On this page Overview Additional considerations Was this helpful? Edit Issue Directory … AI Gateway Features Guardrails Usage considerations Copy page Usage considerations Guardrails currently uses Llama Guard 3 8B ↗ on Workers AI to perform content evaluations. The underlying model may be updated in the future, and we will reflect those changes within Guardrails. Since Guardrails runs on Workers AI, enabling it incurs usage on Workers AI. You can monitor usage through the Workers AI Dashboard. Additional considerations Model availability : If at least one hazard category is set to block , but AI Gateway is unable to receive a response from Workers AI, the request will be blocked. Conversely, if a hazard category is set to flag and AI Gateway cannot obtain a response from Workers AI, the request will proceed without evaluation. This approach prioritizes availability, allowing requests to continue even when content evaluation is not possible. Latency impact : Enabling Guardrails adds some latency. Enabling Guardrails introduces additional latency to requests. Typically, evaluations using Llama Guard 3 8B on Workers AI add approximately 500 milliseconds per request. However, larger requests may experience increased latency, though this increase is not linear. Consider this when balancing safety and performance. Handling long content : When evaluating long prompts or responses, Guardrails automatically segments the content into smaller chunks, processing each through separate Guardrail requests. This approach ensures comprehensive moderation but may result in increased latency for longer inputs. Supported languages : Llama Guard 3.3 8B supports content safety classification in the following languages: English, French, German, Hindi, Italian, Portuguese, Spanish, and Thai. Streaming support : Streaming is not supported when using Guardrails. Note Llama Guard is provided as-is without any representations, warranties, or guarantees. Any rules or examples contained in blogs, developer docs, or other reference materials are provided for informational purposes only. You acknowledge and understand that you are responsible for the results and outcomes of your use of AI Gateway. Was this helpful? Edit page Last updated: Aug 19, 2025 Previous Supported model types Next BYOK (Store Keys) Resources API New to Cloudflare? Directory Sponsorships Open Source Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Speed Test Is BGP Safe Yet? RPKI Toolkit Certificate Transparency Community X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings | 2026-01-13T09:30:12 |
https://docs.google.com/spreadsheets/d/1vKxNnMfGRvLQ4r-arY4dapx15yKcOPo9JtU9vZYJx88/copy | :root{--gm3-sys-color-on-surface-rgb:31,31,31}@media screen and (prefers-color-scheme:dark){:root{--gm3-sys-color-on-surface-rgb:227,227,227}}:root{--wf-harmonize-filter-light:none;--wf-harmonize-filter-dark:none}.q4Wquf,.nfoC7c{display:block;height:25vh;position:relative}@media (min-width:600px){.q4Wquf,.nfoC7c{height:150px}}.q4Wquf.Irjbwb{height:auto}@media screen and (prefers-color-scheme:dark){.q4Wquf:not(.GtvzYd){display:none}}.nfoC7c{margin:0;overflow:hidden}.PwpMUe,.lVUmD{display:block;height:100%;margin:0 auto;width:100%}.St9mde{display:block;-webkit-filter:var(--wf-harmonize-filter-light);filter:var(--wf-harmonize-filter-light);height:100%;max-width:100%;min-height:110px;position:relative;-webkit-transform:translate(-43%,-3%);-ms-transform:translate(-43%,-3%);transform:translate(-43%,-3%);width:auto;z-index:3}@media screen and (prefers-color-scheme:dark){.St9mde{-webkit-filter:var(--wf-harmonize-filter-dark);filter:var(--wf-harmonize-filter-dark)}}.PwpMUe,.lVUmD,.St9mde{-o-object-fit:contain;object-fit:contain}.wsArZ[data-ss-mode="1"] .q4Wquf,.wsArZ[data-ss-mode="1"] .St9mde{height:auto;width:100%}.wsArZ[data-ss-mode="1"] .St9mde{max-width:400px}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .q4Wquf,.NQ5OL .St9mde{height:auto;width:100%}.NQ5OL .St9mde{max-width:400px}}.q4Wquf.NWba7e,.q4Wquf.NWba7e .St9mde{height:auto}.q4Wquf.NWba7e .St9mde{height:auto;max-width:312px;width:100%}.q4Wquf.NWba7e.zpCp3 .St9mde{max-width:unset}.q4Wquf.IiQozc .St9mde{margin:0 auto;-webkit-transform:none;-ms-transform:none;transform:none}.q4Wquf.Irjbwb .St9mde{height:auto;width:100%}.q4Wquf.EEeaqf .St9mde{max-height:144px;max-width:144px}.SnAaEd{background-image:-webkit-gradient(linear,left top,left bottom,from(rgba(233,233,233,0)),color-stop(62.22%,rgba(233,233,233,0)),color-stop(40.22%,rgb(233,233,233)),to(rgba(233,233,233,0)));background-image:-webkit-linear-gradient(top,rgba(233,233,233,0) 0,rgba(233,233,233,0) 62.22%,rgb(233,233,233) 40.22%,rgba(233,233,233,0) 100%);background-image:linear-gradient(to bottom,rgba(233,233,233,0) 0,rgba(233,233,233,0) 62.22%,rgb(233,233,233) 40.22%,rgba(233,233,233,0) 100%);height:100%;left:0;overflow:hidden;position:absolute;right:0;top:0;z-index:2}@media screen and (prefers-color-scheme:dark){.SnAaEd{display:none}}.SnAaEd::after,.SnAaEd::before{content:"";display:block;height:100%;min-width:110px;position:absolute;right:-10%;-webkit-transform:rotate(-104deg);-ms-transform:rotate(-104deg);transform:rotate(-104deg);width:25vh;z-index:2}@media (min-width:600px){.SnAaEd::after,.SnAaEd::before{width:150px}}.SnAaEd::before{background-image:-webkit-gradient(linear,left top,left bottom,from(rgba(243,243,243,0)),to(rgba(243,243,243,.9)));background-image:-webkit-linear-gradient(top,rgba(243,243,243,0) 0,rgba(243,243,243,.9) 100%);background-image:linear-gradient(to bottom,rgba(243,243,243,0) 0,rgba(243,243,243,.9) 100%);bottom:-10%}.SnAaEd::after{background-image:-webkit-gradient(linear,left top,left bottom,from(rgba(255,255,255,0)),to(rgba(255,255,255,.9)));background-image:-webkit-linear-gradient(top,rgba(255,255,255,0) 0,rgba(255,255,255,.9) 100%);background-image:linear-gradient(to bottom,rgba(255,255,255,0) 0,rgba(255,255,255,.9) 100%);bottom:-80%}.wsArZ[data-ss-mode="1"] .SnAaEd~.St9mde{width:auto}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .SnAaEd~.St9mde{width:auto}}.RHNWk .St9mde{height:auto}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .RHNWk .St9mde{width:115px}}.cf660d .St9mde{-webkit-transform:translate(-9%,-3%);-ms-transform:translate(-9%,-3%);transform:translate(-9%,-3%)}.tUhwwc .St9mde{margin:auto;max-height:230px;right:0;top:-3%;-webkit-transform:none;-ms-transform:none;transform:none}.Jkvqxd .St9mde{-webkit-transform:translate(9%,-3%);-ms-transform:translate(9%,-3%);transform:translate(9%,-3%)}.onc8Ic .St9mde{-webkit-transform:translate(var( --c-ps-s,24px ),0);-ms-transform:translate(var( --c-ps-s,24px ),0);transform:translate(var( --c-ps-s,24px ),0)}.WA89Yb .St9mde{-webkit-transform:translate(0,0);-ms-transform:translate(0,0);transform:translate(0,0)}.wsArZ[data-ss-mode="1"] .XEN8Yb .St9mde{max-width:115px}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .XEN8Yb .St9mde{max-width:115px}}@media (min-width:1240px) and (orientation:landscape),all and (min-width:1600px){.KyPKed .NQ5OL .XEN8Yb .St9mde{max-width:115px}}.IsSr6b .St9mde{max-width:300px}.mmskdd .St9mde{-webkit-transform:none;-ms-transform:none;transform:none}@-webkit-keyframes quantumWizBoxInkSpread{0%{-webkit-transform:translate(-50%,-50%) scale(.2);transform:translate(-50%,-50%) scale(.2)}100%{-webkit-transform:translate(-50%,-50%) scale(2.2);transform:translate(-50%,-50%) scale(2.2)}}@keyframes quantumWizBoxInkSpread{0%{-webkit-transform:translate(-50%,-50%) scale(.2);transform:translate(-50%,-50%) scale(.2)}100%{-webkit-transform:translate(-50%,-50%) scale(2.2);transform:translate(-50%,-50%) scale(2.2)}}@-webkit-keyframes quantumWizIconFocusPulse{0%{-webkit-transform:translate(-50%,-50%) scale(1.5);transform:translate(-50%,-50%) scale(1.5);opacity:0}100%{-webkit-transform:translate(-50%,-50%) scale(2);transform:translate(-50%,-50%) scale(2);opacity:1}}@keyframes quantumWizIconFocusPulse{0%{-webkit-transform:translate(-50%,-50%) scale(1.5);transform:translate(-50%,-50%) scale(1.5);opacity:0}100%{-webkit-transform:translate(-50%,-50%) scale(2);transform:translate(-50%,-50%) scale(2);opacity:1}}@-webkit-keyframes quantumWizRadialInkSpread{0%{-webkit-transform:scale(1.5);transform:scale(1.5);opacity:0}100%{-webkit-transform:scale(2.5);transform:scale(2.5);opacity:1}}@keyframes quantumWizRadialInkSpread{0%{-webkit-transform:scale(1.5);transform:scale(1.5);opacity:0}100%{-webkit-transform:scale(2.5);transform:scale(2.5);opacity:1}}@-webkit-keyframes quantumWizRadialInkFocusPulse{0%{-webkit-transform:scale(2);transform:scale(2);opacity:0}100%{-webkit-transform:scale(2.5);transform:scale(2.5);opacity:1}}@keyframes quantumWizRadialInkFocusPulse{0%{-webkit-transform:scale(2);transform:scale(2);opacity:0}100%{-webkit-transform:scale(2.5);transform:scale(2.5);opacity:1}}:root{--wf-tfs:calc(var(--c-tfs,32)/16*1rem);--wf-tfs-bp2:calc(var(--c-tfs,36)/16*1rem);--wf-tfs-bp3:calc(var(--c-tfs,36)/16*1rem);--wf-tfs-bp5:calc(var(--c-tfs,44)/16*1rem);--wf-stfs:calc(var(--c-stfs,16)/16*1rem);--wf-stfs-bp5:calc(var(--c-stfs,16)/16*1rem)}:root{--wf-harmonize-filter-light:none;--wf-harmonize-filter-dark:none}.Dzz9Db,.GpMPBe{display:block;height:25vh;position:relative}@media (min-width:600px){.Dzz9Db,.GpMPBe{height:150px}}@media screen and (prefers-color-scheme:dark){.Dzz9Db:not(.GtvzYd){display:none}}.Dzz9Db.Irjbwb{height:auto}.GpMPBe{margin:0;overflow:hidden}.UFQPDd,.JNOvdd{display:block;height:100%;margin:0 auto;-o-object-fit:contain;object-fit:contain;width:100%}.f4ZpM{display:block;-webkit-filter:var(--wf-harmonize-filter-light);filter:var(--wf-harmonize-filter-light);height:100%;max-width:100%;min-height:110px;position:relative;-webkit-transform:translate(-43%,-3%);-ms-transform:translate(-43%,-3%);transform:translate(-43%,-3%);width:auto;z-index:3}@media screen and (prefers-color-scheme:dark){.f4ZpM{-webkit-filter:var(--wf-harmonize-filter-dark);filter:var(--wf-harmonize-filter-dark)}}.wsArZ[data-ss-mode="1"] .Dzz9Db,.wsArZ[data-ss-mode="1"] .f4ZpM{height:auto;width:100%}.wsArZ[data-ss-mode="1"] .f4ZpM{max-width:400px}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .Dzz9Db,.NQ5OL .f4ZpM{height:auto;width:100%}.NQ5OL .f4ZpM{max-width:400px}}.Dzz9Db.utFBGf,.Dzz9Db.utFBGf .f4ZpM{height:auto}.Dzz9Db.utFBGf .f4ZpM{height:auto;max-width:312px;width:100%}.Dzz9Db.utFBGf.zpCp3 .f4ZpM{max-width:unset}.Dzz9Db.IiQozc .f4ZpM{margin:0 auto;-webkit-transform:none;-ms-transform:none;transform:none}.Dzz9Db.Irjbwb .f4ZpM{height:auto;width:100%}.Dzz9Db.EEeaqf .f4ZpM{max-height:144px;max-width:144px}.nPt1pc{background-image:-webkit-gradient(linear,left top,left bottom,from(rgba(233,233,233,0)),color-stop(62.22%,rgba(233,233,233,0)),color-stop(40.22%,rgb(233,233,233)),to(rgba(233,233,233,0)));background-image:-webkit-linear-gradient(top,rgba(233,233,233,0) 0,rgba(233,233,233,0) 62.22%,rgb(233,233,233) 40.22%,rgba(233,233,233,0) 100%);background-image:linear-gradient(to bottom,rgba(233,233,233,0) 0,rgba(233,233,233,0) 62.22%,rgb(233,233,233) 40.22%,rgba(233,233,233,0) 100%);height:100%;left:0;overflow:hidden;position:absolute;right:0;top:0;z-index:2}@media screen and (prefers-color-scheme:dark){.nPt1pc{display:none}}.nPt1pc::after,.nPt1pc::before{content:"";display:block;height:100%;min-width:110px;position:absolute;right:-10%;-webkit-transform:rotate(-104deg);-ms-transform:rotate(-104deg);transform:rotate(-104deg);width:25vh;z-index:2}@media (min-width:600px){.nPt1pc::after,.nPt1pc::before{width:150px}}.nPt1pc::before{background-image:-webkit-gradient(linear,left top,left bottom,from(rgba(243,243,243,0)),to(rgba(243,243,243,.9)));background-image:-webkit-linear-gradient(top,rgba(243,243,243,0) 0,rgba(243,243,243,.9) 100%);background-image:linear-gradient(to bottom,rgba(243,243,243,0) 0,rgba(243,243,243,.9) 100%);bottom:-10%}.nPt1pc::after{background-image:-webkit-gradient(linear,left top,left bottom,from(rgba(255,255,255,0)),to(rgba(255,255,255,.9)));background-image:-webkit-linear-gradient(top,rgba(255,255,255,0) 0,rgba(255,255,255,.9) 100%);background-image:linear-gradient(to bottom,rgba(255,255,255,0) 0,rgba(255,255,255,.9) 100%);bottom:-80%}.wsArZ[data-ss-mode="1"] .nPt1pc~.f4ZpM{width:auto}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .nPt1pc~.f4ZpM{width:auto}}.ZS7CGc .f4ZpM{height:auto}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .ZS7CGc .f4ZpM{width:115px}}.qiRZ5e .f4ZpM{-webkit-transform:translate(-9%,-3%);-ms-transform:translate(-9%,-3%);transform:translate(-9%,-3%)}.vIv7Gf .f4ZpM{margin:auto;max-height:230px;right:0;top:-3%;-webkit-transform:none;-ms-transform:none;transform:none}.nvYXVd .f4ZpM{-webkit-transform:translate(9%,-3%);-ms-transform:translate(9%,-3%);transform:translate(9%,-3%)}.uOhnzd .f4ZpM{-webkit-transform:translate(24px,0);-ms-transform:translate(24px,0);transform:translate(24px,0)}.MsYMaf .f4ZpM{-webkit-transform:translate(0,0);-ms-transform:translate(0,0);transform:translate(0,0)}.wsArZ[data-ss-mode="1"] .YIi9qf .f4ZpM{max-width:115px}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .YIi9qf .f4ZpM{max-width:115px}}.QG3Xbe .f4ZpM{max-width:300px}.F6gtje .f4ZpM{-webkit-transform:none;-ms-transform:none;transform:none}@-webkit-keyframes mdc-ripple-fg-radius-in{from{-webkit-animation-timing-function:cubic-bezier(.4,0,.2,1);animation-timing-function:cubic-bezier(.4,0,.2,1);-webkit-transform:translate(var(--mdc-ripple-fg-translate-start,0)) scale(1);transform:translate(var(--mdc-ripple-fg-translate-start,0)) scale(1)}to{-webkit-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1))}}@keyframes mdc-ripple-fg-radius-in{from{-webkit-animation-timing-function:cubic-bezier(.4,0,.2,1);animation-timing-function:cubic-bezier(.4,0,.2,1);-webkit-transform:translate(var(--mdc-ripple-fg-translate-start,0)) scale(1);transform:translate(var(--mdc-ripple-fg-translate-start,0)) scale(1)}to{-webkit-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1))}}@-webkit-keyframes mdc-ripple-fg-opacity-in{from{-webkit-animation-timing-function:linear;animation-timing-function:linear;opacity:0}to{opacity:var(--mdc-ripple-fg-opacity,0)}}@keyframes mdc-ripple-fg-opacity-in{from{-webkit-animation-timing-function:linear;animation-timing-function:linear;opacity:0}to{opacity:var(--mdc-ripple-fg-opacity,0)}}@-webkit-keyframes mdc-ripple-fg-opacity-out{from{-webkit-animation-timing-function:linear;animation-timing-function:linear;opacity:var(--mdc-ripple-fg-opacity,0)}to{opacity:0}}@keyframes mdc-ripple-fg-opacity-out{from{-webkit-animation-timing-function:linear;animation-timing-function:linear;opacity:var(--mdc-ripple-fg-opacity,0)}to{opacity:0}}.VfPpkd-ksKsZd-XxIAqe{--mdc-ripple-fg-size:0;--mdc-ripple-left:0;--mdc-ripple-top:0;--mdc-ripple-fg-scale:1;--mdc-ripple-fg-translate-end:0;--mdc-ripple-fg-translate-start:0;-webkit-tap-highlight-color:rgba(0,0,0,0);will-change:transform,opacity;position:relative;outline:none;overflow:hidden}.VfPpkd-ksKsZd-XxIAqe::before,.VfPpkd-ksKsZd-XxIAqe::after{position:absolute;border-radius:50%;opacity:0;pointer-events:none;content:""}.VfPpkd-ksKsZd-XxIAqe::before{-webkit-transition:opacity 15ms linear,background-color 15ms linear;transition:opacity 15ms linear,background-color 15ms linear;z-index:1;z-index:var(--mdc-ripple-z-index,1)}.VfPpkd-ksKsZd-XxIAqe::after{z-index:0;z-index:var(--mdc-ripple-z-index,0)}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d::before{-webkit-transform:scale(var(--mdc-ripple-fg-scale,1));-ms-transform:scale(var(--mdc-ripple-fg-scale,1));transform:scale(var(--mdc-ripple-fg-scale,1))}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d::after{top:0;left:0;-webkit-transform:scale(0);-ms-transform:scale(0);transform:scale(0);-webkit-transform-origin:center center;-ms-transform-origin:center center;transform-origin:center center}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd::after{top:var(--mdc-ripple-top,0);left:var(--mdc-ripple-left,0)}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-Tv8l5d-lJfZMc::after{-webkit-animation:mdc-ripple-fg-radius-in 225ms forwards,mdc-ripple-fg-opacity-in 75ms forwards;animation:mdc-ripple-fg-radius-in 225ms forwards,mdc-ripple-fg-opacity-in 75ms forwards}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-Tv8l5d-OmS1vf::after{-webkit-animation:mdc-ripple-fg-opacity-out .15s;animation:mdc-ripple-fg-opacity-out .15s;-webkit-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));-ms-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1))}.VfPpkd-ksKsZd-XxIAqe::before,.VfPpkd-ksKsZd-XxIAqe::after{top:-50%;left:-50%;width:200%;height:200%}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d::after{width:var(--mdc-ripple-fg-size,100%);height:var(--mdc-ripple-fg-size,100%)}.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded],.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd{overflow:visible}.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded]::before,.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded]::after,.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd::before,.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd::after{top:0;left:0;width:100%;height:100%}.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded].VfPpkd-ksKsZd-mWPk3d::before,.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded].VfPpkd-ksKsZd-mWPk3d::after,.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd.VfPpkd-ksKsZd-mWPk3d::before,.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd.VfPpkd-ksKsZd-mWPk3d::after{top:var(--mdc-ripple-top,0);left:var(--mdc-ripple-left,0);width:var(--mdc-ripple-fg-size,100%);height:var(--mdc-ripple-fg-size,100%)}.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded].VfPpkd-ksKsZd-mWPk3d::after,.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd.VfPpkd-ksKsZd-mWPk3d::after{width:var(--mdc-ripple-fg-size,100%);height:var(--mdc-ripple-fg-size,100%)}.VfPpkd-ksKsZd-XxIAqe::before,.VfPpkd-ksKsZd-XxIAqe::after{background-color:#000;background-color:var(--mdc-ripple-color,#000)}.VfPpkd-ksKsZd-XxIAqe:hover::before,.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE::before{opacity:.04;opacity:var(--mdc-ripple-hover-opacity,.04)}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe::before,.VfPpkd-ksKsZd-XxIAqe:not(.VfPpkd-ksKsZd-mWPk3d):focus::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12;opacity:var(--mdc-ripple-focus-opacity,.12)}.VfPpkd-ksKsZd-XxIAqe:not(.VfPpkd-ksKsZd-mWPk3d)::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.VfPpkd-ksKsZd-XxIAqe:not(.VfPpkd-ksKsZd-mWPk3d):active::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12;opacity:var(--mdc-ripple-press-opacity,.12)}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0.12)}.VfPpkd-Bz112c-LgbsSe{font-size:24px;width:48px;height:48px;padding:12px}.VfPpkd-Bz112c-LgbsSe.VfPpkd-Bz112c-LgbsSe-OWXEXe-e5LLRc-SxQuSe .VfPpkd-Bz112c-Jh9lGc{width:40px;height:40px;margin-top:4px;margin-bottom:4px;margin-right:4px;margin-left:4px}.VfPpkd-Bz112c-LgbsSe.VfPpkd-Bz112c-LgbsSe-OWXEXe-e5LLRc-SxQuSe .VfPpkd-Bz112c-J1Ukfc-LhBDec{max-height:40px;max-width:40px}.VfPpkd-Bz112c-LgbsSe:disabled{color:rgba(0,0,0,.38);color:var(--mdc-theme-text-disabled-on-light,rgba(0,0,0,.38))}.VfPpkd-Bz112c-LgbsSe svg,.VfPpkd-Bz112c-LgbsSe img{width:24px;height:24px}.VfPpkd-Bz112c-LgbsSe{display:inline-block;position:relative;-webkit-box-sizing:border-box;box-sizing:border-box;border:none;outline:none;background-color:transparent;fill:currentColor;color:inherit;text-decoration:none;cursor:pointer;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none;z-index:0;overflow:visible}.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-RLmnJb{position:absolute;top:50%;height:48px;left:50%;width:48px;-webkit-transform:translate(-50%,-50%);-ms-transform:translate(-50%,-50%);transform:translate(-50%,-50%)}@media screen and (forced-colors:active){.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Bz112c-J1Ukfc-LhBDec,.VfPpkd-Bz112c-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Bz112c-J1Ukfc-LhBDec{display:block}}.VfPpkd-Bz112c-LgbsSe:disabled{cursor:default;pointer-events:none}.VfPpkd-Bz112c-LgbsSe[hidden]{display:none}.VfPpkd-Bz112c-LgbsSe-OWXEXe-KVuj8d-Q3DXx{-webkit-box-align:center;-webkit-align-items:center;align-items:center;display:-webkit-inline-box;display:-webkit-inline-flex;display:inline-flex;-webkit-box-pack:center;-webkit-justify-content:center;justify-content:center}.VfPpkd-Bz112c-J1Ukfc-LhBDec{pointer-events:none;border:2px solid transparent;border-radius:6px;-webkit-box-sizing:content-box;box-sizing:content-box;position:absolute;top:50%;left:50%;-webkit-transform:translate(-50%,-50%);-ms-transform:translate(-50%,-50%);transform:translate(-50%,-50%);height:100%;width:100%;display:none}@media screen and (forced-colors:active){.VfPpkd-Bz112c-J1Ukfc-LhBDec{border-color:CanvasText}}.VfPpkd-Bz112c-J1Ukfc-LhBDec::after{content:"";border:2px solid transparent;border-radius:8px;display:block;position:absolute;top:50%;left:50%;-webkit-transform:translate(-50%,-50%);-ms-transform:translate(-50%,-50%);transform:translate(-50%,-50%);height:calc(100% + 4px);width:calc(100% + 4px)}@media screen and (forced-colors:active){.VfPpkd-Bz112c-J1Ukfc-LhBDec::after{border-color:CanvasText}}.VfPpkd-Bz112c-kBDsod{display:inline-block}.VfPpkd-Bz112c-kBDsod.VfPpkd-Bz112c-kBDsod-OWXEXe-IT5dJd,.VfPpkd-Bz112c-LgbsSe-OWXEXe-IT5dJd .VfPpkd-Bz112c-kBDsod{display:none}.VfPpkd-Bz112c-LgbsSe-OWXEXe-IT5dJd .VfPpkd-Bz112c-kBDsod.VfPpkd-Bz112c-kBDsod-OWXEXe-IT5dJd{display:inline-block}.VfPpkd-Bz112c-mRLv6{height:100%;left:0;outline:none;position:absolute;top:0;width:100%}.VfPpkd-Bz112c-LgbsSe{--mdc-ripple-fg-size:0;--mdc-ripple-left:0;--mdc-ripple-top:0;--mdc-ripple-fg-scale:1;--mdc-ripple-fg-translate-end:0;--mdc-ripple-fg-translate-start:0;-webkit-tap-highlight-color:rgba(0,0,0,0);will-change:transform,opacity}.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::after{position:absolute;border-radius:50%;opacity:0;pointer-events:none;content:""}.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::before{-webkit-transition:opacity 15ms linear,background-color 15ms linear;transition:opacity 15ms linear,background-color 15ms linear;z-index:1;z-index:var(--mdc-ripple-z-index,1)}.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::after{z-index:0;z-index:var(--mdc-ripple-z-index,0)}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Bz112c-Jh9lGc::before{-webkit-transform:scale(var(--mdc-ripple-fg-scale,1));-ms-transform:scale(var(--mdc-ripple-fg-scale,1));transform:scale(var(--mdc-ripple-fg-scale,1))}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Bz112c-Jh9lGc::after{top:0;left:0;-webkit-transform:scale(0);-ms-transform:scale(0);transform:scale(0);-webkit-transform-origin:center center;-ms-transform-origin:center center;transform-origin:center center}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd .VfPpkd-Bz112c-Jh9lGc::after{top:var(--mdc-ripple-top,0);left:var(--mdc-ripple-left,0)}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-Tv8l5d-lJfZMc .VfPpkd-Bz112c-Jh9lGc::after{-webkit-animation:mdc-ripple-fg-radius-in 225ms forwards,mdc-ripple-fg-opacity-in 75ms forwards;animation:mdc-ripple-fg-radius-in 225ms forwards,mdc-ripple-fg-opacity-in 75ms forwards}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-Tv8l5d-OmS1vf .VfPpkd-Bz112c-Jh9lGc::after{-webkit-animation:mdc-ripple-fg-opacity-out .15s;animation:mdc-ripple-fg-opacity-out .15s;-webkit-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));-ms-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1))}.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::after{top:0;left:0;width:100%;height:100%}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Bz112c-Jh9lGc::after{top:var(--mdc-ripple-top,0);left:var(--mdc-ripple-left,0);width:var(--mdc-ripple-fg-size,100%);height:var(--mdc-ripple-fg-size,100%)}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Bz112c-Jh9lGc::after{width:var(--mdc-ripple-fg-size,100%);height:var(--mdc-ripple-fg-size,100%)}.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::after{background-color:#000;background-color:var(--mdc-ripple-color,#000)}.VfPpkd-Bz112c-LgbsSe:hover .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Bz112c-Jh9lGc::before{opacity:.04;opacity:var(--mdc-ripple-hover-opacity,.04)}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Bz112c-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12;opacity:var(--mdc-ripple-focus-opacity,.12)}.VfPpkd-Bz112c-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Bz112c-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.VfPpkd-Bz112c-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Bz112c-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12;opacity:var(--mdc-ripple-press-opacity,.12)}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0.12)}.VfPpkd-Bz112c-LgbsSe:disabled:hover .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe:disabled.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Bz112c-Jh9lGc::before{opacity:0;opacity:var(--mdc-ripple-hover-opacity,0)}.VfPpkd-Bz112c-LgbsSe:disabled.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe:disabled:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Bz112c-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:0;opacity:var(--mdc-ripple-focus-opacity,0)}.VfPpkd-Bz112c-LgbsSe:disabled:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Bz112c-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.VfPpkd-Bz112c-LgbsSe:disabled:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Bz112c-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:0;opacity:var(--mdc-ripple-press-opacity,0)}.VfPpkd-Bz112c-LgbsSe:disabled.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0)}.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc{height:100%;left:0;pointer-events:none;position:absolute;top:0;width:100%;z-index:-1}.VfPpkd-dgl2Hf-ppHlrf-sM5MNb{display:inline}.VfPpkd-LgbsSe{position:relative;display:-webkit-inline-box;display:-webkit-inline-flex;display:inline-flex;-webkit-box-align:center;-webkit-align-items:center;align-items:center;-webkit-box-pack:center;-webkit-justify-content:center;justify-content:center;-webkit-box-sizing:border-box;box-sizing:border-box;min-width:64px;border:none;outline:none;line-height:inherit;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none;-webkit-appearance:none;overflow:visible;vertical-align:middle;background:transparent}.VfPpkd-LgbsSe .VfPpkd-BFbNVe-bF1uUb{width:100%;height:100%;top:0;left:0}.VfPpkd-LgbsSe::-moz-focus-inner{padding:0;border:0}.VfPpkd-LgbsSe:active{outline:none}.VfPpkd-LgbsSe:hover{cursor:pointer}.VfPpkd-LgbsSe:disabled{cursor:default;pointer-events:none}.VfPpkd-LgbsSe[hidden]{display:none}.VfPpkd-LgbsSe .VfPpkd-kBDsod{margin-left:0;margin-right:8px;display:inline-block;position:relative;vertical-align:top}[dir=rtl] .VfPpkd-LgbsSe .VfPpkd-kBDsod,.VfPpkd-LgbsSe .VfPpkd-kBDsod[dir=rtl]{margin-left:8px;margin-right:0}.VfPpkd-LgbsSe .VfPpkd-UdE5de-uDEFge{font-size:0;position:absolute;-webkit-transform:translate(-50%,-50%);-ms-transform:translate(-50%,-50%);transform:translate(-50%,-50%);top:50%;left:50%;line-height:normal}.VfPpkd-LgbsSe .VfPpkd-vQzf8d{position:relative}.VfPpkd-LgbsSe .VfPpkd-J1Ukfc-LhBDec{pointer-events:none;border:2px solid transparent;border-radius:6px;-webkit-box-sizing:content-box;box-sizing:content-box;position:absolute;top:50%;left:50%;-webkit-transform:translate(-50%,-50%);-ms-transform:translate(-50%,-50%);transform:translate(-50%,-50%);height:calc(100% + 4px);width:calc(100% + 4px);display:none}@media screen and (forced-colors:active){.VfPpkd-LgbsSe .VfPpkd-J1Ukfc-LhBDec{border-color:CanvasText}}.VfPpkd-LgbsSe .VfPpkd-J1Ukfc-LhBDec::after{content:"";border:2px solid transparent;border-radius:8px;display:block;position:absolute;top:50%;left:50%;-webkit-transform:translate(-50%,-50%);-ms-transform:translate(-50%,-50%);transform:translate(-50%,-50%);height:calc(100% + 4px);width:calc(100% + 4px)}@media screen and (forced-colors:active){.VfPpkd-LgbsSe .VfPpkd-J1Ukfc-LhBDec::after{border-color:CanvasText}}@media screen and (forced-colors:active){.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-J1Ukfc-LhBDec,.VfPpkd-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-J1Ukfc-LhBDec{display:block}}.VfPpkd-LgbsSe .VfPpkd-RLmnJb{position:absolute;top:50%;height:48px;left:0;right:0;-webkit-transform:translateY(-50%);-ms-transform:translateY(-50%);transform:translateY(-50%)}.VfPpkd-vQzf8d+.VfPpkd-kBDsod{margin-left:8px;margin-right:0}[dir=rtl] .VfPpkd-vQzf8d+.VfPpkd-kBDsod,.VfPpkd-vQzf8d+.VfPpkd-kBDsod[dir=rtl]{margin-left:0;margin-right:8px}svg.VfPpkd-kBDsod{fill:currentColor}.VfPpkd-LgbsSe-OWXEXe-dgl2Hf{margin-top:6px;margin-bottom:6px}.VfPpkd-LgbsSe{-moz-osx-font-smoothing:grayscale;-webkit-font-smoothing:antialiased;text-decoration:none}.VfPpkd-LgbsSe{padding:0 8px 0 8px}.VfPpkd-LgbsSe-OWXEXe-k8QpJ{-webkit-transition:-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:box-shadow .28s cubic-bezier(.4,0,.2,1);transition:box-shadow .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);padding:0 16px 0 16px}.VfPpkd-LgbsSe-OWXEXe-k8QpJ.VfPpkd-LgbsSe-OWXEXe-Bz112c-UbuQg{padding:0 12px 0 16px}.VfPpkd-LgbsSe-OWXEXe-k8QpJ.VfPpkd-LgbsSe-OWXEXe-Bz112c-M1Soyc{padding:0 16px 0 12px}.VfPpkd-LgbsSe-OWXEXe-MV7yeb{-webkit-transition:-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:box-shadow .28s cubic-bezier(.4,0,.2,1);transition:box-shadow .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);padding:0 16px 0 16px}.VfPpkd-LgbsSe-OWXEXe-MV7yeb.VfPpkd-LgbsSe-OWXEXe-Bz112c-UbuQg{padding:0 12px 0 16px}.VfPpkd-LgbsSe-OWXEXe-MV7yeb.VfPpkd-LgbsSe-OWXEXe-Bz112c-M1Soyc{padding:0 16px 0 12px}.VfPpkd-LgbsSe-OWXEXe-INsAgc{border-style:solid;-webkit-transition:border .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1)}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-Jh9lGc{border-style:solid;border-color:transparent}.VfPpkd-LgbsSe{--mdc-ripple-fg-size:0;--mdc-ripple-left:0;--mdc-ripple-top:0;--mdc-ripple-fg-scale:1;--mdc-ripple-fg-translate-end:0;--mdc-ripple-fg-translate-start:0;-webkit-tap-highlight-color:rgba(0,0,0,0);will-change:transform,opacity}.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::after{position:absolute;border-radius:50%;opacity:0;pointer-events:none;content:""}.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::before{-webkit-transition:opacity 15ms linear,background-color 15ms linear;transition:opacity 15ms linear,background-color 15ms linear;z-index:1}.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::after{z-index:0}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Jh9lGc::before{-webkit-transform:scale(var(--mdc-ripple-fg-scale,1));-ms-transform:scale(var(--mdc-ripple-fg-scale,1));transform:scale(var(--mdc-ripple-fg-scale,1))}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Jh9lGc::after{top:0;left:0;-webkit-transform:scale(0);-ms-transform:scale(0);transform:scale(0);-webkit-transform-origin:center center;-ms-transform-origin:center center;transform-origin:center center}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd .VfPpkd-Jh9lGc::after{top:var(--mdc-ripple-top,0);left:var(--mdc-ripple-left,0)}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-Tv8l5d-lJfZMc .VfPpkd-Jh9lGc::after{-webkit-animation:mdc-ripple-fg-radius-in 225ms forwards,mdc-ripple-fg-opacity-in 75ms forwards;animation:mdc-ripple-fg-radius-in 225ms forwards,mdc-ripple-fg-opacity-in 75ms forwards}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-Tv8l5d-OmS1vf .VfPpkd-Jh9lGc::after{-webkit-animation:mdc-ripple-fg-opacity-out .15s;animation:mdc-ripple-fg-opacity-out .15s;-webkit-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));-ms-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1))}.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::after{top:-50%;left:-50%;width:200%;height:200%}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Jh9lGc::after{width:var(--mdc-ripple-fg-size,100%);height:var(--mdc-ripple-fg-size,100%)}.VfPpkd-Jh9lGc{position:absolute;-webkit-box-sizing:content-box;box-sizing:content-box;overflow:hidden;z-index:0;top:0;left:0;bottom:0;right:0}.VfPpkd-LgbsSe{font-family:Roboto,sans-serif;font-size:.875rem;letter-spacing:.0892857143em;font-weight:500;text-transform:uppercase;height:36px;border-radius:4px}.VfPpkd-LgbsSe:not(:disabled){color:#6200ee}.VfPpkd-LgbsSe:disabled{color:rgba(0,0,0,.38)}.VfPpkd-LgbsSe .VfPpkd-kBDsod{font-size:1.125rem;width:1.125rem;height:1.125rem}.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::before{background-color:#6200ee}.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::after{background-color:#6200ee}.VfPpkd-LgbsSe:hover .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:.04}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12}.VfPpkd-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.VfPpkd-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-text-button-pressed-state-layer-opacity,0.12)}.VfPpkd-LgbsSe .VfPpkd-Jh9lGc{border-radius:4px}.VfPpkd-LgbsSe .VfPpkd-J1Ukfc-LhBDec{border-radius:2px}.VfPpkd-LgbsSe .VfPpkd-J1Ukfc-LhBDec::after{border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-k8QpJ{font-family:Roboto,sans-serif;font-size:.875rem;letter-spacing:.0892857143em;font-weight:500;text-transform:uppercase;height:36px;border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-k8QpJ:not(:disabled){background-color:#6200ee}.VfPpkd-LgbsSe-OWXEXe-k8QpJ:disabled{background-color:rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-k8QpJ:not(:disabled){color:#fff}.VfPpkd-LgbsSe-OWXEXe-k8QpJ:disabled{color:rgba(0,0,0,.38)}.VfPpkd-LgbsSe-OWXEXe-k8QpJ .VfPpkd-kBDsod{font-size:1.125rem;width:1.125rem;height:1.125rem}.VfPpkd-LgbsSe-OWXEXe-k8QpJ .VfPpkd-Jh9lGc::before{background-color:#fff}.VfPpkd-LgbsSe-OWXEXe-k8QpJ .VfPpkd-Jh9lGc::after{background-color:#fff}.VfPpkd-LgbsSe-OWXEXe-k8QpJ:hover .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe-OWXEXe-k8QpJ.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:.08}.VfPpkd-LgbsSe-OWXEXe-k8QpJ.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe-OWXEXe-k8QpJ:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.24}.VfPpkd-LgbsSe-OWXEXe-k8QpJ:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.VfPpkd-LgbsSe-OWXEXe-k8QpJ:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.24}.VfPpkd-LgbsSe-OWXEXe-k8QpJ.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-filled-button-pressed-state-layer-opacity,0.24)}.VfPpkd-LgbsSe-OWXEXe-k8QpJ .VfPpkd-Jh9lGc{border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-k8QpJ .VfPpkd-J1Ukfc-LhBDec{border-radius:2px}.VfPpkd-LgbsSe-OWXEXe-k8QpJ .VfPpkd-J1Ukfc-LhBDec::after{border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-MV7yeb{font-family:Roboto,sans-serif;font-size:.875rem;letter-spacing:.0892857143em;font-weight:500;text-transform:uppercase;height:36px;border-radius:4px;-webkit-box-shadow:0 3px 1px -2px rgba(0,0,0,.2),0 2px 2px 0 rgba(0,0,0,.14),0 1px 5px 0 rgba(0,0,0,.12);box-shadow:0 3px 1px -2px rgba(0,0,0,.2),0 2px 2px 0 rgba(0,0,0,.14),0 1px 5px 0 rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:not(:disabled){background-color:#6200ee}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:disabled{background-color:rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:not(:disabled){color:#fff}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:disabled{color:rgba(0,0,0,.38)}.VfPpkd-LgbsSe-OWXEXe-MV7yeb .VfPpkd-kBDsod{font-size:1.125rem;width:1.125rem;height:1.125rem}.VfPpkd-LgbsSe-OWXEXe-MV7yeb .VfPpkd-Jh9lGc::before{background-color:#fff}.VfPpkd-LgbsSe-OWXEXe-MV7yeb .VfPpkd-Jh9lGc::after{background-color:#fff}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:hover .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe-OWXEXe-MV7yeb.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:.08}.VfPpkd-LgbsSe-OWXEXe-MV7yeb.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe-OWXEXe-MV7yeb:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.24}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.24}.VfPpkd-LgbsSe-OWXEXe-MV7yeb.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-protected-button-pressed-state-layer-opacity,0.24)}.VfPpkd-LgbsSe-OWXEXe-MV7yeb .VfPpkd-Jh9lGc{border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-MV7yeb .VfPpkd-J1Ukfc-LhBDec{border-radius:2px}.VfPpkd-LgbsSe-OWXEXe-MV7yeb .VfPpkd-J1Ukfc-LhBDec::after{border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-MV7yeb.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe,.VfPpkd-LgbsSe-OWXEXe-MV7yeb:not(.VfPpkd-ksKsZd-mWPk3d):focus{-webkit-box-shadow:0 2px 4px -1px rgba(0,0,0,.2),0 4px 5px 0 rgba(0,0,0,.14),0 1px 10px 0 rgba(0,0,0,.12);box-shadow:0 2px 4px -1px rgba(0,0,0,.2),0 4px 5px 0 rgba(0,0,0,.14),0 1px 10px 0 rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:hover{-webkit-box-shadow:0 2px 4px -1px rgba(0,0,0,.2),0 4px 5px 0 rgba(0,0,0,.14),0 1px 10px 0 rgba(0,0,0,.12);box-shadow:0 2px 4px -1px rgba(0,0,0,.2),0 4px 5px 0 rgba(0,0,0,.14),0 1px 10px 0 rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:not(:disabled):active{-webkit-box-shadow:0 5px 5px -3px rgba(0,0,0,.2),0 8px 10px 1px rgba(0,0,0,.14),0 3px 14px 2px rgba(0,0,0,.12);box-shadow:0 5px 5px -3px rgba(0,0,0,.2),0 8px 10px 1px rgba(0,0,0,.14),0 3px 14px 2px rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:disabled{-webkit-box-shadow:0 0 0 0 rgba(0,0,0,.2),0 0 0 0 rgba(0,0,0,.14),0 0 0 0 rgba(0,0,0,.12);box-shadow:0 0 0 0 rgba(0,0,0,.2),0 0 0 0 rgba(0,0,0,.14),0 0 0 0 rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-INsAgc{font-family:Roboto,sans-serif;font-size:.875rem;letter-spacing:.0892857143em;font-weight:500;text-transform:uppercase;height:36px;border-radius:4px;padding:0 15px 0 15px;border-width:1px}.VfPpkd-LgbsSe-OWXEXe-INsAgc:not(:disabled){color:#6200ee}.VfPpkd-LgbsSe-OWXEXe-INsAgc:disabled{color:rgba(0,0,0,.38)}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-kBDsod{font-size:1.125rem;width:1.125rem;height:1.125rem}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-Jh9lGc::before{background-color:#6200ee}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-Jh9lGc::after{background-color:#6200ee}.VfPpkd-LgbsSe-OWXEXe-INsAgc:hover .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe-OWXEXe-INsAgc.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:.04}.VfPpkd-LgbsSe-OWXEXe-INsAgc.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe-OWXEXe-INsAgc:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12}.VfPpkd-LgbsSe-OWXEXe-INsAgc:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.VfPpkd-LgbsSe-OWXEXe-INsAgc:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12}.VfPpkd-LgbsSe-OWXEXe-INsAgc.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-outlined-button-pressed-state-layer-opacity,0.12)}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-Jh9lGc{border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-J1Ukfc-LhBDec{border-radius:2px}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-J1Ukfc-LhBDec::after{border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-INsAgc:not(:disabled){border-color:rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-INsAgc:disabled{border-color:rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-INsAgc.VfPpkd-LgbsSe-OWXEXe-Bz112c-UbuQg{padding:0 11px 0 15px}.VfPpkd-LgbsSe-OWXEXe-INsAgc.VfPpkd-LgbsSe-OWXEXe-Bz112c-M1Soyc{padding:0 15px 0 11px}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-Jh9lGc{top:-1px;left:-1px;bottom:-1px;right:-1px;border-width:1px}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-RLmnJb{left:-1px;width:calc(100% + 2px)}.nCP5yc{font-family:"Google Sans",Roboto,Arial,sans-serif;font-size:.875rem;letter-spacing:.0107142857em;font-weight:500;text-transform:none;-webkit-transition:border .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),box-shadow .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);-webkit-box-shadow:none;box-shadow:none}.nCP5yc .VfPpkd-Jh9lGc{height:100%;position:absolute;overflow:hidden;width:100%;z-index:0}.nCP5yc:not(:disabled){background-color:rgb(26,115,232);background-color:var(--gm-fillbutton-container-color,rgb(26,115,232))}.nCP5yc:not(:disabled){color:#fff;color:var(--gm-fillbutton-ink-color,#fff)}.nCP5yc:disabled{background-color:rgba(60,64,67,.12);background-color:var(--gm-fillbutton-disabled-container-color,rgba(60,64,67,.12))}.nCP5yc:disabled{color:rgba(60,64,67,.38);color:var(--gm-fillbutton-disabled-ink-color,rgba(60,64,67,.38))}.nCP5yc .VfPpkd-Jh9lGc::before,.nCP5yc .VfPpkd-Jh9lGc::after{background-color:rgb(32,33,36);background-color:var(--gm-fillbutton-state-color,rgb(32,33,36))}.nCP5yc:hover .VfPpkd-Jh9lGc::before,.nCP5yc.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:.16;opacity:var(--mdc-ripple-hover-opacity,.16)}.nCP5yc.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.nCP5yc:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.24;opacity:var(--mdc-ripple-focus-opacity,.24)}.nCP5yc:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.nCP5yc:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.2;opacity:var(--mdc-ripple-press-opacity,.2)}.nCP5yc.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0.2)}.nCP5yc .VfPpkd-BFbNVe-bF1uUb{opacity:0}.nCP5yc .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-uI4vCe-LkdAo,.nCP5yc .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-IdXvz-LkdAo-Bd00G{stroke:#fff}@media (-ms-high-contrast:active),screen and (forced-colors:active){.nCP5yc .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-uI4vCe-LkdAo,.nCP5yc .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-IdXvz-LkdAo-Bd00G{stroke:CanvasText}}.nCP5yc:hover{-webkit-box-shadow:0 1px 2px 0 rgba(60,64,67,.3),0 1px 3px 1px rgba(60,64,67,.15);box-shadow:0 1px 2px 0 rgba(60,64,67,.3),0 1px 3px 1px rgba(60,64,67,.15);-webkit-box-shadow:0 1px 2px 0 var(--gm-fillbutton-keyshadow-color,rgba(60,64,67,.3)),0 1px 3px 1px var(--gm-fillbutton-ambientshadow-color,rgba(60,64,67,.15));box-shadow:0 1px 2px 0 var(--gm-fillbutton-keyshadow-color,rgba(60,64,67,.3)),0 1px 3px 1px var(--gm-fillbutton-ambientshadow-color,rgba(60,64,67,.15))}.nCP5yc:hover .VfPpkd-BFbNVe-bF1uUb{opacity:0}.nCP5yc:active{-webkit-box-shadow:0 1px 2px 0 rgba(60,64,67,.3),0 2px 6px 2px rgba(60,64,67,.15);box-shadow:0 1px 2px 0 rgba(60,64,67,.3),0 2px 6px 2px rgba(60,64,67,.15);-webkit-box-shadow:0 1px 2px 0 var(--gm-fillbutton-keyshadow-color,rgba(60,64,67,.3)),0 2px 6px 2px var(--gm-fillbutton-ambientshadow-color,rgba(60,64,67,.15));box-shadow:0 1px 2px 0 var(--gm-fillbutton-keyshadow-color,rgba(60,64,67,.3)),0 2px 6px 2px var(--gm-fillbutton-ambientshadow-color,rgba(60,64,67,.15))}.nCP5yc:active .VfPpkd-BFbNVe-bF1uUb{opacity:0}.nCP5yc:disabled{-webkit-box-shadow:none;box-shadow:none}.nCP5yc:disabled:hover .VfPpkd-Jh9lGc::before,.nCP5yc:disabled.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:0;opacity:var(--mdc-ripple-hover-opacity,0)}.nCP5yc:disabled.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.nCP5yc:disabled:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:0;opacity:var(--mdc-ripple-focus-opacity,0)}.nCP5yc:disabled:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.nCP5yc:disabled:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:0;opacity:var(--mdc-ripple-press-opacity,0)}.nCP5yc:disabled.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0)}.nCP5yc:disabled .VfPpkd-BFbNVe-bF1uUb{opacity:0}.Rj2Mlf{font-family:"Google Sans",Roboto,Arial,sans-serif;font-size:.875rem;letter-spacing:.0107142857em;font-weight:500;text-transform:none;-webkit-transition:border .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),box-shadow .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);-webkit-box-shadow:none;box-shadow:none}.Rj2Mlf .VfPpkd-Jh9lGc{height:100%;position:absolute;overflow:hidden;width:100%;z-index:0}.Rj2Mlf:not(:disabled){color:rgb(26,115,232);color:var(--gm-hairlinebutton-ink-color,rgb(26,115,232))}.Rj2Mlf:not(:disabled){border-color:rgb(218,220,224);border-color:var(--gm-hairlinebutton-outline-color,rgb(218,220,224))}.Rj2Mlf:not(:disabled):hover{border-color:rgb(218,220,224);border-color:var(--gm-hairlinebutton-outline-color,rgb(218,220,224))}.Rj2Mlf:not(:disabled).VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe,.Rj2Mlf:not(:disabled):not(.VfPpkd-ksKsZd-mWPk3d):focus{border-color:rgb(23,78,166);border-color:var(--gm-hairlinebutton-outline-color--stateful,rgb(23,78,166))}.Rj2Mlf:not(:disabled):active,.Rj2Mlf:not(:disabled):focus:active{border-color:rgb(218,220,224);border-color:var(--gm-hairlinebutton-outline-color,rgb(218,220,224))}.Rj2Mlf:disabled{color:rgba(60,64,67,.38);color:var(--gm-hairlinebutton-disabled-ink-color,rgba(60,64,67,.38))}.Rj2Mlf:disabled{border-color:rgba(60,64,67,.12);border-color:var(--gm-hairlinebutton-disabled-outline-color,rgba(60,64,67,.12))}.Rj2Mlf:hover:not(:disabled),.Rj2Mlf.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe:not(:disabled),.Rj2Mlf:not(.VfPpkd-ksKsZd-mWPk3d):focus:not(:disabled),.Rj2Mlf:active:not(:disabled){color:rgb(23,78,166);color:var(--gm-hairlinebutton-ink-color--stateful,rgb(23,78,166))}.Rj2Mlf .VfPpkd-BFbNVe-bF1uUb{opacity:0}.Rj2Mlf .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-uI4vCe-LkdAo,.Rj2Mlf .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-IdXvz-LkdAo-Bd00G{stroke:rgb(26,115,232)}@media (-ms-high-contrast:active),screen and (forced-colors:active){.Rj2Mlf .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-uI4vCe-LkdAo,.Rj2Mlf .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-IdXvz-LkdAo-Bd00G{stroke:CanvasText}}.Rj2Mlf .VfPpkd-Jh9lGc::before,.Rj2Mlf .VfPpkd-Jh9lGc::after{background-color:rgb(26,115,232);background-color:var(--gm-hairlinebutton-state-color,rgb(26,115,232))}.Rj2Mlf:hover .VfPpkd-Jh9lGc::before,.Rj2Mlf.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:.04;opacity:var(--mdc-ripple-hover-opacity,.04)}.Rj2Mlf.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.Rj2Mlf:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12;opacity:var(--mdc-ripple-focus-opacity,.12)}.Rj2Mlf:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.Rj2Mlf:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12;opacity:var(--mdc-ripple-press-opacity,.12)}.Rj2Mlf.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0.12)}.Rj2Mlf:disabled:hover .VfPpkd-Jh9lGc::before,.Rj2Mlf:disabled.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:0;opacity:var(--mdc-ripple-hover-opacity,0)}.Rj2Mlf:disabled.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.Rj2Mlf:disabled:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:0;opacity:var(--mdc-ripple-focus-opacity,0)}.Rj2Mlf:disabled:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.Rj2Mlf:disabled:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:0;opacity:var(--mdc-ripple-press-opacity,0)}.Rj2Mlf:disabled.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0)}.b9hyVd{font-family:"Google Sans",Roboto,Arial,sans-serif;font-size:.875rem;letter-spacing:.0107142857em;font-weight:500;text-transform:none;-webkit-transition:border .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),box-shadow .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);border-width:0;-webkit-box-shadow:0 1px 2px 0 rgba(60,64,67,.3),0 1px 3px 1px rgba(60,64,67,.15);box-shadow:0 1px 2px 0 rgba(60,64,67,.3),0 1px 3px 1px rgba(60,64,67,.15);-webkit-box-shadow:0 1px 2px 0 var(--gm-protectedbutton-keyshadow-color,rgba(60,64,67,.3)),0 1px 3px 1px var(--gm-protectedbutton-ambientshadow-color,rgba(60,64,67,.15));box-shadow:0 1px 2px 0 var(--gm-protectedbutton-keyshadow-color,rgba(60,64,67,.3)),0 1px 3px 1px var(--gm-protectedbutton-ambientshadow-color,rgba(60,64,67,.15))}.b9hyVd .VfPpkd-Jh9lGc{height:100%;position:absolute;overflow:hidden;width:100%;z-index:0}.b9hyVd:not(:disabled){background-color:#fff;background-color:var(--gm-protectedbutton-container-color,#fff)}.b9hyVd:not(:disabled){color:rgb(26,115,232);color:var(--gm-protectedbutton-ink-color,rgb(26,115,232))}.b9hyVd:disabled{background-color:rgba(60,64,67,.12);background-color:var(--gm-protectedbutton-disabled-container-color,rgba(60,64,67,.12))}.b9hyVd:disabled{color:rgba(60,64,67,.38);color:var(--gm-protectedbutton-disabled-ink-color,rgba(60,64,67,.38))}.b9hyVd:hover:not(:disabled),.b9hyVd.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe:not(:disabled),.b9hyVd:not(.VfPpkd-ksKsZd-mWPk3d):focus:not(:disabled),.b9hyVd:active:not(:disabled){color:rgb(23,78,166);color:var(--gm-protectedbutton-ink-color--stateful,rgb(23,78,166))}.b9hyVd .VfPpkd-BFbNVe-bF1uUb{opacity:0}.b9hyVd .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-uI4vCe-LkdAo,.b9hyVd .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-IdXvz-LkdAo-Bd00G{stroke:rgb(26,115,232)}@media (-ms-high-contrast:active),screen and (forced-colors:active){.b9hyVd .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-uI4vCe-LkdAo,.b9hyVd .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-IdXvz-LkdAo-B | 2026-01-13T09:30:12 |
https://developers.cloudflare.com/ai-gateway/usage/chat-completion/ | Unified API (OpenAI compat) · Cloudflare AI Gateway docs Skip to content Cloudflare Docs Search Docs Directory APIs SDKs Help Log in Select theme Dark Light Auto AI Gateway No results found. Try a different search term, or use our global search . Overview Getting started Using AI Gateway Unified API (OpenAI compat) Provider Native Workers AI Amazon Bedrock Anthropic Azure OpenAI Baseten Cartesia Cerebras Cohere Deepgram DeepSeek ElevenLabs Fal AI Google AI Studio Google Vertex AI Groq HuggingFace Ideogram Mistral AI OpenAI OpenRouter Parallel Perplexity Replicate xAI WebSockets API Beta Overview Realtime WebSockets API Non-realtime WebSockets API Features Overview Unified Billing Caching Rate limiting Dynamic routing Beta Overview Using a dynamic route JSON Configuration Data Loss Prevention (DLP) Beta Overview Set up Data Loss Prevention (DLP) Guardrails Beta Overview Set up Guardrails Supported model types Usage considerations Configuration BYOK (Store Keys) Beta Custom costs Custom Providers Beta Manage gateways Request handling Authenticated Gateway Observability Costs Custom metadata Analytics Logging Overview Workers Logpush Integrations Vercel AI SDK Agents ↗ AI Gateway Binding Methods Workers AI Tutorials Platform Overview Limits Pricing Audit logs Changelog Header Glossary REST API reference ↗ API MCP server ↗ MCP AI Assistant ↗ Architectures LLM resources llms.txt prompt.txt AI Gateway llms-full.txt Developer Platform llms-full.txt GitHub X.com YouTube Select theme Dark Light Auto On this page Overview Endpoint URL Parameters Examples Supported Providers On this page Overview Endpoint URL Parameters Examples Supported Providers Tags AI Was this helpful? Edit Issue Directory … AI Gateway Using AI Gateway Unified API (OpenAI compat) Copy page Unified API (OpenAI compat) Cloudflare's AI Gateway offers an OpenAI-compatible /chat/completions endpoint, enabling integration with multiple AI providers using a single URL. This feature simplifies the integration process, allowing for seamless switching between different models without significant code modifications. Endpoint URL https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions Replace {account_id} and {gateway_id} with your Cloudflare account and gateway IDs. Parameters Switch providers by changing the model and apiKey parameters. Specify the model using {provider}/{model} format. For example: openai/gpt-5-mini google-ai-studio/gemini-2.5-flash anthropic/claude-sonnet-4-5 Examples Make a request to OpenAI using OpenAI JS SDK with Stored Key (BYOK) import OpenAI from "openai" ; const client = new OpenAI ( { apiKey : "{cf_api_token}" , baseURL : "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat" , } ) ; const response = await client . chat . completions . create ( { model : "openai/gpt-5.2" , messages : [ { role : "user" , content : "Hello, world!" } ] , } ) ; import OpenAI from "openai" ; const client = new OpenAI ( { apiKey : "{cf_api_token}" , baseURL : "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat" , } ) ; const response = await client . chat . completions . create ( { model : "anthropic/claude-4-5-sonnet" , messages : [ { role : "user" , content : "Hello, world!" } ] , } ) ; import OpenAI from "openai" ; const client = new OpenAI ( { apiKey : "{cf_api_token}" , baseURL : "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat" , } ) ; const response = await client . chat . completions . create ( { model : "google/gemini-2.5-pro" , messages : [ { role : "user" , content : "Hello, world!" } ] , } ) ; import OpenAI from "openai" ; const client = new OpenAI ( { apiKey : "{cf_api_token}" , baseURL : "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat" , } ) ; const response = await client . chat . completions . create ( { model : "grok/grok-4" , messages : [ { role : "user" , content : "Hello, world!" } ] , } ) ; import OpenAI from "openai" ; const client = new OpenAI ( { apiKey : "{cf_api_token}" , baseURL : "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat" , } ) ; const response = await client . chat . completions . create ( { model : "dynamic/customer-support" , messages : [ { role : "user" , content : "Hello, world!" } ] , } ) ; import OpenAI from "openai" ; const client = new OpenAI ( { apiKey : "{cf_api_token}" , baseURL : "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat" , } ) ; const response = await client . chat . completions . create ( { model : "workers-ai/@cf/meta/llama-3.3-70b-instruct-fp8-fast" , messages : [ { role : "user" , content : "Hello, world!" } ] , } ) ; import OpenAI from "openai" ; const client = new OpenAI ( { apiKey : "{openai_api_token}" , defaultHeaders : { // if gateway is authenticated "cf-aig-authorization" : `Bearer {cf_api_token}` , }, baseURL : "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat" , } ) ; const response = await client . chat . completions . create ( { model : "openai/gpt-5.2" , messages : [ { role : "user" , content : "Hello, world!" } ] , } ) ; import OpenAI from "openai" ; const client = new OpenAI ( { apiKey : "{anthropic_api_token}" , defaultHeaders : { // if gateway is authenticated "cf-aig-authorization" : `Bearer {cf_api_token}` , }, baseURL : "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat" , } ) ; const response = await client . chat . completions . create ( { model : "anthropic/claude-4-5-sonnet" , messages : [ { role : "user" , content : "Hello, world!" } ] , } ) ; import OpenAI from "openai" ; const client = new OpenAI ( { apiKey : "{google_api_token}" , defaultHeaders : { // if gateway is authenticated "cf-aig-authorization" : `Bearer {cf_api_token}` , }, baseURL : "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat" , } ) ; const response = await client . chat . completions . create ( { model : "google/gemini-2.5-pro" , messages : [ { role : "user" , content : "Hello, world!" } ] , } ) ; import OpenAI from "openai" ; const client = new OpenAI ( { apiKey : "{grok_api_token}" , defaultHeaders : { // if gateway is authenticated "cf-aig-authorization" : `Bearer {cf_api_token}` , }, baseURL : "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat" , } ) ; const response = await client . chat . completions . create ( { model : "grok/grok-4" , messages : [ { role : "user" , content : "Hello, world!" } ] , } ) ; import OpenAI from "openai" ; const client = new OpenAI ( { apiKey : "{dynamic_api_token}" , defaultHeaders : { // if gateway is authenticated "cf-aig-authorization" : `Bearer {cf_api_token}` , }, baseURL : "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat" , } ) ; const response = await client . chat . completions . create ( { model : "dynamic/customer-support" , messages : [ { role : "user" , content : "Hello, world!" } ] , } ) ; import OpenAI from "openai" ; const client = new OpenAI ( { apiKey : "{workers-ai_api_token}" , defaultHeaders : { // if gateway is authenticated "cf-aig-authorization" : `Bearer {cf_api_token}` , }, baseURL : "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat" , } ) ; const response = await client . chat . completions . create ( { model : "workers-ai/@cf/meta/llama-3.3-70b-instruct-fp8-fast" , messages : [ { role : "user" , content : "Hello, world!" } ] , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified () ; const { text } = await generateText ( { model : aigateway ( unified ( 'openai/gpt-5.2' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified () ; const { text } = await generateText ( { model : aigateway ( unified ( 'anthropic/claude-4-5-sonnet' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified () ; const { text } = await generateText ( { model : aigateway ( unified ( 'google/gemini-2.5-pro' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified () ; const { text } = await generateText ( { model : aigateway ( unified ( 'grok/grok-4' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified () ; const { text } = await generateText ( { model : aigateway ( unified ( 'dynamic/customer-support' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified () ; const { text } = await generateText ( { model : aigateway ( unified ( 'workers-ai/@cf/meta/llama-3.3-70b-instruct-fp8-fast' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( unified ( 'openai/gpt-5.2' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( unified ( 'anthropic/claude-4-5-sonnet' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( unified ( 'google/gemini-2.5-pro' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( unified ( 'grok/grok-4' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( unified ( 'dynamic/customer-support' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( unified ( 'workers-ai/@cf/meta/llama-3.3-70b-instruct-fp8-fast' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createOpenAI } from 'ai-gateway-provider/providers/openai' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const openai = createOpenAI () ; const { text } = await generateText ( { model : aigateway ( openai . chat ( 'gpt-5.2' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createAnthropic } from 'ai-gateway-provider/providers/anthropic' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const anthropic = createAnthropic () ; const { text } = await generateText ( { model : aigateway ( anthropic ( 'claude-4-5-sonnet' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createGoogle } from 'ai-gateway-provider/providers/google' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const google = createGoogle () ; const { text } = await generateText ( { model : aigateway ( google ( 'gemini-2.5-pro' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createXai } from 'ai-gateway-provider/providers/xai' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const xai = createXai () ; const { text } = await generateText ( { model : aigateway ( xai ( 'grok-4' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified () ; const { text } = await generateText ( { model : aigateway ( unified ( 'customer-support' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified () ; const { text } = await generateText ( { model : aigateway ( unified ( '@cf/meta/llama-3.3-70b-instruct-fp8-fast' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createOpenAI } from 'ai-gateway-provider/providers/openai' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const openai = createOpenAI ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( openai . chat ( 'gpt-5.2' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createAnthropic } from 'ai-gateway-provider/providers/anthropic' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const anthropic = createAnthropic ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( anthropic ( 'claude-4-5-sonnet' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createGoogle } from 'ai-gateway-provider/providers/google' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const google = createGoogle ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( google ( 'gemini-2.5-pro' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createXai } from 'ai-gateway-provider/providers/xai' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const xai = createXai ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( xai ( 'grok-4' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( unified ( 'customer-support' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( unified ( '@cf/meta/llama-3.3-70b-instruct-fp8-fast' )) , prompt : 'What is Cloudflare?' , } ) ; curl -X POST https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions \ --header 'cf-aig-authorization: Bearer {CF_AIG_TOKEN}' \ --header 'Content-Type: application/json' \ --data '{ "model": "openai/gpt-5.2", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] }' curl -X POST https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions \ --header 'cf-aig-authorization: Bearer {CF_AIG_TOKEN}' \ --header 'Content-Type: application/json' \ --data '{ "model": "anthropic/claude-4-5-sonnet", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] }' curl -X POST https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions \ --header 'cf-aig-authorization: Bearer {CF_AIG_TOKEN}' \ --header 'Content-Type: application/json' \ --data '{ "model": "google/gemini-2.5-pro", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] }' curl -X POST https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions \ --header 'cf-aig-authorization: Bearer {CF_AIG_TOKEN}' \ --header 'Content-Type: application/json' \ --data '{ "model": "grok/grok-4", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] }' curl -X POST https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions \ --header 'cf-aig-authorization: Bearer {CF_AIG_TOKEN}' \ --header 'Content-Type: application/json' \ --data '{ "model": "dynamic/customer-support", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] }' curl -X POST https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions \ --header 'cf-aig-authorization: Bearer {CF_AIG_TOKEN}' \ --header 'Content-Type: application/json' \ --data '{ "model": "workers-ai/@cf/meta/llama-3.3-70b-instruct-fp8-fast", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] }' curl -X POST https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions \ --header 'cf-aig-authorization: Bearer {CF_AIG_TOKEN}' \ --header 'Authorization: Bearer {openai_api_token}' \ --header 'Content-Type: application/json' \ --data '{ "model": "openai/gpt-5.2", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] }' curl -X POST https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions \ --header 'cf-aig-authorization: Bearer {CF_AIG_TOKEN}' \ --header 'Authorization: Bearer {anthropic_api_token}' \ --header 'Content-Type: application/json' \ --data '{ "model": "anthropic/claude-4-5-sonnet", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] }' curl -X POST https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions \ --header 'cf-aig-authorization: Bearer {CF_AIG_TOKEN}' \ --header 'Authorization: Bearer {google_api_token}' \ --header 'Content-Type: application/json' \ --data '{ "model": "google/gemini-2.5-pro", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] }' curl -X POST https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions \ --header 'cf-aig-authorization: Bearer {CF_AIG_TOKEN}' \ --header 'Authorization: Bearer {grok_api_token}' \ --header 'Content-Type: application/json' \ --data '{ "model": "grok/grok-4", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] }' curl -X POST https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions \ --header 'cf-aig-authorization: Bearer {CF_AIG_TOKEN}' \ --header 'Authorization: Bearer {dynamic_api_token}' \ --header 'Content-Type: application/json' \ --data '{ "model": "dynamic/customer-support", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] }' curl -X POST https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions \ --header 'cf-aig-authorization: Bearer {CF_AIG_TOKEN}' \ --header 'Authorization: Bearer {workers-ai_api_token}' \ --header 'Content-Type: application/json' \ --data '{ "model": "workers-ai/@cf/meta/llama-3.3-70b-instruct-fp8-fast", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] }' Supported Providers The OpenAI-compatible endpoint supports models from the following providers: Anthropic OpenAI Groq Mistral Cohere Perplexity Workers AI Google-AI-Studio Google Vertex AI xAI DeepSeek Cerebras Baseten Parallel Was this helpful? Edit page Last updated: Jan 7, 2026 Previous Getting started Next Workers AI Resources API New to Cloudflare? Directory Sponsorships Open Source Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Speed Test Is BGP Safe Yet? RPKI Toolkit Certificate Transparency Community X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings | 2026-01-13T09:30:12 |
http://ads-developers.googleblog.com/2021/04/announcing-v2-of-adsense-management-api.html | Google Ads Developer Blog: Announcing v2 of the AdSense Management API Ads Developer Blog The official blog for information about the Google Ads, Google Ad Manager, Google Mobile Ads SDKs for AdMob and IMA SDKs, and other Google Advertising Platform developer tools. Announcing v2 of the AdSense Management API Monday, April 19, 2021 We're happy to announce that v2 of the AdSense Management API is available starting today. This version adds the ability to fetch the status of sites on your account and aligns the AdSense Management API with current Google API standards . At this time, v1.4 of the AdSense Management API is now deprecated, and it will sunset on October 12, 2021 . Notable changes from v1.4 to v2 include the following: All deprecated methods in v1.4 have been removed in v2. This includes resource methods that did not specify an AdSense account. Resources are now identified by a name field. For example, an AdClient’s name would be “ accounts/{accountId}/adclients/{adClientId} ”. With v2, AdSense Management API reporting data now aligns with the AdSense UI. This means that AdMob and YouTube properties are no longer supported. If you need to continue to fetch AdMob data programmatically, please migrate to the AdMob API . Additionally, the AdSense Management API will only support report data going back 3 years. For a full list of changes, see the release notes . As always, feel free to reach out to us on the AdSense API forum with any API-related questions. - Donovan McMurray , AdSense API Team Google Labels: adsense_api , release , sunset    Labels  account_management ad_clicks ad_customizers ad_exchange ad_exchange_buyer ad_exchange_optimization-series ad_exchange_rest ad_exchange_rtb ad_exchange_seller ad_exchange_soap ad_extensions ad_inspector ad_manager ad_manager_api ad_manager_api_v201805 ad_manager_api_v201808 ad_manager_api_v201811 ad_manager_api_v201902 ad_manager_api_v201905 ad_manager_api_v201908 ad_manager_api_v201911 ad_manager_api_v202002 ad_manager_api_v202005 ad_manager_api_v202008 ad_manager_api_v202011 ad_manager_api_v202102 ad_manager_api_v202105 ad_manager_api_v202108 ad_manager_api_v202111 ad_manager_api_v202202 ad_manager_api_v202205 ad_manager_api_v202208 ad_manager_api_v202211 ad_manager_api_v202302 ad_manager_api_v202305 ad_manager_api_v202308 ad_manager_api_v202311 ad_manager_api_v202402 ad_manager_api_v202405 ad_manager_api_v202408 ad_manager_api_v202411 ad_manager_api_v202502 ad_manager_api_v202511 ad_param ad_speed adexchangebuyer AdGroup AdGroupAd admanager_api admob admob_api admob_api_v1 admob_mediation admob_sdk admob_v4.3.1 admob_v5.0.5 admob_v6.0.1 ads adsense adsense_api adsense_host_api adsense_host_api_v3 adsense_management_api adsense_management_api_v1 adsense_management_api_v1.1 adsense_management_api_v1.2 adsense_management_api_v1.3 adsense_management_api_v1.4 advanced_apis adwhirl adwhirl_v3.1.1 adwords AdWords Scripts adwords_AdGroupCriterionService adwords_api adwords_api_v201302 adwords_api_v201306 adwords_api_v201309 adwords_api_v201402 adwords_api_v201406 adwords_api_v201409 adwords_api_v201502 adwords_api_v201506 adwords_api_v201509 adwords_api_v201601 adwords_api_v201603 adwords_api_v201605 adwords_api_v201607 adwords_api_v201609 adwords_api_v201702 adwords_api_v201705 adwords_api_v201708 adwords_api_v201710 adwords_api_v201802 adwords_api_v201806 adwords_api_v201809 adwords_api_workshops adwords_BatchJobService adwords_CampaignService adwords_CreateAccountService adwords_for_video adwords_ManagedCustomerService adwords_MutateJobService adwords_ReportDefinitionService adwords_scripts adwords_v201109 adwords_v201206 adwords_v201209 adwords_v201302 adwords_v201306 adwords_v201309 adwords_v201601 adwords_v201605 adwords_v201607 adwords_v201609 adwords_v201702 adwords_v201802 adwords_v201806 adwords_v201809 ai_tools alerting amp analytics analyticsapi android android_layout animation announcement annual developer survey api app_engine asset_group asset_group_listing_group_filter asset_group_signal assets attribution_reporting_api audiences authentication authorization authorized_buyer authorized_buyers aw_reporting awql batch_processing beacon_api best_practices beta bid_manager_api bid_modifiers bidding billing brand guidelines brand_guidelines budget_order_service budgets builders bulk_upload c# caf_sdk call_extensions call_metrics call_only call_tracking call-only callout_extensions campaign campaign_management campaign_manager_360 CampaignCriterion case_study cast certificates certification change_history chart_tools chrome chromecast click click_tracking click_type click-to-download clicks client_libraries client_library cm360 code_examples common_questions conference content content_api conversion conversions ConversionTrackerService converted_clicks creative_platforms creatives custom_fields customer_match DAI dart data_manager_api dbm_api debugging decorators deprecation developer dfa_ad_service dfa_api dfa_api_v118 dfa_creative_service dfa_reporting_api dfa_site_service dfa_v1.16 dfa_v1.17 dfa_v1.18 dfa_v1.19 dfa_v1.20 dfp dfp_api dfp_appengine dfp_creatives dfp_inventory dfp_mobile dfp_pql dfp_reports dfp_sales dfp_teams dfp_v201111 dfp_v201201 dfp_v201203 dfp_v201204 dfp_v201206 dfp_v201208 dfp_v201211 dfp_v201302 dfp_v201308 dfp_v201608 dfp_v201711 discord display display_network display_select display_smart_campaign docs documentation dotnet doubleclick DoubleClick_Rich_Media doubleclick_studio drafts dsa dv360 dv360_api dynamic_creative enhanced_campaigns entity_read_files erf error handling eta examples excluded_placement_lists exoplayer expanded_text_ads experiment experiments faq feedback feeds firebase flash flash_sdk floc flutter forecast_service games gaql gclid gdc gdl geo_targets geotargeting gmail_ads gmail_image_ads gmail_multi_product_ads gmail_single_promotion_ads GMF gmp golang google_ads google_ads_api google_ads_api_migration_workshop google_ads_api_v0 google_ads_api_v0_1 google_ads_api_v0_3 google_ads_api_v0_4 google_ads_api_v0_5 google_ads_api_v0_6 google_ads_api_v0_7 google_ads_api_v1_0 google_ads_api_v1_1 google_ads_api_v1_2 google_ads_api_v1_3 google_ads_api_v2_1 google_ads_api_v3_0 google_ads_api_v3_1 google_ads_api_v4 google_ads_api_v5 google_ads_api_v6 google_ads_scripts google_ads_solutions google_apis google_apps_script google_drive google_play_services google_plus gpt gRPC guide guides hangout hotel_ads hotel_campaigns html5 html5_ads https i18n ids ima_android ima_flash ima_html5 ima_ios ima_roku ima_sdk image image_ads image_optimization implementation impression_share interstitial interview io13 iOS iOS9 java_app_engine java_dart_api jdbc keyword_optimizer keywords kotlin labels limits line_item linq listing_groups location_extensions location_feeds LocationExtensionOperand LocationGroups logging manager_accounts maps_api marketplace maximize mcc MCP media media_bundle mediation_test_suite merchant_api migration mobile mobile_ads mobile_ads_garage mobile_ads_sdk mobile_sites mobile_speed mobile_targeting mobile_ux monitoring native native_ads_express new_features oath2 oauth oauth2 offline_conversions OfflineConversionFeedService open_source openrtb optimization pal Performance Max performance_max performance_max_api_workshop php PLA placements PMax policy policy_violation PQL price_extension privacy privacy_sandbox product_listing_ads proguard promotion_line publisher_ads_audits python qa quality_score query_builder_blog_series query_language quota rate_limiter rate_sheet RateExceededError realtime_bidding realtime_bidding_api realtime_bidding_protocol realtimebidding recommendations referer release remarketing reporting reports responsive_ads rest rewarded_video rmf ruby sa360 sandbox scripts sdf sdkless search search audience search terms search_audience search_network search_theme selector sendbeacon service_accounts SGAI shared_negative_keywords shopping simulations sitelinks smart snds spend ssl StepInsideAdWords success_stories suggested_ad_units sunset survey swift swift_package_manager swiftui target target_cpa targeting template_ads terms test_accounts test_network testing text_ads text_asset_automation tools trials turtledove ui unity update updates upgrade upgraded_urls v201509 vast3 vcpm video viewable-cpm webinar workshop workshops wp8 xml youtube  Archive      2026 Jan     2025 Dec Nov Oct Sep Aug Jul Jun May Apr Mar Feb Jan     2024 Dec Nov Oct Sep Aug Jul Jun May Apr Mar Feb Jan     2023 Dec Nov Oct Sep Aug Jul Jun May Apr Mar Feb Jan     2022 Dec Nov Oct Sep Aug Jul Jun May Apr Mar Feb Jan     2021 Dec Nov Oct Sep Aug Jul Jun May Apr Mar Feb Jan     2020 Dec Nov Oct Sep Aug Jul Jun May Apr Mar Feb Jan     2019 Dec Nov Oct Sep Aug Jul Jun May Apr Mar Feb Jan     2018 Dec Nov Oct Sep Aug Jul Jun May Apr Mar Feb Jan     2017 Dec Nov Oct Sep Aug Jul Jun May Apr Mar Feb Jan     2016 Dec Nov Oct Sep Aug Jul Jun May Apr Mar Feb Jan     2015 Dec Nov Oct Sep Aug Jul Jun May Apr Mar Feb Jan     2014 Dec Nov Oct Sep Aug Jul Jun May Apr Mar Feb Jan     2013 Dec Nov Oct Sep Aug Jul Jun May Apr Mar Feb Jan     2012 Dec Nov Oct Sep Aug Jul Jun May Apr Mar Feb Jan     2011 Dec Nov Give us feedback in our developer product forums: Google Ads API Google Ads scripts Google Ad Manager API DCM API Google Mobile Ads SDK Google AdMob API Google Interactive Media Ads SDK Google Content API for Shopping Authorized Buyers API Google Privacy Terms | 2026-01-13T09:30:12 |
https://docs.google.com/document/d/1kp3Crgi_iFavDn0YlAwlWo7U2M7oGfCrAOeDDsul1vA/copy | :root{--gm3-sys-color-on-surface-rgb:31,31,31}@media screen and (prefers-color-scheme:dark){:root{--gm3-sys-color-on-surface-rgb:227,227,227}}:root{--wf-harmonize-filter-light:none;--wf-harmonize-filter-dark:none}.q4Wquf,.nfoC7c{display:block;height:25vh;position:relative}@media (min-width:600px){.q4Wquf,.nfoC7c{height:150px}}.q4Wquf.Irjbwb{height:auto}@media screen and (prefers-color-scheme:dark){.q4Wquf:not(.GtvzYd){display:none}}.nfoC7c{margin:0;overflow:hidden}.PwpMUe,.lVUmD{display:block;height:100%;margin:0 auto;width:100%}.St9mde{display:block;-webkit-filter:var(--wf-harmonize-filter-light);filter:var(--wf-harmonize-filter-light);height:100%;max-width:100%;min-height:110px;position:relative;-webkit-transform:translate(-43%,-3%);-ms-transform:translate(-43%,-3%);transform:translate(-43%,-3%);width:auto;z-index:3}@media screen and (prefers-color-scheme:dark){.St9mde{-webkit-filter:var(--wf-harmonize-filter-dark);filter:var(--wf-harmonize-filter-dark)}}.PwpMUe,.lVUmD,.St9mde{-o-object-fit:contain;object-fit:contain}.wsArZ[data-ss-mode="1"] .q4Wquf,.wsArZ[data-ss-mode="1"] .St9mde{height:auto;width:100%}.wsArZ[data-ss-mode="1"] .St9mde{max-width:400px}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .q4Wquf,.NQ5OL .St9mde{height:auto;width:100%}.NQ5OL .St9mde{max-width:400px}}.q4Wquf.NWba7e,.q4Wquf.NWba7e .St9mde{height:auto}.q4Wquf.NWba7e .St9mde{height:auto;max-width:312px;width:100%}.q4Wquf.NWba7e.zpCp3 .St9mde{max-width:unset}.q4Wquf.IiQozc .St9mde{margin:0 auto;-webkit-transform:none;-ms-transform:none;transform:none}.q4Wquf.Irjbwb .St9mde{height:auto;width:100%}.q4Wquf.EEeaqf .St9mde{max-height:144px;max-width:144px}.SnAaEd{background-image:-webkit-gradient(linear,left top,left bottom,from(rgba(233,233,233,0)),color-stop(62.22%,rgba(233,233,233,0)),color-stop(40.22%,rgb(233,233,233)),to(rgba(233,233,233,0)));background-image:-webkit-linear-gradient(top,rgba(233,233,233,0) 0,rgba(233,233,233,0) 62.22%,rgb(233,233,233) 40.22%,rgba(233,233,233,0) 100%);background-image:linear-gradient(to bottom,rgba(233,233,233,0) 0,rgba(233,233,233,0) 62.22%,rgb(233,233,233) 40.22%,rgba(233,233,233,0) 100%);height:100%;left:0;overflow:hidden;position:absolute;right:0;top:0;z-index:2}@media screen and (prefers-color-scheme:dark){.SnAaEd{display:none}}.SnAaEd::after,.SnAaEd::before{content:"";display:block;height:100%;min-width:110px;position:absolute;right:-10%;-webkit-transform:rotate(-104deg);-ms-transform:rotate(-104deg);transform:rotate(-104deg);width:25vh;z-index:2}@media (min-width:600px){.SnAaEd::after,.SnAaEd::before{width:150px}}.SnAaEd::before{background-image:-webkit-gradient(linear,left top,left bottom,from(rgba(243,243,243,0)),to(rgba(243,243,243,.9)));background-image:-webkit-linear-gradient(top,rgba(243,243,243,0) 0,rgba(243,243,243,.9) 100%);background-image:linear-gradient(to bottom,rgba(243,243,243,0) 0,rgba(243,243,243,.9) 100%);bottom:-10%}.SnAaEd::after{background-image:-webkit-gradient(linear,left top,left bottom,from(rgba(255,255,255,0)),to(rgba(255,255,255,.9)));background-image:-webkit-linear-gradient(top,rgba(255,255,255,0) 0,rgba(255,255,255,.9) 100%);background-image:linear-gradient(to bottom,rgba(255,255,255,0) 0,rgba(255,255,255,.9) 100%);bottom:-80%}.wsArZ[data-ss-mode="1"] .SnAaEd~.St9mde{width:auto}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .SnAaEd~.St9mde{width:auto}}.RHNWk .St9mde{height:auto}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .RHNWk .St9mde{width:115px}}.cf660d .St9mde{-webkit-transform:translate(-9%,-3%);-ms-transform:translate(-9%,-3%);transform:translate(-9%,-3%)}.tUhwwc .St9mde{margin:auto;max-height:230px;right:0;top:-3%;-webkit-transform:none;-ms-transform:none;transform:none}.Jkvqxd .St9mde{-webkit-transform:translate(9%,-3%);-ms-transform:translate(9%,-3%);transform:translate(9%,-3%)}.onc8Ic .St9mde{-webkit-transform:translate(var( --c-ps-s,24px ),0);-ms-transform:translate(var( --c-ps-s,24px ),0);transform:translate(var( --c-ps-s,24px ),0)}.WA89Yb .St9mde{-webkit-transform:translate(0,0);-ms-transform:translate(0,0);transform:translate(0,0)}.wsArZ[data-ss-mode="1"] .XEN8Yb .St9mde{max-width:115px}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .XEN8Yb .St9mde{max-width:115px}}@media (min-width:1240px) and (orientation:landscape),all and (min-width:1600px){.KyPKed .NQ5OL .XEN8Yb .St9mde{max-width:115px}}.IsSr6b .St9mde{max-width:300px}.mmskdd .St9mde{-webkit-transform:none;-ms-transform:none;transform:none}@-webkit-keyframes quantumWizBoxInkSpread{0%{-webkit-transform:translate(-50%,-50%) scale(.2);transform:translate(-50%,-50%) scale(.2)}100%{-webkit-transform:translate(-50%,-50%) scale(2.2);transform:translate(-50%,-50%) scale(2.2)}}@keyframes quantumWizBoxInkSpread{0%{-webkit-transform:translate(-50%,-50%) scale(.2);transform:translate(-50%,-50%) scale(.2)}100%{-webkit-transform:translate(-50%,-50%) scale(2.2);transform:translate(-50%,-50%) scale(2.2)}}@-webkit-keyframes quantumWizIconFocusPulse{0%{-webkit-transform:translate(-50%,-50%) scale(1.5);transform:translate(-50%,-50%) scale(1.5);opacity:0}100%{-webkit-transform:translate(-50%,-50%) scale(2);transform:translate(-50%,-50%) scale(2);opacity:1}}@keyframes quantumWizIconFocusPulse{0%{-webkit-transform:translate(-50%,-50%) scale(1.5);transform:translate(-50%,-50%) scale(1.5);opacity:0}100%{-webkit-transform:translate(-50%,-50%) scale(2);transform:translate(-50%,-50%) scale(2);opacity:1}}@-webkit-keyframes quantumWizRadialInkSpread{0%{-webkit-transform:scale(1.5);transform:scale(1.5);opacity:0}100%{-webkit-transform:scale(2.5);transform:scale(2.5);opacity:1}}@keyframes quantumWizRadialInkSpread{0%{-webkit-transform:scale(1.5);transform:scale(1.5);opacity:0}100%{-webkit-transform:scale(2.5);transform:scale(2.5);opacity:1}}@-webkit-keyframes quantumWizRadialInkFocusPulse{0%{-webkit-transform:scale(2);transform:scale(2);opacity:0}100%{-webkit-transform:scale(2.5);transform:scale(2.5);opacity:1}}@keyframes quantumWizRadialInkFocusPulse{0%{-webkit-transform:scale(2);transform:scale(2);opacity:0}100%{-webkit-transform:scale(2.5);transform:scale(2.5);opacity:1}}:root{--wf-tfs:calc(var(--c-tfs,32)/16*1rem);--wf-tfs-bp2:calc(var(--c-tfs,36)/16*1rem);--wf-tfs-bp3:calc(var(--c-tfs,36)/16*1rem);--wf-tfs-bp5:calc(var(--c-tfs,44)/16*1rem);--wf-stfs:calc(var(--c-stfs,16)/16*1rem);--wf-stfs-bp5:calc(var(--c-stfs,16)/16*1rem)}:root{--wf-harmonize-filter-light:none;--wf-harmonize-filter-dark:none}.Dzz9Db,.GpMPBe{display:block;height:25vh;position:relative}@media (min-width:600px){.Dzz9Db,.GpMPBe{height:150px}}@media screen and (prefers-color-scheme:dark){.Dzz9Db:not(.GtvzYd){display:none}}.Dzz9Db.Irjbwb{height:auto}.GpMPBe{margin:0;overflow:hidden}.UFQPDd,.JNOvdd{display:block;height:100%;margin:0 auto;-o-object-fit:contain;object-fit:contain;width:100%}.f4ZpM{display:block;-webkit-filter:var(--wf-harmonize-filter-light);filter:var(--wf-harmonize-filter-light);height:100%;max-width:100%;min-height:110px;position:relative;-webkit-transform:translate(-43%,-3%);-ms-transform:translate(-43%,-3%);transform:translate(-43%,-3%);width:auto;z-index:3}@media screen and (prefers-color-scheme:dark){.f4ZpM{-webkit-filter:var(--wf-harmonize-filter-dark);filter:var(--wf-harmonize-filter-dark)}}.wsArZ[data-ss-mode="1"] .Dzz9Db,.wsArZ[data-ss-mode="1"] .f4ZpM{height:auto;width:100%}.wsArZ[data-ss-mode="1"] .f4ZpM{max-width:400px}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .Dzz9Db,.NQ5OL .f4ZpM{height:auto;width:100%}.NQ5OL .f4ZpM{max-width:400px}}.Dzz9Db.utFBGf,.Dzz9Db.utFBGf .f4ZpM{height:auto}.Dzz9Db.utFBGf .f4ZpM{height:auto;max-width:312px;width:100%}.Dzz9Db.utFBGf.zpCp3 .f4ZpM{max-width:unset}.Dzz9Db.IiQozc .f4ZpM{margin:0 auto;-webkit-transform:none;-ms-transform:none;transform:none}.Dzz9Db.Irjbwb .f4ZpM{height:auto;width:100%}.Dzz9Db.EEeaqf .f4ZpM{max-height:144px;max-width:144px}.nPt1pc{background-image:-webkit-gradient(linear,left top,left bottom,from(rgba(233,233,233,0)),color-stop(62.22%,rgba(233,233,233,0)),color-stop(40.22%,rgb(233,233,233)),to(rgba(233,233,233,0)));background-image:-webkit-linear-gradient(top,rgba(233,233,233,0) 0,rgba(233,233,233,0) 62.22%,rgb(233,233,233) 40.22%,rgba(233,233,233,0) 100%);background-image:linear-gradient(to bottom,rgba(233,233,233,0) 0,rgba(233,233,233,0) 62.22%,rgb(233,233,233) 40.22%,rgba(233,233,233,0) 100%);height:100%;left:0;overflow:hidden;position:absolute;right:0;top:0;z-index:2}@media screen and (prefers-color-scheme:dark){.nPt1pc{display:none}}.nPt1pc::after,.nPt1pc::before{content:"";display:block;height:100%;min-width:110px;position:absolute;right:-10%;-webkit-transform:rotate(-104deg);-ms-transform:rotate(-104deg);transform:rotate(-104deg);width:25vh;z-index:2}@media (min-width:600px){.nPt1pc::after,.nPt1pc::before{width:150px}}.nPt1pc::before{background-image:-webkit-gradient(linear,left top,left bottom,from(rgba(243,243,243,0)),to(rgba(243,243,243,.9)));background-image:-webkit-linear-gradient(top,rgba(243,243,243,0) 0,rgba(243,243,243,.9) 100%);background-image:linear-gradient(to bottom,rgba(243,243,243,0) 0,rgba(243,243,243,.9) 100%);bottom:-10%}.nPt1pc::after{background-image:-webkit-gradient(linear,left top,left bottom,from(rgba(255,255,255,0)),to(rgba(255,255,255,.9)));background-image:-webkit-linear-gradient(top,rgba(255,255,255,0) 0,rgba(255,255,255,.9) 100%);background-image:linear-gradient(to bottom,rgba(255,255,255,0) 0,rgba(255,255,255,.9) 100%);bottom:-80%}.wsArZ[data-ss-mode="1"] .nPt1pc~.f4ZpM{width:auto}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .nPt1pc~.f4ZpM{width:auto}}.ZS7CGc .f4ZpM{height:auto}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .ZS7CGc .f4ZpM{width:115px}}.qiRZ5e .f4ZpM{-webkit-transform:translate(-9%,-3%);-ms-transform:translate(-9%,-3%);transform:translate(-9%,-3%)}.vIv7Gf .f4ZpM{margin:auto;max-height:230px;right:0;top:-3%;-webkit-transform:none;-ms-transform:none;transform:none}.nvYXVd .f4ZpM{-webkit-transform:translate(9%,-3%);-ms-transform:translate(9%,-3%);transform:translate(9%,-3%)}.uOhnzd .f4ZpM{-webkit-transform:translate(24px,0);-ms-transform:translate(24px,0);transform:translate(24px,0)}.MsYMaf .f4ZpM{-webkit-transform:translate(0,0);-ms-transform:translate(0,0);transform:translate(0,0)}.wsArZ[data-ss-mode="1"] .YIi9qf .f4ZpM{max-width:115px}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .YIi9qf .f4ZpM{max-width:115px}}.QG3Xbe .f4ZpM{max-width:300px}.F6gtje .f4ZpM{-webkit-transform:none;-ms-transform:none;transform:none}@-webkit-keyframes mdc-ripple-fg-radius-in{from{-webkit-animation-timing-function:cubic-bezier(.4,0,.2,1);animation-timing-function:cubic-bezier(.4,0,.2,1);-webkit-transform:translate(var(--mdc-ripple-fg-translate-start,0)) scale(1);transform:translate(var(--mdc-ripple-fg-translate-start,0)) scale(1)}to{-webkit-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1))}}@keyframes mdc-ripple-fg-radius-in{from{-webkit-animation-timing-function:cubic-bezier(.4,0,.2,1);animation-timing-function:cubic-bezier(.4,0,.2,1);-webkit-transform:translate(var(--mdc-ripple-fg-translate-start,0)) scale(1);transform:translate(var(--mdc-ripple-fg-translate-start,0)) scale(1)}to{-webkit-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1))}}@-webkit-keyframes mdc-ripple-fg-opacity-in{from{-webkit-animation-timing-function:linear;animation-timing-function:linear;opacity:0}to{opacity:var(--mdc-ripple-fg-opacity,0)}}@keyframes mdc-ripple-fg-opacity-in{from{-webkit-animation-timing-function:linear;animation-timing-function:linear;opacity:0}to{opacity:var(--mdc-ripple-fg-opacity,0)}}@-webkit-keyframes mdc-ripple-fg-opacity-out{from{-webkit-animation-timing-function:linear;animation-timing-function:linear;opacity:var(--mdc-ripple-fg-opacity,0)}to{opacity:0}}@keyframes mdc-ripple-fg-opacity-out{from{-webkit-animation-timing-function:linear;animation-timing-function:linear;opacity:var(--mdc-ripple-fg-opacity,0)}to{opacity:0}}.VfPpkd-ksKsZd-XxIAqe{--mdc-ripple-fg-size:0;--mdc-ripple-left:0;--mdc-ripple-top:0;--mdc-ripple-fg-scale:1;--mdc-ripple-fg-translate-end:0;--mdc-ripple-fg-translate-start:0;-webkit-tap-highlight-color:rgba(0,0,0,0);will-change:transform,opacity;position:relative;outline:none;overflow:hidden}.VfPpkd-ksKsZd-XxIAqe::before,.VfPpkd-ksKsZd-XxIAqe::after{position:absolute;border-radius:50%;opacity:0;pointer-events:none;content:""}.VfPpkd-ksKsZd-XxIAqe::before{-webkit-transition:opacity 15ms linear,background-color 15ms linear;transition:opacity 15ms linear,background-color 15ms linear;z-index:1;z-index:var(--mdc-ripple-z-index,1)}.VfPpkd-ksKsZd-XxIAqe::after{z-index:0;z-index:var(--mdc-ripple-z-index,0)}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d::before{-webkit-transform:scale(var(--mdc-ripple-fg-scale,1));-ms-transform:scale(var(--mdc-ripple-fg-scale,1));transform:scale(var(--mdc-ripple-fg-scale,1))}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d::after{top:0;left:0;-webkit-transform:scale(0);-ms-transform:scale(0);transform:scale(0);-webkit-transform-origin:center center;-ms-transform-origin:center center;transform-origin:center center}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd::after{top:var(--mdc-ripple-top,0);left:var(--mdc-ripple-left,0)}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-Tv8l5d-lJfZMc::after{-webkit-animation:mdc-ripple-fg-radius-in 225ms forwards,mdc-ripple-fg-opacity-in 75ms forwards;animation:mdc-ripple-fg-radius-in 225ms forwards,mdc-ripple-fg-opacity-in 75ms forwards}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-Tv8l5d-OmS1vf::after{-webkit-animation:mdc-ripple-fg-opacity-out .15s;animation:mdc-ripple-fg-opacity-out .15s;-webkit-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));-ms-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1))}.VfPpkd-ksKsZd-XxIAqe::before,.VfPpkd-ksKsZd-XxIAqe::after{top:-50%;left:-50%;width:200%;height:200%}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d::after{width:var(--mdc-ripple-fg-size,100%);height:var(--mdc-ripple-fg-size,100%)}.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded],.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd{overflow:visible}.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded]::before,.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded]::after,.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd::before,.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd::after{top:0;left:0;width:100%;height:100%}.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded].VfPpkd-ksKsZd-mWPk3d::before,.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded].VfPpkd-ksKsZd-mWPk3d::after,.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd.VfPpkd-ksKsZd-mWPk3d::before,.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd.VfPpkd-ksKsZd-mWPk3d::after{top:var(--mdc-ripple-top,0);left:var(--mdc-ripple-left,0);width:var(--mdc-ripple-fg-size,100%);height:var(--mdc-ripple-fg-size,100%)}.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded].VfPpkd-ksKsZd-mWPk3d::after,.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd.VfPpkd-ksKsZd-mWPk3d::after{width:var(--mdc-ripple-fg-size,100%);height:var(--mdc-ripple-fg-size,100%)}.VfPpkd-ksKsZd-XxIAqe::before,.VfPpkd-ksKsZd-XxIAqe::after{background-color:#000;background-color:var(--mdc-ripple-color,#000)}.VfPpkd-ksKsZd-XxIAqe:hover::before,.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE::before{opacity:.04;opacity:var(--mdc-ripple-hover-opacity,.04)}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe::before,.VfPpkd-ksKsZd-XxIAqe:not(.VfPpkd-ksKsZd-mWPk3d):focus::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12;opacity:var(--mdc-ripple-focus-opacity,.12)}.VfPpkd-ksKsZd-XxIAqe:not(.VfPpkd-ksKsZd-mWPk3d)::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.VfPpkd-ksKsZd-XxIAqe:not(.VfPpkd-ksKsZd-mWPk3d):active::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12;opacity:var(--mdc-ripple-press-opacity,.12)}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0.12)}.VfPpkd-Bz112c-LgbsSe{font-size:24px;width:48px;height:48px;padding:12px}.VfPpkd-Bz112c-LgbsSe.VfPpkd-Bz112c-LgbsSe-OWXEXe-e5LLRc-SxQuSe .VfPpkd-Bz112c-Jh9lGc{width:40px;height:40px;margin-top:4px;margin-bottom:4px;margin-right:4px;margin-left:4px}.VfPpkd-Bz112c-LgbsSe.VfPpkd-Bz112c-LgbsSe-OWXEXe-e5LLRc-SxQuSe .VfPpkd-Bz112c-J1Ukfc-LhBDec{max-height:40px;max-width:40px}.VfPpkd-Bz112c-LgbsSe:disabled{color:rgba(0,0,0,.38);color:var(--mdc-theme-text-disabled-on-light,rgba(0,0,0,.38))}.VfPpkd-Bz112c-LgbsSe svg,.VfPpkd-Bz112c-LgbsSe img{width:24px;height:24px}.VfPpkd-Bz112c-LgbsSe{display:inline-block;position:relative;-webkit-box-sizing:border-box;box-sizing:border-box;border:none;outline:none;background-color:transparent;fill:currentColor;color:inherit;text-decoration:none;cursor:pointer;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none;z-index:0;overflow:visible}.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-RLmnJb{position:absolute;top:50%;height:48px;left:50%;width:48px;-webkit-transform:translate(-50%,-50%);-ms-transform:translate(-50%,-50%);transform:translate(-50%,-50%)}@media screen and (forced-colors:active){.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Bz112c-J1Ukfc-LhBDec,.VfPpkd-Bz112c-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Bz112c-J1Ukfc-LhBDec{display:block}}.VfPpkd-Bz112c-LgbsSe:disabled{cursor:default;pointer-events:none}.VfPpkd-Bz112c-LgbsSe[hidden]{display:none}.VfPpkd-Bz112c-LgbsSe-OWXEXe-KVuj8d-Q3DXx{-webkit-box-align:center;-webkit-align-items:center;align-items:center;display:-webkit-inline-box;display:-webkit-inline-flex;display:inline-flex;-webkit-box-pack:center;-webkit-justify-content:center;justify-content:center}.VfPpkd-Bz112c-J1Ukfc-LhBDec{pointer-events:none;border:2px solid transparent;border-radius:6px;-webkit-box-sizing:content-box;box-sizing:content-box;position:absolute;top:50%;left:50%;-webkit-transform:translate(-50%,-50%);-ms-transform:translate(-50%,-50%);transform:translate(-50%,-50%);height:100%;width:100%;display:none}@media screen and (forced-colors:active){.VfPpkd-Bz112c-J1Ukfc-LhBDec{border-color:CanvasText}}.VfPpkd-Bz112c-J1Ukfc-LhBDec::after{content:"";border:2px solid transparent;border-radius:8px;display:block;position:absolute;top:50%;left:50%;-webkit-transform:translate(-50%,-50%);-ms-transform:translate(-50%,-50%);transform:translate(-50%,-50%);height:calc(100% + 4px);width:calc(100% + 4px)}@media screen and (forced-colors:active){.VfPpkd-Bz112c-J1Ukfc-LhBDec::after{border-color:CanvasText}}.VfPpkd-Bz112c-kBDsod{display:inline-block}.VfPpkd-Bz112c-kBDsod.VfPpkd-Bz112c-kBDsod-OWXEXe-IT5dJd,.VfPpkd-Bz112c-LgbsSe-OWXEXe-IT5dJd .VfPpkd-Bz112c-kBDsod{display:none}.VfPpkd-Bz112c-LgbsSe-OWXEXe-IT5dJd .VfPpkd-Bz112c-kBDsod.VfPpkd-Bz112c-kBDsod-OWXEXe-IT5dJd{display:inline-block}.VfPpkd-Bz112c-mRLv6{height:100%;left:0;outline:none;position:absolute;top:0;width:100%}.VfPpkd-Bz112c-LgbsSe{--mdc-ripple-fg-size:0;--mdc-ripple-left:0;--mdc-ripple-top:0;--mdc-ripple-fg-scale:1;--mdc-ripple-fg-translate-end:0;--mdc-ripple-fg-translate-start:0;-webkit-tap-highlight-color:rgba(0,0,0,0);will-change:transform,opacity}.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::after{position:absolute;border-radius:50%;opacity:0;pointer-events:none;content:""}.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::before{-webkit-transition:opacity 15ms linear,background-color 15ms linear;transition:opacity 15ms linear,background-color 15ms linear;z-index:1;z-index:var(--mdc-ripple-z-index,1)}.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::after{z-index:0;z-index:var(--mdc-ripple-z-index,0)}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Bz112c-Jh9lGc::before{-webkit-transform:scale(var(--mdc-ripple-fg-scale,1));-ms-transform:scale(var(--mdc-ripple-fg-scale,1));transform:scale(var(--mdc-ripple-fg-scale,1))}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Bz112c-Jh9lGc::after{top:0;left:0;-webkit-transform:scale(0);-ms-transform:scale(0);transform:scale(0);-webkit-transform-origin:center center;-ms-transform-origin:center center;transform-origin:center center}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd .VfPpkd-Bz112c-Jh9lGc::after{top:var(--mdc-ripple-top,0);left:var(--mdc-ripple-left,0)}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-Tv8l5d-lJfZMc .VfPpkd-Bz112c-Jh9lGc::after{-webkit-animation:mdc-ripple-fg-radius-in 225ms forwards,mdc-ripple-fg-opacity-in 75ms forwards;animation:mdc-ripple-fg-radius-in 225ms forwards,mdc-ripple-fg-opacity-in 75ms forwards}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-Tv8l5d-OmS1vf .VfPpkd-Bz112c-Jh9lGc::after{-webkit-animation:mdc-ripple-fg-opacity-out .15s;animation:mdc-ripple-fg-opacity-out .15s;-webkit-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));-ms-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1))}.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::after{top:0;left:0;width:100%;height:100%}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Bz112c-Jh9lGc::after{top:var(--mdc-ripple-top,0);left:var(--mdc-ripple-left,0);width:var(--mdc-ripple-fg-size,100%);height:var(--mdc-ripple-fg-size,100%)}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Bz112c-Jh9lGc::after{width:var(--mdc-ripple-fg-size,100%);height:var(--mdc-ripple-fg-size,100%)}.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::after{background-color:#000;background-color:var(--mdc-ripple-color,#000)}.VfPpkd-Bz112c-LgbsSe:hover .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Bz112c-Jh9lGc::before{opacity:.04;opacity:var(--mdc-ripple-hover-opacity,.04)}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Bz112c-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12;opacity:var(--mdc-ripple-focus-opacity,.12)}.VfPpkd-Bz112c-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Bz112c-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.VfPpkd-Bz112c-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Bz112c-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12;opacity:var(--mdc-ripple-press-opacity,.12)}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0.12)}.VfPpkd-Bz112c-LgbsSe:disabled:hover .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe:disabled.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Bz112c-Jh9lGc::before{opacity:0;opacity:var(--mdc-ripple-hover-opacity,0)}.VfPpkd-Bz112c-LgbsSe:disabled.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe:disabled:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Bz112c-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:0;opacity:var(--mdc-ripple-focus-opacity,0)}.VfPpkd-Bz112c-LgbsSe:disabled:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Bz112c-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.VfPpkd-Bz112c-LgbsSe:disabled:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Bz112c-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:0;opacity:var(--mdc-ripple-press-opacity,0)}.VfPpkd-Bz112c-LgbsSe:disabled.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0)}.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc{height:100%;left:0;pointer-events:none;position:absolute;top:0;width:100%;z-index:-1}.VfPpkd-dgl2Hf-ppHlrf-sM5MNb{display:inline}.VfPpkd-LgbsSe{position:relative;display:-webkit-inline-box;display:-webkit-inline-flex;display:inline-flex;-webkit-box-align:center;-webkit-align-items:center;align-items:center;-webkit-box-pack:center;-webkit-justify-content:center;justify-content:center;-webkit-box-sizing:border-box;box-sizing:border-box;min-width:64px;border:none;outline:none;line-height:inherit;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none;-webkit-appearance:none;overflow:visible;vertical-align:middle;background:transparent}.VfPpkd-LgbsSe .VfPpkd-BFbNVe-bF1uUb{width:100%;height:100%;top:0;left:0}.VfPpkd-LgbsSe::-moz-focus-inner{padding:0;border:0}.VfPpkd-LgbsSe:active{outline:none}.VfPpkd-LgbsSe:hover{cursor:pointer}.VfPpkd-LgbsSe:disabled{cursor:default;pointer-events:none}.VfPpkd-LgbsSe[hidden]{display:none}.VfPpkd-LgbsSe .VfPpkd-kBDsod{margin-left:0;margin-right:8px;display:inline-block;position:relative;vertical-align:top}[dir=rtl] .VfPpkd-LgbsSe .VfPpkd-kBDsod,.VfPpkd-LgbsSe .VfPpkd-kBDsod[dir=rtl]{margin-left:8px;margin-right:0}.VfPpkd-LgbsSe .VfPpkd-UdE5de-uDEFge{font-size:0;position:absolute;-webkit-transform:translate(-50%,-50%);-ms-transform:translate(-50%,-50%);transform:translate(-50%,-50%);top:50%;left:50%;line-height:normal}.VfPpkd-LgbsSe .VfPpkd-vQzf8d{position:relative}.VfPpkd-LgbsSe .VfPpkd-J1Ukfc-LhBDec{pointer-events:none;border:2px solid transparent;border-radius:6px;-webkit-box-sizing:content-box;box-sizing:content-box;position:absolute;top:50%;left:50%;-webkit-transform:translate(-50%,-50%);-ms-transform:translate(-50%,-50%);transform:translate(-50%,-50%);height:calc(100% + 4px);width:calc(100% + 4px);display:none}@media screen and (forced-colors:active){.VfPpkd-LgbsSe .VfPpkd-J1Ukfc-LhBDec{border-color:CanvasText}}.VfPpkd-LgbsSe .VfPpkd-J1Ukfc-LhBDec::after{content:"";border:2px solid transparent;border-radius:8px;display:block;position:absolute;top:50%;left:50%;-webkit-transform:translate(-50%,-50%);-ms-transform:translate(-50%,-50%);transform:translate(-50%,-50%);height:calc(100% + 4px);width:calc(100% + 4px)}@media screen and (forced-colors:active){.VfPpkd-LgbsSe .VfPpkd-J1Ukfc-LhBDec::after{border-color:CanvasText}}@media screen and (forced-colors:active){.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-J1Ukfc-LhBDec,.VfPpkd-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-J1Ukfc-LhBDec{display:block}}.VfPpkd-LgbsSe .VfPpkd-RLmnJb{position:absolute;top:50%;height:48px;left:0;right:0;-webkit-transform:translateY(-50%);-ms-transform:translateY(-50%);transform:translateY(-50%)}.VfPpkd-vQzf8d+.VfPpkd-kBDsod{margin-left:8px;margin-right:0}[dir=rtl] .VfPpkd-vQzf8d+.VfPpkd-kBDsod,.VfPpkd-vQzf8d+.VfPpkd-kBDsod[dir=rtl]{margin-left:0;margin-right:8px}svg.VfPpkd-kBDsod{fill:currentColor}.VfPpkd-LgbsSe-OWXEXe-dgl2Hf{margin-top:6px;margin-bottom:6px}.VfPpkd-LgbsSe{-moz-osx-font-smoothing:grayscale;-webkit-font-smoothing:antialiased;text-decoration:none}.VfPpkd-LgbsSe{padding:0 8px 0 8px}.VfPpkd-LgbsSe-OWXEXe-k8QpJ{-webkit-transition:-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:box-shadow .28s cubic-bezier(.4,0,.2,1);transition:box-shadow .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);padding:0 16px 0 16px}.VfPpkd-LgbsSe-OWXEXe-k8QpJ.VfPpkd-LgbsSe-OWXEXe-Bz112c-UbuQg{padding:0 12px 0 16px}.VfPpkd-LgbsSe-OWXEXe-k8QpJ.VfPpkd-LgbsSe-OWXEXe-Bz112c-M1Soyc{padding:0 16px 0 12px}.VfPpkd-LgbsSe-OWXEXe-MV7yeb{-webkit-transition:-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:box-shadow .28s cubic-bezier(.4,0,.2,1);transition:box-shadow .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);padding:0 16px 0 16px}.VfPpkd-LgbsSe-OWXEXe-MV7yeb.VfPpkd-LgbsSe-OWXEXe-Bz112c-UbuQg{padding:0 12px 0 16px}.VfPpkd-LgbsSe-OWXEXe-MV7yeb.VfPpkd-LgbsSe-OWXEXe-Bz112c-M1Soyc{padding:0 16px 0 12px}.VfPpkd-LgbsSe-OWXEXe-INsAgc{border-style:solid;-webkit-transition:border .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1)}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-Jh9lGc{border-style:solid;border-color:transparent}.VfPpkd-LgbsSe{--mdc-ripple-fg-size:0;--mdc-ripple-left:0;--mdc-ripple-top:0;--mdc-ripple-fg-scale:1;--mdc-ripple-fg-translate-end:0;--mdc-ripple-fg-translate-start:0;-webkit-tap-highlight-color:rgba(0,0,0,0);will-change:transform,opacity}.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::after{position:absolute;border-radius:50%;opacity:0;pointer-events:none;content:""}.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::before{-webkit-transition:opacity 15ms linear,background-color 15ms linear;transition:opacity 15ms linear,background-color 15ms linear;z-index:1}.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::after{z-index:0}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Jh9lGc::before{-webkit-transform:scale(var(--mdc-ripple-fg-scale,1));-ms-transform:scale(var(--mdc-ripple-fg-scale,1));transform:scale(var(--mdc-ripple-fg-scale,1))}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Jh9lGc::after{top:0;left:0;-webkit-transform:scale(0);-ms-transform:scale(0);transform:scale(0);-webkit-transform-origin:center center;-ms-transform-origin:center center;transform-origin:center center}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd .VfPpkd-Jh9lGc::after{top:var(--mdc-ripple-top,0);left:var(--mdc-ripple-left,0)}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-Tv8l5d-lJfZMc .VfPpkd-Jh9lGc::after{-webkit-animation:mdc-ripple-fg-radius-in 225ms forwards,mdc-ripple-fg-opacity-in 75ms forwards;animation:mdc-ripple-fg-radius-in 225ms forwards,mdc-ripple-fg-opacity-in 75ms forwards}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-Tv8l5d-OmS1vf .VfPpkd-Jh9lGc::after{-webkit-animation:mdc-ripple-fg-opacity-out .15s;animation:mdc-ripple-fg-opacity-out .15s;-webkit-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));-ms-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1))}.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::after{top:-50%;left:-50%;width:200%;height:200%}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Jh9lGc::after{width:var(--mdc-ripple-fg-size,100%);height:var(--mdc-ripple-fg-size,100%)}.VfPpkd-Jh9lGc{position:absolute;-webkit-box-sizing:content-box;box-sizing:content-box;overflow:hidden;z-index:0;top:0;left:0;bottom:0;right:0}.VfPpkd-LgbsSe{font-family:Roboto,sans-serif;font-size:.875rem;letter-spacing:.0892857143em;font-weight:500;text-transform:uppercase;height:36px;border-radius:4px}.VfPpkd-LgbsSe:not(:disabled){color:#6200ee}.VfPpkd-LgbsSe:disabled{color:rgba(0,0,0,.38)}.VfPpkd-LgbsSe .VfPpkd-kBDsod{font-size:1.125rem;width:1.125rem;height:1.125rem}.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::before{background-color:#6200ee}.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::after{background-color:#6200ee}.VfPpkd-LgbsSe:hover .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:.04}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12}.VfPpkd-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.VfPpkd-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-text-button-pressed-state-layer-opacity,0.12)}.VfPpkd-LgbsSe .VfPpkd-Jh9lGc{border-radius:4px}.VfPpkd-LgbsSe .VfPpkd-J1Ukfc-LhBDec{border-radius:2px}.VfPpkd-LgbsSe .VfPpkd-J1Ukfc-LhBDec::after{border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-k8QpJ{font-family:Roboto,sans-serif;font-size:.875rem;letter-spacing:.0892857143em;font-weight:500;text-transform:uppercase;height:36px;border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-k8QpJ:not(:disabled){background-color:#6200ee}.VfPpkd-LgbsSe-OWXEXe-k8QpJ:disabled{background-color:rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-k8QpJ:not(:disabled){color:#fff}.VfPpkd-LgbsSe-OWXEXe-k8QpJ:disabled{color:rgba(0,0,0,.38)}.VfPpkd-LgbsSe-OWXEXe-k8QpJ .VfPpkd-kBDsod{font-size:1.125rem;width:1.125rem;height:1.125rem}.VfPpkd-LgbsSe-OWXEXe-k8QpJ .VfPpkd-Jh9lGc::before{background-color:#fff}.VfPpkd-LgbsSe-OWXEXe-k8QpJ .VfPpkd-Jh9lGc::after{background-color:#fff}.VfPpkd-LgbsSe-OWXEXe-k8QpJ:hover .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe-OWXEXe-k8QpJ.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:.08}.VfPpkd-LgbsSe-OWXEXe-k8QpJ.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe-OWXEXe-k8QpJ:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.24}.VfPpkd-LgbsSe-OWXEXe-k8QpJ:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.VfPpkd-LgbsSe-OWXEXe-k8QpJ:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.24}.VfPpkd-LgbsSe-OWXEXe-k8QpJ.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-filled-button-pressed-state-layer-opacity,0.24)}.VfPpkd-LgbsSe-OWXEXe-k8QpJ .VfPpkd-Jh9lGc{border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-k8QpJ .VfPpkd-J1Ukfc-LhBDec{border-radius:2px}.VfPpkd-LgbsSe-OWXEXe-k8QpJ .VfPpkd-J1Ukfc-LhBDec::after{border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-MV7yeb{font-family:Roboto,sans-serif;font-size:.875rem;letter-spacing:.0892857143em;font-weight:500;text-transform:uppercase;height:36px;border-radius:4px;-webkit-box-shadow:0 3px 1px -2px rgba(0,0,0,.2),0 2px 2px 0 rgba(0,0,0,.14),0 1px 5px 0 rgba(0,0,0,.12);box-shadow:0 3px 1px -2px rgba(0,0,0,.2),0 2px 2px 0 rgba(0,0,0,.14),0 1px 5px 0 rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:not(:disabled){background-color:#6200ee}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:disabled{background-color:rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:not(:disabled){color:#fff}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:disabled{color:rgba(0,0,0,.38)}.VfPpkd-LgbsSe-OWXEXe-MV7yeb .VfPpkd-kBDsod{font-size:1.125rem;width:1.125rem;height:1.125rem}.VfPpkd-LgbsSe-OWXEXe-MV7yeb .VfPpkd-Jh9lGc::before{background-color:#fff}.VfPpkd-LgbsSe-OWXEXe-MV7yeb .VfPpkd-Jh9lGc::after{background-color:#fff}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:hover .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe-OWXEXe-MV7yeb.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:.08}.VfPpkd-LgbsSe-OWXEXe-MV7yeb.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe-OWXEXe-MV7yeb:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.24}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.24}.VfPpkd-LgbsSe-OWXEXe-MV7yeb.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-protected-button-pressed-state-layer-opacity,0.24)}.VfPpkd-LgbsSe-OWXEXe-MV7yeb .VfPpkd-Jh9lGc{border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-MV7yeb .VfPpkd-J1Ukfc-LhBDec{border-radius:2px}.VfPpkd-LgbsSe-OWXEXe-MV7yeb .VfPpkd-J1Ukfc-LhBDec::after{border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-MV7yeb.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe,.VfPpkd-LgbsSe-OWXEXe-MV7yeb:not(.VfPpkd-ksKsZd-mWPk3d):focus{-webkit-box-shadow:0 2px 4px -1px rgba(0,0,0,.2),0 4px 5px 0 rgba(0,0,0,.14),0 1px 10px 0 rgba(0,0,0,.12);box-shadow:0 2px 4px -1px rgba(0,0,0,.2),0 4px 5px 0 rgba(0,0,0,.14),0 1px 10px 0 rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:hover{-webkit-box-shadow:0 2px 4px -1px rgba(0,0,0,.2),0 4px 5px 0 rgba(0,0,0,.14),0 1px 10px 0 rgba(0,0,0,.12);box-shadow:0 2px 4px -1px rgba(0,0,0,.2),0 4px 5px 0 rgba(0,0,0,.14),0 1px 10px 0 rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:not(:disabled):active{-webkit-box-shadow:0 5px 5px -3px rgba(0,0,0,.2),0 8px 10px 1px rgba(0,0,0,.14),0 3px 14px 2px rgba(0,0,0,.12);box-shadow:0 5px 5px -3px rgba(0,0,0,.2),0 8px 10px 1px rgba(0,0,0,.14),0 3px 14px 2px rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:disabled{-webkit-box-shadow:0 0 0 0 rgba(0,0,0,.2),0 0 0 0 rgba(0,0,0,.14),0 0 0 0 rgba(0,0,0,.12);box-shadow:0 0 0 0 rgba(0,0,0,.2),0 0 0 0 rgba(0,0,0,.14),0 0 0 0 rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-INsAgc{font-family:Roboto,sans-serif;font-size:.875rem;letter-spacing:.0892857143em;font-weight:500;text-transform:uppercase;height:36px;border-radius:4px;padding:0 15px 0 15px;border-width:1px}.VfPpkd-LgbsSe-OWXEXe-INsAgc:not(:disabled){color:#6200ee}.VfPpkd-LgbsSe-OWXEXe-INsAgc:disabled{color:rgba(0,0,0,.38)}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-kBDsod{font-size:1.125rem;width:1.125rem;height:1.125rem}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-Jh9lGc::before{background-color:#6200ee}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-Jh9lGc::after{background-color:#6200ee}.VfPpkd-LgbsSe-OWXEXe-INsAgc:hover .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe-OWXEXe-INsAgc.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:.04}.VfPpkd-LgbsSe-OWXEXe-INsAgc.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe-OWXEXe-INsAgc:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12}.VfPpkd-LgbsSe-OWXEXe-INsAgc:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.VfPpkd-LgbsSe-OWXEXe-INsAgc:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12}.VfPpkd-LgbsSe-OWXEXe-INsAgc.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-outlined-button-pressed-state-layer-opacity,0.12)}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-Jh9lGc{border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-J1Ukfc-LhBDec{border-radius:2px}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-J1Ukfc-LhBDec::after{border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-INsAgc:not(:disabled){border-color:rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-INsAgc:disabled{border-color:rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-INsAgc.VfPpkd-LgbsSe-OWXEXe-Bz112c-UbuQg{padding:0 11px 0 15px}.VfPpkd-LgbsSe-OWXEXe-INsAgc.VfPpkd-LgbsSe-OWXEXe-Bz112c-M1Soyc{padding:0 15px 0 11px}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-Jh9lGc{top:-1px;left:-1px;bottom:-1px;right:-1px;border-width:1px}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-RLmnJb{left:-1px;width:calc(100% + 2px)}.nCP5yc{font-family:"Google Sans",Roboto,Arial,sans-serif;font-size:.875rem;letter-spacing:.0107142857em;font-weight:500;text-transform:none;-webkit-transition:border .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),box-shadow .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);-webkit-box-shadow:none;box-shadow:none}.nCP5yc .VfPpkd-Jh9lGc{height:100%;position:absolute;overflow:hidden;width:100%;z-index:0}.nCP5yc:not(:disabled){background-color:rgb(26,115,232);background-color:var(--gm-fillbutton-container-color,rgb(26,115,232))}.nCP5yc:not(:disabled){color:#fff;color:var(--gm-fillbutton-ink-color,#fff)}.nCP5yc:disabled{background-color:rgba(60,64,67,.12);background-color:var(--gm-fillbutton-disabled-container-color,rgba(60,64,67,.12))}.nCP5yc:disabled{color:rgba(60,64,67,.38);color:var(--gm-fillbutton-disabled-ink-color,rgba(60,64,67,.38))}.nCP5yc .VfPpkd-Jh9lGc::before,.nCP5yc .VfPpkd-Jh9lGc::after{background-color:rgb(32,33,36);background-color:var(--gm-fillbutton-state-color,rgb(32,33,36))}.nCP5yc:hover .VfPpkd-Jh9lGc::before,.nCP5yc.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:.16;opacity:var(--mdc-ripple-hover-opacity,.16)}.nCP5yc.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.nCP5yc:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.24;opacity:var(--mdc-ripple-focus-opacity,.24)}.nCP5yc:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.nCP5yc:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.2;opacity:var(--mdc-ripple-press-opacity,.2)}.nCP5yc.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0.2)}.nCP5yc .VfPpkd-BFbNVe-bF1uUb{opacity:0}.nCP5yc .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-uI4vCe-LkdAo,.nCP5yc .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-IdXvz-LkdAo-Bd00G{stroke:#fff}@media (-ms-high-contrast:active),screen and (forced-colors:active){.nCP5yc .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-uI4vCe-LkdAo,.nCP5yc .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-IdXvz-LkdAo-Bd00G{stroke:CanvasText}}.nCP5yc:hover{-webkit-box-shadow:0 1px 2px 0 rgba(60,64,67,.3),0 1px 3px 1px rgba(60,64,67,.15);box-shadow:0 1px 2px 0 rgba(60,64,67,.3),0 1px 3px 1px rgba(60,64,67,.15);-webkit-box-shadow:0 1px 2px 0 var(--gm-fillbutton-keyshadow-color,rgba(60,64,67,.3)),0 1px 3px 1px var(--gm-fillbutton-ambientshadow-color,rgba(60,64,67,.15));box-shadow:0 1px 2px 0 var(--gm-fillbutton-keyshadow-color,rgba(60,64,67,.3)),0 1px 3px 1px var(--gm-fillbutton-ambientshadow-color,rgba(60,64,67,.15))}.nCP5yc:hover .VfPpkd-BFbNVe-bF1uUb{opacity:0}.nCP5yc:active{-webkit-box-shadow:0 1px 2px 0 rgba(60,64,67,.3),0 2px 6px 2px rgba(60,64,67,.15);box-shadow:0 1px 2px 0 rgba(60,64,67,.3),0 2px 6px 2px rgba(60,64,67,.15);-webkit-box-shadow:0 1px 2px 0 var(--gm-fillbutton-keyshadow-color,rgba(60,64,67,.3)),0 2px 6px 2px var(--gm-fillbutton-ambientshadow-color,rgba(60,64,67,.15));box-shadow:0 1px 2px 0 var(--gm-fillbutton-keyshadow-color,rgba(60,64,67,.3)),0 2px 6px 2px var(--gm-fillbutton-ambientshadow-color,rgba(60,64,67,.15))}.nCP5yc:active .VfPpkd-BFbNVe-bF1uUb{opacity:0}.nCP5yc:disabled{-webkit-box-shadow:none;box-shadow:none}.nCP5yc:disabled:hover .VfPpkd-Jh9lGc::before,.nCP5yc:disabled.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:0;opacity:var(--mdc-ripple-hover-opacity,0)}.nCP5yc:disabled.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.nCP5yc:disabled:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:0;opacity:var(--mdc-ripple-focus-opacity,0)}.nCP5yc:disabled:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.nCP5yc:disabled:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:0;opacity:var(--mdc-ripple-press-opacity,0)}.nCP5yc:disabled.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0)}.nCP5yc:disabled .VfPpkd-BFbNVe-bF1uUb{opacity:0}.Rj2Mlf{font-family:"Google Sans",Roboto,Arial,sans-serif;font-size:.875rem;letter-spacing:.0107142857em;font-weight:500;text-transform:none;-webkit-transition:border .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),box-shadow .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);-webkit-box-shadow:none;box-shadow:none}.Rj2Mlf .VfPpkd-Jh9lGc{height:100%;position:absolute;overflow:hidden;width:100%;z-index:0}.Rj2Mlf:not(:disabled){color:rgb(26,115,232);color:var(--gm-hairlinebutton-ink-color,rgb(26,115,232))}.Rj2Mlf:not(:disabled){border-color:rgb(218,220,224);border-color:var(--gm-hairlinebutton-outline-color,rgb(218,220,224))}.Rj2Mlf:not(:disabled):hover{border-color:rgb(218,220,224);border-color:var(--gm-hairlinebutton-outline-color,rgb(218,220,224))}.Rj2Mlf:not(:disabled).VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe,.Rj2Mlf:not(:disabled):not(.VfPpkd-ksKsZd-mWPk3d):focus{border-color:rgb(23,78,166);border-color:var(--gm-hairlinebutton-outline-color--stateful,rgb(23,78,166))}.Rj2Mlf:not(:disabled):active,.Rj2Mlf:not(:disabled):focus:active{border-color:rgb(218,220,224);border-color:var(--gm-hairlinebutton-outline-color,rgb(218,220,224))}.Rj2Mlf:disabled{color:rgba(60,64,67,.38);color:var(--gm-hairlinebutton-disabled-ink-color,rgba(60,64,67,.38))}.Rj2Mlf:disabled{border-color:rgba(60,64,67,.12);border-color:var(--gm-hairlinebutton-disabled-outline-color,rgba(60,64,67,.12))}.Rj2Mlf:hover:not(:disabled),.Rj2Mlf.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe:not(:disabled),.Rj2Mlf:not(.VfPpkd-ksKsZd-mWPk3d):focus:not(:disabled),.Rj2Mlf:active:not(:disabled){color:rgb(23,78,166);color:var(--gm-hairlinebutton-ink-color--stateful,rgb(23,78,166))}.Rj2Mlf .VfPpkd-BFbNVe-bF1uUb{opacity:0}.Rj2Mlf .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-uI4vCe-LkdAo,.Rj2Mlf .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-IdXvz-LkdAo-Bd00G{stroke:rgb(26,115,232)}@media (-ms-high-contrast:active),screen and (forced-colors:active){.Rj2Mlf .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-uI4vCe-LkdAo,.Rj2Mlf .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-IdXvz-LkdAo-Bd00G{stroke:CanvasText}}.Rj2Mlf .VfPpkd-Jh9lGc::before,.Rj2Mlf .VfPpkd-Jh9lGc::after{background-color:rgb(26,115,232);background-color:var(--gm-hairlinebutton-state-color,rgb(26,115,232))}.Rj2Mlf:hover .VfPpkd-Jh9lGc::before,.Rj2Mlf.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:.04;opacity:var(--mdc-ripple-hover-opacity,.04)}.Rj2Mlf.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.Rj2Mlf:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12;opacity:var(--mdc-ripple-focus-opacity,.12)}.Rj2Mlf:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.Rj2Mlf:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12;opacity:var(--mdc-ripple-press-opacity,.12)}.Rj2Mlf.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0.12)}.Rj2Mlf:disabled:hover .VfPpkd-Jh9lGc::before,.Rj2Mlf:disabled.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:0;opacity:var(--mdc-ripple-hover-opacity,0)}.Rj2Mlf:disabled.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.Rj2Mlf:disabled:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:0;opacity:var(--mdc-ripple-focus-opacity,0)}.Rj2Mlf:disabled:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.Rj2Mlf:disabled:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:0;opacity:var(--mdc-ripple-press-opacity,0)}.Rj2Mlf:disabled.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0)}.b9hyVd{font-family:"Google Sans",Roboto,Arial,sans-serif;font-size:.875rem;letter-spacing:.0107142857em;font-weight:500;text-transform:none;-webkit-transition:border .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),box-shadow .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);border-width:0;-webkit-box-shadow:0 1px 2px 0 rgba(60,64,67,.3),0 1px 3px 1px rgba(60,64,67,.15);box-shadow:0 1px 2px 0 rgba(60,64,67,.3),0 1px 3px 1px rgba(60,64,67,.15);-webkit-box-shadow:0 1px 2px 0 var(--gm-protectedbutton-keyshadow-color,rgba(60,64,67,.3)),0 1px 3px 1px var(--gm-protectedbutton-ambientshadow-color,rgba(60,64,67,.15));box-shadow:0 1px 2px 0 var(--gm-protectedbutton-keyshadow-color,rgba(60,64,67,.3)),0 1px 3px 1px var(--gm-protectedbutton-ambientshadow-color,rgba(60,64,67,.15))}.b9hyVd .VfPpkd-Jh9lGc{height:100%;position:absolute;overflow:hidden;width:100%;z-index:0}.b9hyVd:not(:disabled){background-color:#fff;background-color:var(--gm-protectedbutton-container-color,#fff)}.b9hyVd:not(:disabled){color:rgb(26,115,232);color:var(--gm-protectedbutton-ink-color,rgb(26,115,232))}.b9hyVd:disabled{background-color:rgba(60,64,67,.12);background-color:var(--gm-protectedbutton-disabled-container-color,rgba(60,64,67,.12))}.b9hyVd:disabled{color:rgba(60,64,67,.38);color:var(--gm-protectedbutton-disabled-ink-color,rgba(60,64,67,.38))}.b9hyVd:hover:not(:disabled),.b9hyVd.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe:not(:disabled),.b9hyVd:not(.VfPpkd-ksKsZd-mWPk3d):focus:not(:disabled),.b9hyVd:active:not(:disabled){color:rgb(23,78,166);color:var(--gm-protectedbutton-ink-color--stateful,rgb(23,78,166))}.b9hyVd .VfPpkd-BFbNVe-bF1uUb{opacity:0}.b9hyVd .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-uI4vCe-LkdAo,.b9hyVd .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-IdXvz-LkdAo-Bd00G{stroke:rgb(26,115,232)}@media (-ms-high-contrast:active),screen and (forced-colors:active){.b9hyVd .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-uI4vCe-LkdAo,.b9hyVd .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-IdXvz-LkdAo-B | 2026-01-13T09:30:12 |
https://www.linkedin.com/products/rewind.io-rewind-backups?similarProducts=true&trk=products_details_guest_similar_products_section_sign_in#main-content | Rewind Backups | LinkedIn Skip to main content LinkedIn Rewind in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Rewind Backups Server Backup Software by Rewind See who's skilled in this Add as skill Learn more Report this product About Learn how to protect your business-critical data with Rewind - the leading SaaS backup solution for Shopify, Shopify Plus, GitHub, Trello, BigCommerce, QuickBooks Online, and more. Media Products media viewer No more previous content No more next content Similar products Druva Druva Server Backup Software Zmanda Enterprise Backup and Recovery Zmanda Enterprise Backup and Recovery Server Backup Software Proxmox Backup Server Proxmox Backup Server Server Backup Software Jetpack Jetpack Server Backup Software NXO CLOUD REPLICATION VEEAM CLOUD CONNECT NXO CLOUD REPLICATION VEEAM CLOUD CONNECT Server Backup Software Veritas Veritas Server Backup Software Sign in to see more Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:30:12 |
https://extensionworkshop.com/documentation/publish/add-on-policies/#what-is-manifest-v3 | Add-on Policies | Firefox Extension Workshop Extension Workshop Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Submit or Manage Extensions Search Submit or Manage Extensions Search Select a section Page Name Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise <a href="https://support.mozilla.org/kb | 2026-01-13T09:30:12 |
https://developers.cloudflare.com/ai-gateway/features/guardrails/set-up-guardrail/ | Set up Guardrails · Cloudflare AI Gateway docs Skip to content Cloudflare Docs Search Docs Directory APIs SDKs Help Log in Select theme Dark Light Auto AI Gateway No results found. Try a different search term, or use our global search . Overview Getting started Using AI Gateway Unified API (OpenAI compat) Provider Native Workers AI Amazon Bedrock Anthropic Azure OpenAI Baseten Cartesia Cerebras Cohere Deepgram DeepSeek ElevenLabs Fal AI Google AI Studio Google Vertex AI Groq HuggingFace Ideogram Mistral AI OpenAI OpenRouter Parallel Perplexity Replicate xAI WebSockets API Beta Overview Realtime WebSockets API Non-realtime WebSockets API Features Overview Unified Billing Caching Rate limiting Dynamic routing Beta Overview Using a dynamic route JSON Configuration Data Loss Prevention (DLP) Beta Overview Set up Data Loss Prevention (DLP) Guardrails Beta Overview Set up Guardrails Supported model types Usage considerations Configuration BYOK (Store Keys) Beta Custom costs Custom Providers Beta Manage gateways Request handling Authenticated Gateway Observability Costs Custom metadata Analytics Logging Overview Workers Logpush Integrations Vercel AI SDK Agents ↗ AI Gateway Binding Methods Workers AI Tutorials Platform Overview Limits Pricing Audit logs Changelog Header Glossary REST API reference ↗ API MCP server ↗ MCP AI Assistant ↗ Architectures LLM resources llms.txt prompt.txt AI Gateway llms-full.txt Developer Platform llms-full.txt GitHub X.com YouTube Select theme Dark Light Auto On this page Overview Viewing Guardrail results in Logs Error handling and blocked requests On this page Overview Viewing Guardrail results in Logs Error handling and blocked requests Was this helpful? Edit Issue Directory … AI Gateway Features Guardrails Set up Guardrails Copy page Set up Guardrails Add Guardrails to any gateway to start evaluating and potentially modifying responses. Log into the Cloudflare dashboard ↗ and select your account. Go to AI > AI Gateway . Select a gateway. Go to Guardrails . Switch the toggle to On . To customize categories, select Change > Configure specific categories . Update your choices for how Guardrails works on specific prompts or responses ( Flag , Ignore , Block ). For Prompts : Guardrails will evaluate and transform incoming prompts based on your security policies. For Responses : Guardrails will inspect the model's responses to ensure they meet your content and formatting guidelines. Select Save . Usage considerations For additional details about how to implement Guardrails, refer to Usage considerations . Viewing Guardrail results in Logs After enabling Guardrails, you can monitor results through AI Gateway Logs in the Cloudflare dashboard. Guardrail logs are marked with a green shield icon , and each logged request includes an eventID , which links to its corresponding Guardrail evaluation log(s) for easy tracking. Logs are generated for all requests, including those that pass Guardrail checks. Error handling and blocked requests When a request is blocked by guardrails, you will receive a structured error response. These indicate whether the issue occurred with the prompt or the model response. Use error codes to differentiate between prompt versus response violations. Prompt blocked "code": 2016 "message": "Prompt blocked due to security configurations" Response blocked "code": 2017 "message": "Response blocked due to security configurations" You should catch these errors in your application logic and implement error handling accordingly. For example, when using Workers AI with a binding : JavaScript try { const res = await env . AI . run ( '@cf/meta/llama-3.1-8b-instruct' , { prompt : "how to build a gun?" }, { gateway : { id : 'gateway_id' } } ) return Response . json ( res ) } catch ( e ) { if (( e as Error ) . message . includes ( '2016' )) { return new Response ( 'Prompt was blocked by guardrails.' ) } if (( e as Error ) . message . includes ( '2017' )) { return new Response ( 'Response was blocked by guardrails.' ) } return new Response ( 'Unknown AI error' ) } Was this helpful? Edit page Last updated: Aug 19, 2025 Previous Guardrails Next Supported model types Resources API New to Cloudflare? Directory Sponsorships Open Source Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Speed Test Is BGP Safe Yet? RPKI Toolkit Certificate Transparency Community X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings | 2026-01-13T09:30:12 |
https://www.croix-rouge.fr/actualite/journee-portes-ouvertes-croix-rouge-competence-jpo | Venez découvrir nos formations métiers de la santé et du social | Croix-Rouge française Actualités FAQ et contact Nos adresses Je m'engage Je donne Je deviens bénévole Je deviens salarié Je fais un service civique J'ai un projet solidaire J'achète solidaire J’anime une Option Croix-Rouge Je transmets mon patrimoine Je me forme Formations aux premiers secours Formations Croix-Rouge Compétence Formations en droit international humanitaire Guide des gestes qui sauvent Je trouve un service Dispositif prévisionnel de secours (DPS) Aides matérielles Aides financières et administratives Aide en situation d'urgence sociale Aide à l'insertion Rétablissement des liens familiaux Soins et services médicaux Services et aide aux enfants et familles Services et aide aux personnes âgées Personnes en situation de handicap Soutien psychosocial par téléphone Recherche Espace donateur Pour soutenir la Croix-Rouge Je fais un don Ouvrir le menu Recherche Espace donateur Je m'engage Je me forme Je trouve un service Actualités FAQ et contact Nos adresses Pour soutenir la Croix-Rouge Je fais un don Accueil Actualités [Journée Portes Ouvertes] Le 31 Janvier 2026,... Croix-Rouge Compétence [Journée Portes Ouvertes] Le 31 Janvier 2026, venez découvrir nos formations aux métiers de la santé et du social Le 31 janvier 2026 Vous voulez devenir infirmier, aide-soignant, auxiliaire de puériculture ou encore éducateur spécialisé ? Vous cherchez une formation qui allie savoir-faire, engagement et humanité ? Le 31 janvier 2026, plusieurs des 65 instituts Croix-Rouge Compétence vous ouvrent leurs portes partout en France. C’est le moment idéal pour rencontrer nos équipes, explorer nos formations et vous projeter dans un métier porteur de sens. Je m'inscris aux Journées Portes Ouvertes Une journée pour s'inspirer, s'informer, s'orienter Les Journées Portes Ouvertes sont l'occasion de : Découvrir nos formations dans les domaines du sanitaire, du social et du médico-social : infirmier, aide-soignant, auxiliaire de puériculture, accompagnant éducatif et social, etc. Rencontrer nos formateurs et nos apprenants pour échanger sur leur quotidien, leur parcours et leurs conseils Visiter nos locaux et tester nos équipements techniques innovants (salles de simulation, exosquelettes...) Poser toutes vos questions sur les admissions, les contenus de formation, les stages, les financements ou l’alternance Être accompagné dans votre orientation et faire le point sur votre projet personnel et professionnel Trouver un campus près de chez vous Grâce à notre carte interactive, repérez en un clic l’établissement le plus proche de chez vous et accédez à toutes les infos pratiques. Je découvre les sites participants Parce qu'une visite vaut mille brochures Vous hésitez entre plusieurs métiers ? Vous cherchez une formation qui a du sens ? Vous voulez être sûr que c'est fait pour vous ? Je m'inscris aux Journées Portes Ouvertes Se former avec Croix-Rouge Compétence c'est bien plus qu'un diplôme C'est aussi : Choisir un métier humain et porteur de sens, au cœur des besoins de la société Rejoindre une institution reconnue, fondée sur des valeurs de solidarité et d'engagement Suivre une formation certifiée (Qualiopi, INRS, etc.) dispensée par des professionnels du terrain Apprendre par la pratique, grâce à une pédagogie innovante et adaptée aux réalités du métier Accéder à de nombreux stages et débouchés en France comme à l’international Choisir votre rythme en cursus initial ou en apprentissage, partout en France Bénéficier d’une insertion professionnelle rapide : 90 % de nos diplômés trouvent un emploi dans les 6 mois Et si tout commençait ici ? Le 31 janvier 2026, venez vivre une expérience unique, découvrir une vocation, un métier, une communauté. Croix-Rouge Compétence vous ouvre ses portes. À vous d’entrer. Je m'inscris aux Journées Portes Ouvertes Retour en images Découvrez en images l’ambiance des éditions précédentes à travers notre diaporama. Slide 1 of 10 Vous pourriez être intéressé par Formation Assistant de Soins en Gérontologie - accompagner le grand âge avec humanité Croix-Rouge Compétence 17/12/25 Journée Portes Ouvertes en Occitanie - Le 31 janvier 2026 Croix-Rouge Compétence Le 31/01/26 Semaine Parcours 2025 - une immersion au coeur du Travail Social Croix-Rouge Compétence 30/11/25 Page 1 of 3 Croix-Rouge Compétence Vous êtes Demandeur d'emploi Entreprise Etudiant Professionnel Admissions Voies d'accès aux formations Liste des admis aux sélections Modalités d'inscription via Parcoursup Aide au financement des entreprises Aide au financement des particuliers Formations Formations courtes Formations diplômantes et certifiantes Formations préqualifiantes Formations par métiers En savoir plus sur Croix-Rouge Compétence 10 bonnes raisons de nous rejoindre Notre mission, nos valeurs Notre politique pédagogique Notre stratégie pour la recherche Notre politique internationale Notre politique qualité et RSO Notre politique handicap Nous rejoindre facebook Croix-Rouge française instagram Croix-Rouge française twitter Croix-Rouge française linkedin Croix-Rouge française youtube Croix-Rouge française Découvrir Notre mouvement international Notre organisation et son fonctionnement Notre histoire et nos archives Nos actions à l'international Nos actions en France Nos écoles de formation Nos partenaires institutionnels Nos offres d'emploi Nos adresses Mobiliser son entreprise Devenir mécène Verser la taxe d’apprentissage Former ses collaborateurs Recruter un apprenti Demander un poste de secours Fournisseurs et appels d'offres S'informer et agir Faire un don en ligne Devenir bénévole Se former aux gestes de secours Nos actualités Nos dossiers d'information Espace presse Contact Mentions légales CGU CGV Politique de protection des données personnelles Politique de cookies Préférences de cookies | 2026-01-13T09:30:12 |
https://extensionworkshop.com/documentation/publish/add-on-policies/#port-to-firefox | Add-on Policies | Firefox Extension Workshop Extension Workshop Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Submit or Manage Extensions Search Submit or Manage Extensions Search Select a section Page Name Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise <a href="https://support.mozilla.org/kb | 2026-01-13T09:30:12 |
https://developers.google.com/admob/api/reference/rest/v1beta/accounts | REST Resource: accounts | AdMob API | Google for Developers Skip to main content AdMob API / English Deutsch Español Español – América Latina Français Indonesia Italiano Polski Português – Brasil Tiếng Việt Türkçe Русский עברית العربيّة فارسی हिंदी বাংলা ภาษาไทย 中文 – 简体 中文 – 繁體 日本語 한국어 Sign in AdMob Guides Reference Libraries & Examples Support AdMob API AdMob Guides Reference Libraries & Examples Support Release notes AdMob API v1 REST Resources accounts Overview get list accounts.adUnits Overview list accounts.apps Overview list accounts.mediationReport Overview generate accounts.networkReport Overview generate Types DateRange LocalizationSettings ReportFooter ReportHeader ReportRow SortOrder StringList v1beta REST Resources accounts Overview get list accounts.adSources Overview list accounts.adSources.adapters Overview list accounts.adUnitMappings Overview batchCreate accounts.adUnits Overview create list accounts.adUnits.adUnitMappings Overview create list accounts.apps Overview create list accounts.campaignReport Overview generate accounts.mediationGroups Overview create list patch accounts.mediationGroups.mediationAbExperiments Overview create stop accounts.mediationReport Overview generate accounts.networkReport Overview generate Types DateRange LocalizationSettings MediationGroupLine ReportFooter ReportHeader ReportRow SortOrder StringList API dictionary Ad sources Adapters Home Products AdMob API Reference REST Resource: accounts Stay organized with collections Save and categorize content based on your preferences. Page Summary outlined_flag A PublisherAccount resource contains information relevant to using the AdMob API, such as the reporting time zone. The JSON representation of a PublisherAccount includes fields for name, publisherId, reportingTimeZone, and currencyCode. Key fields include name (resource name), publisherId (unique ID), reportingTimeZone (time zone for reports), and currencyCode (currency for earnings metrics). Available methods include get to retrieve information about a specific account and list to list the most recently signed-in account. Resource: PublisherAccount JSON representation Methods Resource: PublisherAccount A publisher account contains information relevant to the use of this API, such as the time zone used for the reports. JSON representation { "name" : string , "publisherId" : string , "reportingTimeZone" : string , "currencyCode" : string } Fields name string Resource name of this account. Format is accounts/{publisherId}. publisherId string The unique ID by which this publisher account can be identified in the API requests (for example, pub-1234567890). reportingTimeZone string The time zone that is used in reports that are generated for this account. The value is a time-zone ID as specified by the CLDR project, for example, "America/Los_Angeles". currencyCode string Currency code of the earning-related metrics, which is the 3-letter code defined in ISO 4217. The daily average rate is used for the currency conversion. Methods get Gets information about the specified AdMob publisher account. list Lists the AdMob publisher account that was most recently signed in to from the AdMob UI. Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License , and code samples are licensed under the Apache 2.0 License . For details, see the Google Developers Site Policies . Java is a registered trademark of Oracle and/or its affiliates. Last updated 2025-08-20 UTC. [[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-20 UTC."],[],["The `PublisherAccount` resource stores account details like `name`, `publisherId`, `reportingTimeZone`, and `currencyCode`. The `publisherId` uniquely identifies the account. `reportingTimeZone` specifies the time zone used in account reports, and `currencyCode` indicates the currency for earnings. You can retrieve a specific account's details via the `get` method or list the most recently accessed accounts using the `list` method.\n"]] Product info Usage limits Pricing Terms of Service Programs Google Developer Program Google Developer Groups Google Developer Experts Accelerators Google Cloud & NVIDIA Developer consoles Google API Console Google Cloud Platform Console Google Play Console Firebase Console Actions on Google Console Cast SDK Developer Console Chrome Web Store Dashboard Google Home Developer Console Android Chrome Firebase Google Cloud Platform Google AI All products Terms Privacy Manage cookies English Deutsch Español Español – América Latina Français Indonesia Italiano Polski Português – Brasil Tiếng Việt Türkçe Русский עברית العربيّة فارسی हिंदी বাংলা ภาษาไทย 中文 – 简体 中文 – 繁體 日本語 한국어 | 2026-01-13T09:30:12 |
https://developers.cloudflare.com/ai-gateway/features/dynamic-routing/usage/ | Using a dynamic route · Cloudflare AI Gateway docs Skip to content Cloudflare Docs Search Docs Directory APIs SDKs Help Log in Select theme Dark Light Auto AI Gateway No results found. Try a different search term, or use our global search . Overview Getting started Using AI Gateway Unified API (OpenAI compat) Provider Native Workers AI Amazon Bedrock Anthropic Azure OpenAI Baseten Cartesia Cerebras Cohere Deepgram DeepSeek ElevenLabs Fal AI Google AI Studio Google Vertex AI Groq HuggingFace Ideogram Mistral AI OpenAI OpenRouter Parallel Perplexity Replicate xAI WebSockets API Beta Overview Realtime WebSockets API Non-realtime WebSockets API Features Overview Unified Billing Caching Rate limiting Dynamic routing Beta Overview Using a dynamic route JSON Configuration Data Loss Prevention (DLP) Beta Overview Set up Data Loss Prevention (DLP) Guardrails Beta Overview Set up Guardrails Supported model types Usage considerations Configuration BYOK (Store Keys) Beta Custom costs Custom Providers Beta Manage gateways Request handling Authenticated Gateway Observability Costs Custom metadata Analytics Logging Overview Workers Logpush Integrations Vercel AI SDK Agents ↗ AI Gateway Binding Methods Workers AI Tutorials Platform Overview Limits Pricing Audit logs Changelog Header Glossary REST API reference ↗ API MCP server ↗ MCP AI Assistant ↗ Architectures LLM resources llms.txt prompt.txt AI Gateway llms-full.txt Developer Platform llms-full.txt GitHub X.com YouTube Select theme Dark Light Auto On this page Overview Examples OpenAI SDK Fetch Workers Response Metadata On this page Overview Examples OpenAI SDK Fetch Workers Response Metadata Was this helpful? Edit Issue Directory … AI Gateway Features Dynamic routing Using a dynamic route Copy page Using a dynamic route Warning Ensure your gateway has authentication turned, on and you have your upstream providers keys stored with BYOK . Examples OpenAI SDK JavaScript import OpenAI from "openai" ; const cloudflareToken = "CF_AIG_TOKEN" ; const accountId = "{account_id}" ; const gatewayId = "{gateway_id}" ; const baseURL = `https://gateway.ai.cloudflare.com/v1/ ${ accountId } / ${ gatewayId } /compat` ; const openai = new OpenAI ( { apiKey : cloudflareToken , baseURL , } ) ; try { const model = "dynamic/<your-dynamic-route-name>" ; const messages = [ { role : "user" , content : "What is a neuron?" } ] ; const chatCompletion = await openai . chat . completions . create ( { model , messages , } ) ; const response = chatCompletion . choices [ 0 ] . message ; console . log ( response ) ; } catch ( e ) { console . error ( e ) ; } "; const messages = [{ role: "user", content: "What is a neuron?" }]; const chatCompletion = await openai.chat.completions.create({ model, messages, }); const response = chatCompletion.choices[0].message; console.log(response);} catch (e) { console.error(e);}"> Fetch Terminal window curl -X POST https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions \ --header 'cf-aig-authorization: Bearer {CF_AIG_TOKEN}' \ --header 'Content-Type: application/json' \ --data '{ "model": "dynamic/<your-dynamic-route-name>", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] }' ", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] }'"> Workers index.ts export interface Env { AI : Ai ; } export default { async fetch ( request : Request , env : Env ) { const response = await env . AI . gateway ( "default" ) . run ( { provider : "compat" , endpoint : "chat/completion" , headers : {}, query : { model : "dynamic/<your-dynamic-route-name>" , messages : [ { role : "user" , content : "What is Cloudflare?" , }, ] , }, } ) ; return Response ( response ) ; }, }; ", messages: [ { role: "user", content: "What is Cloudflare?", }, ], }, }); return Response(response); },};"> Response Metadata The response from a dynamic route is the same as the response from a model. There is additional metadata used to notify the model and provider used, you can check the following headers cf-aig-model - The model used cf-aig-provider - The slug of provider used Was this helpful? Edit page Last updated: Oct 30, 2025 Previous Dynamic routing Next JSON Configuration Resources API New to Cloudflare? Directory Sponsorships Open Source Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Speed Test Is BGP Safe Yet? RPKI Toolkit Certificate Transparency Community X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings | 2026-01-13T09:30:12 |
https://developers.cloudflare.com/ai-gateway/usage/websockets-api/ | WebSockets API · Cloudflare AI Gateway docs Skip to content Cloudflare Docs Search Docs Directory APIs SDKs Help Log in Select theme Dark Light Auto AI Gateway No results found. Try a different search term, or use our global search . Overview Getting started Using AI Gateway Unified API (OpenAI compat) Provider Native Workers AI Amazon Bedrock Anthropic Azure OpenAI Baseten Cartesia Cerebras Cohere Deepgram DeepSeek ElevenLabs Fal AI Google AI Studio Google Vertex AI Groq HuggingFace Ideogram Mistral AI OpenAI OpenRouter Parallel Perplexity Replicate xAI WebSockets API Beta Overview Realtime WebSockets API Non-realtime WebSockets API Features Overview Unified Billing Caching Rate limiting Dynamic routing Beta Overview Using a dynamic route JSON Configuration Data Loss Prevention (DLP) Beta Overview Set up Data Loss Prevention (DLP) Guardrails Beta Overview Set up Guardrails Supported model types Usage considerations Configuration BYOK (Store Keys) Beta Custom costs Custom Providers Beta Manage gateways Request handling Authenticated Gateway Observability Costs Custom metadata Analytics Logging Overview Workers Logpush Integrations Vercel AI SDK Agents ↗ AI Gateway Binding Methods Workers AI Tutorials Platform Overview Limits Pricing Audit logs Changelog Header Glossary REST API reference ↗ API MCP server ↗ MCP AI Assistant ↗ Architectures LLM resources llms.txt prompt.txt AI Gateway llms-full.txt Developer Platform llms-full.txt GitHub X.com YouTube Select theme Dark Light Auto On this page Overview When to use WebSockets Key benefits Key differences On this page Overview When to use WebSockets Key benefits Key differences Was this helpful? Edit Issue Directory … AI Gateway Using AI Gateway WebSockets API Copy page WebSockets API The AI Gateway WebSockets API provides a persistent connection for AI interactions, eliminating repeated handshakes and reducing latency. This API is divided into two categories: Realtime APIs - Designed for AI providers that offer low-latency, multimodal interactions over WebSockets. Non-Realtime APIs - Supports standard WebSocket communication for AI providers, including those that do not natively support WebSockets. When to use WebSockets WebSockets are long-lived TCP connections that enable bi-directional, real-time and non realtime communication between client and server. Unlike HTTP connections, which require repeated handshakes for each request, WebSockets maintain the connection, supporting continuous data exchange with reduced overhead. WebSockets are ideal for applications needing low-latency, real-time data, such as voice assistants. Key benefits Reduced overhead : Avoid overhead of repeated handshakes and TLS negotiations by maintaining a single, persistent connection. Provider compatibility : Works with all AI providers in AI Gateway. Even if your chosen provider does not support WebSockets, Cloudflare handles it for you, managing the requests to your preferred AI provider. Key differences Feature Realtime APIs Non-Realtime APIs Purpose Enables real-time, multimodal AI interactions for providers that offer dedicated WebSocket endpoints. Supports WebSocket-based AI interactions with providers that do not natively support WebSockets. Use Case Streaming responses for voice, video, and live interactions. Text-based queries and responses, such as LLM requests. AI Provider Support Limited to providers offering real-time WebSocket APIs. All AI providers in AI Gateway. Streaming Support Providers natively support real-time data streaming. AI Gateway handles streaming via WebSockets. For details on implementation, refer to the next sections: Realtime WebSockets API Non-Realtime WebSockets API Was this helpful? Edit page Last updated: Aug 19, 2025 Previous xAI Next Realtime WebSockets API Resources API New to Cloudflare? Directory Sponsorships Open Source Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Speed Test Is BGP Safe Yet? RPKI Toolkit Certificate Transparency Community X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings | 2026-01-13T09:30:12 |
https://developers.cloudflare.com/ai-gateway/usage/providers/huggingface/ | HuggingFace · Cloudflare AI Gateway docs Skip to content Cloudflare Docs Search Docs Directory APIs SDKs Help Log in Select theme Dark Light Auto AI Gateway No results found. Try a different search term, or use our global search . Overview Getting started Using AI Gateway Unified API (OpenAI compat) Provider Native Workers AI Amazon Bedrock Anthropic Azure OpenAI Baseten Cartesia Cerebras Cohere Deepgram DeepSeek ElevenLabs Fal AI Google AI Studio Google Vertex AI Groq HuggingFace Ideogram Mistral AI OpenAI OpenRouter Parallel Perplexity Replicate xAI WebSockets API Beta Overview Realtime WebSockets API Non-realtime WebSockets API Features Overview Unified Billing Caching Rate limiting Dynamic routing Beta Overview Using a dynamic route JSON Configuration Data Loss Prevention (DLP) Beta Overview Set up Data Loss Prevention (DLP) Guardrails Beta Overview Set up Guardrails Supported model types Usage considerations Configuration BYOK (Store Keys) Beta Custom costs Custom Providers Beta Manage gateways Request handling Authenticated Gateway Observability Costs Custom metadata Analytics Logging Overview Workers Logpush Integrations Vercel AI SDK Agents ↗ AI Gateway Binding Methods Workers AI Tutorials Platform Overview Limits Pricing Audit logs Changelog Header Glossary REST API reference ↗ API MCP server ↗ MCP AI Assistant ↗ Architectures LLM resources llms.txt prompt.txt AI Gateway llms-full.txt Developer Platform llms-full.txt GitHub X.com YouTube Select theme Dark Light Auto On this page Overview Endpoint URL structure Prerequisites Examples cURL Use HuggingFace.js library with JavaScript On this page Overview Endpoint URL structure Prerequisites Examples cURL Use HuggingFace.js library with JavaScript Was this helpful? Edit Issue Directory … AI Gateway Using AI Gateway Provider Native HuggingFace Copy page HuggingFace HuggingFace ↗ helps users build, deploy and train machine learning models. Endpoint https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/huggingface URL structure When making requests to HuggingFace Inference API, replace https://api-inference.huggingface.co/models/ in the URL you're currently using with https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/huggingface . Note that the model you're trying to access should come right after, for example https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/huggingface/bigcode/starcoder . Prerequisites When making requests to HuggingFace, ensure you have the following: Your AI Gateway Account ID. Your AI Gateway gateway name. An active HuggingFace API token. The name of the HuggingFace model you want to use. Examples cURL Request curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/huggingface/bigcode/starcoder \ --header 'Authorization: Bearer {hf_api_token}' \ --header 'Content-Type: application/json' \ --data '{ "inputs": "console.log" }' Use HuggingFace.js library with JavaScript If you are using the HuggingFace.js library, you can set your inference endpoint like this: JavaScript import { HfInferenceEndpoint } from "@huggingface/inference" ; const accountId = "{account_id}" ; const gatewayId = "{gateway_id}" ; const model = "gpt2" ; const baseURL = `https://gateway.ai.cloudflare.com/v1/ ${ accountId } / ${ gatewayId } /huggingface/ ${ model } ` ; const apiToken = env . HF_API_TOKEN ; const hf = new HfInferenceEndpoint ( baseURL , apiToken ) ; Was this helpful? Edit page Last updated: Nov 24, 2025 Previous Groq Next Ideogram Resources API New to Cloudflare? Directory Sponsorships Open Source Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Speed Test Is BGP Safe Yet? RPKI Toolkit Certificate Transparency Community X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings | 2026-01-13T09:30:12 |
http://ads-developers.googleblog.com/2021/04/announcing-v2-of-adsense-management-api.html | Google Ads Developer Blog: Announcing v2 of the AdSense Management API Ads Developer Blog The official blog for information about the Google Ads, Google Ad Manager, Google Mobile Ads SDKs for AdMob and IMA SDKs, and other Google Advertising Platform developer tools. Announcing v2 of the AdSense Management API Monday, April 19, 2021 We're happy to announce that v2 of the AdSense Management API is available starting today. This version adds the ability to fetch the status of sites on your account and aligns the AdSense Management API with current Google API standards . At this time, v1.4 of the AdSense Management API is now deprecated, and it will sunset on October 12, 2021 . Notable changes from v1.4 to v2 include the following: All deprecated methods in v1.4 have been removed in v2. This includes resource methods that did not specify an AdSense account. Resources are now identified by a name field. For example, an AdClient’s name would be “ accounts/{accountId}/adclients/{adClientId} ”. With v2, AdSense Management API reporting data now aligns with the AdSense UI. This means that AdMob and YouTube properties are no longer supported. If you need to continue to fetch AdMob data programmatically, please migrate to the AdMob API . Additionally, the AdSense Management API will only support report data going back 3 years. For a full list of changes, see the release notes . As always, feel free to reach out to us on the AdSense API forum with any API-related questions. - Donovan McMurray , AdSense API Team Google Labels: adsense_api , release , sunset    Labels  account_management ad_clicks ad_customizers ad_exchange ad_exchange_buyer ad_exchange_optimization-series ad_exchange_rest ad_exchange_rtb ad_exchange_seller ad_exchange_soap ad_extensions ad_inspector ad_manager ad_manager_api ad_manager_api_v201805 ad_manager_api_v201808 ad_manager_api_v201811 ad_manager_api_v201902 ad_manager_api_v201905 ad_manager_api_v201908 ad_manager_api_v201911 ad_manager_api_v202002 ad_manager_api_v202005 ad_manager_api_v202008 ad_manager_api_v202011 ad_manager_api_v202102 ad_manager_api_v202105 ad_manager_api_v202108 ad_manager_api_v202111 ad_manager_api_v202202 ad_manager_api_v202205 ad_manager_api_v202208 ad_manager_api_v202211 ad_manager_api_v202302 ad_manager_api_v202305 ad_manager_api_v202308 ad_manager_api_v202311 ad_manager_api_v202402 ad_manager_api_v202405 ad_manager_api_v202408 ad_manager_api_v202411 ad_manager_api_v202502 ad_manager_api_v202511 ad_param ad_speed adexchangebuyer AdGroup AdGroupAd admanager_api admob admob_api admob_api_v1 admob_mediation admob_sdk admob_v4.3.1 admob_v5.0.5 admob_v6.0.1 ads adsense adsense_api adsense_host_api adsense_host_api_v3 adsense_management_api adsense_management_api_v1 adsense_management_api_v1.1 adsense_management_api_v1.2 adsense_management_api_v1.3 adsense_management_api_v1.4 advanced_apis adwhirl adwhirl_v3.1.1 adwords AdWords Scripts adwords_AdGroupCriterionService adwords_api adwords_api_v201302 adwords_api_v201306 adwords_api_v201309 adwords_api_v201402 adwords_api_v201406 adwords_api_v201409 adwords_api_v201502 adwords_api_v201506 adwords_api_v201509 adwords_api_v201601 adwords_api_v201603 adwords_api_v201605 adwords_api_v201607 adwords_api_v201609 adwords_api_v201702 adwords_api_v201705 adwords_api_v201708 adwords_api_v201710 adwords_api_v201802 adwords_api_v201806 adwords_api_v201809 adwords_api_workshops adwords_BatchJobService adwords_CampaignService adwords_CreateAccountService adwords_for_video adwords_ManagedCustomerService adwords_MutateJobService adwords_ReportDefinitionService adwords_scripts adwords_v201109 adwords_v201206 adwords_v201209 adwords_v201302 adwords_v201306 adwords_v201309 adwords_v201601 adwords_v201605 adwords_v201607 adwords_v201609 adwords_v201702 adwords_v201802 adwords_v201806 adwords_v201809 ai_tools alerting amp analytics analyticsapi android android_layout animation announcement annual developer survey api app_engine asset_group asset_group_listing_group_filter asset_group_signal assets attribution_reporting_api audiences authentication authorization authorized_buyer authorized_buyers aw_reporting awql batch_processing beacon_api best_practices beta bid_manager_api bid_modifiers bidding billing brand guidelines brand_guidelines budget_order_service budgets builders bulk_upload c# caf_sdk call_extensions call_metrics call_only call_tracking call-only callout_extensions campaign campaign_management campaign_manager_360 CampaignCriterion case_study cast certificates certification change_history chart_tools chrome chromecast click click_tracking click_type click-to-download clicks client_libraries client_library cm360 code_examples common_questions conference content content_api conversion conversions ConversionTrackerService converted_clicks creative_platforms creatives custom_fields customer_match DAI dart data_manager_api dbm_api debugging decorators deprecation developer dfa_ad_service dfa_api dfa_api_v118 dfa_creative_service dfa_reporting_api dfa_site_service dfa_v1.16 dfa_v1.17 dfa_v1.18 dfa_v1.19 dfa_v1.20 dfp dfp_api dfp_appengine dfp_creatives dfp_inventory dfp_mobile dfp_pql dfp_reports dfp_sales dfp_teams dfp_v201111 dfp_v201201 dfp_v201203 dfp_v201204 dfp_v201206 dfp_v201208 dfp_v201211 dfp_v201302 dfp_v201308 dfp_v201608 dfp_v201711 discord display display_network display_select display_smart_campaign docs documentation dotnet doubleclick DoubleClick_Rich_Media doubleclick_studio drafts dsa dv360 dv360_api dynamic_creative enhanced_campaigns entity_read_files erf error handling eta examples excluded_placement_lists exoplayer expanded_text_ads experiment experiments faq feedback feeds firebase flash flash_sdk floc flutter forecast_service games gaql gclid gdc gdl geo_targets geotargeting gmail_ads gmail_image_ads gmail_multi_product_ads gmail_single_promotion_ads GMF gmp golang google_ads google_ads_api google_ads_api_migration_workshop google_ads_api_v0 google_ads_api_v0_1 google_ads_api_v0_3 google_ads_api_v0_4 google_ads_api_v0_5 google_ads_api_v0_6 google_ads_api_v0_7 google_ads_api_v1_0 google_ads_api_v1_1 google_ads_api_v1_2 google_ads_api_v1_3 google_ads_api_v2_1 google_ads_api_v3_0 google_ads_api_v3_1 google_ads_api_v4 google_ads_api_v5 google_ads_api_v6 google_ads_scripts google_ads_solutions google_apis google_apps_script google_drive google_play_services google_plus gpt gRPC guide guides hangout hotel_ads hotel_campaigns html5 html5_ads https i18n ids ima_android ima_flash ima_html5 ima_ios ima_roku ima_sdk image image_ads image_optimization implementation impression_share interstitial interview io13 iOS iOS9 java_app_engine java_dart_api jdbc keyword_optimizer keywords kotlin labels limits line_item linq listing_groups location_extensions location_feeds LocationExtensionOperand LocationGroups logging manager_accounts maps_api marketplace maximize mcc MCP media media_bundle mediation_test_suite merchant_api migration mobile mobile_ads mobile_ads_garage mobile_ads_sdk mobile_sites mobile_speed mobile_targeting mobile_ux monitoring native native_ads_express new_features oath2 oauth oauth2 offline_conversions OfflineConversionFeedService open_source openrtb optimization pal Performance Max performance_max performance_max_api_workshop php PLA placements PMax policy policy_violation PQL price_extension privacy privacy_sandbox product_listing_ads proguard promotion_line publisher_ads_audits python qa quality_score query_builder_blog_series query_language quota rate_limiter rate_sheet RateExceededError realtime_bidding realtime_bidding_api realtime_bidding_protocol realtimebidding recommendations referer release remarketing reporting reports responsive_ads rest rewarded_video rmf ruby sa360 sandbox scripts sdf sdkless search search audience search terms search_audience search_network search_theme selector sendbeacon service_accounts SGAI shared_negative_keywords shopping simulations sitelinks smart snds spend ssl StepInsideAdWords success_stories suggested_ad_units sunset survey swift swift_package_manager swiftui target target_cpa targeting template_ads terms test_accounts test_network testing text_ads text_asset_automation tools trials turtledove ui unity update updates upgrade upgraded_urls v201509 vast3 vcpm video viewable-cpm webinar workshop workshops wp8 xml youtube  Archive      2026 Jan     2025 Dec Nov Oct Sep Aug Jul Jun May Apr Mar Feb Jan     2024 Dec Nov Oct Sep Aug Jul Jun May Apr Mar Feb Jan     2023 Dec Nov Oct Sep Aug Jul Jun May Apr Mar Feb Jan     2022 Dec Nov Oct Sep Aug Jul Jun May Apr Mar Feb Jan     2021 Dec Nov Oct Sep Aug Jul Jun May Apr Mar Feb Jan     2020 Dec Nov Oct Sep Aug Jul Jun May Apr Mar Feb Jan     2019 Dec Nov Oct Sep Aug Jul Jun May Apr Mar Feb Jan     2018 Dec Nov Oct Sep Aug Jul Jun May Apr Mar Feb Jan     2017 Dec Nov Oct Sep Aug Jul Jun May Apr Mar Feb Jan     2016 Dec Nov Oct Sep Aug Jul Jun May Apr Mar Feb Jan     2015 Dec Nov Oct Sep Aug Jul Jun May Apr Mar Feb Jan     2014 Dec Nov Oct Sep Aug Jul Jun May Apr Mar Feb Jan     2013 Dec Nov Oct Sep Aug Jul Jun May Apr Mar Feb Jan     2012 Dec Nov Oct Sep Aug Jul Jun May Apr Mar Feb Jan     2011 Dec Nov Give us feedback in our developer product forums: Google Ads API Google Ads scripts Google Ad Manager API DCM API Google Mobile Ads SDK Google AdMob API Google Interactive Media Ads SDK Google Content API for Shopping Authorized Buyers API Google Privacy Terms | 2026-01-13T09:30:12 |
https://developers.google.com/admob/api/reference/rest/v1beta/accounts.adUnits.adUnitMappings | REST Resource: accounts.adUnits.adUnitMappings | AdMob API | Google for Developers Skip to main content AdMob API / English Deutsch Español Español – América Latina Français Indonesia Italiano Polski Português – Brasil Tiếng Việt Türkçe Русский עברית العربيّة فارسی हिंदी বাংলা ภาษาไทย 中文 – 简体 中文 – 繁體 日本語 한국어 Sign in AdMob Guides Reference Libraries & Examples Support AdMob API AdMob Guides Reference Libraries & Examples Support Release notes AdMob API v1 REST Resources accounts Overview get list accounts.adUnits Overview list accounts.apps Overview list accounts.mediationReport Overview generate accounts.networkReport Overview generate Types DateRange LocalizationSettings ReportFooter ReportHeader ReportRow SortOrder StringList v1beta REST Resources accounts Overview get list accounts.adSources Overview list accounts.adSources.adapters Overview list accounts.adUnitMappings Overview batchCreate accounts.adUnits Overview create list accounts.adUnits.adUnitMappings Overview create list accounts.apps Overview create list accounts.campaignReport Overview generate accounts.mediationGroups Overview create list patch accounts.mediationGroups.mediationAbExperiments Overview create stop accounts.mediationReport Overview generate accounts.networkReport Overview generate Types DateRange LocalizationSettings MediationGroupLine ReportFooter ReportHeader ReportRow SortOrder StringList API dictionary Ad sources Adapters Home Products AdMob API Reference REST Resource: accounts.adUnits.adUnitMappings Stay organized with collections Save and categorize content based on your preferences. Page Summary outlined_flag An AdUnitMapping defines settings to map an AdMob ad unit to a third-party ad unit. The AdUnitMapping resource includes fields such as name, adapterId, state, adUnitConfigurations, and displayName. The State of an ad unit mapping can be either STATE_UNSPECIFIED or ENABLED , indicating if it's active. Available methods for AdUnitMapping include create to add a new mapping and list to view existing ones. Resource: AdUnitMapping JSON representation State Methods Resource: AdUnitMapping Settings to map an AdMob ad unit to a 3rd party ad unit. JSON representation { "name" : string , "adapterId" : string , "state" : enum ( State ) , "adUnitConfigurations" : { string : string , ... } , "displayName" : string } Fields name string Resource name of this ad unit mapping. Format is: accounts/{publisherId}/adUnits/{ad_unit_id_fragment}/adUnitMappings/{adUnitMappingId} Example: accounts/pub-1234567890123456/adUnits/0123456789/adUnitMappings/987654321 adapterId string ( int64 format) The ID of mediation ad source adapter used by this ad unit mapping. The adapter determines the information needed in the ad_network_settings. state enum ( State ) Output only. The status of this ad unit mapping. adUnitConfigurations map (key: string ( int64 format), value: string) Settings for the specified ad unit to make an ad request to 3rd party ad network. Key-value pairs with values set by the user for the keys requested by the ad network. Please see https://support.google.com/admob/answer/3245073 for details on how to configure the network settings. An object containing a list of "key": value pairs. Example: { "name": "wrench", "mass": "1.3kg", "count": "3" } . displayName string Optional. The display name of this ad unit mapping instance. State Status of the ad unit mapping. Newly created ad unit mapping is set to ENABLED. Output only. Enums STATE_UNSPECIFIED The default value. ENABLED The ad unit mapping is active and used to serve ads or collecting stats. Methods create Create an ad unit mapping under the specific AdMob account and ad unit. list List ad unit mappings under the specified AdMob account and ad unit. Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License , and code samples are licensed under the Apache 2.0 License . For details, see the Google Developers Site Policies . Java is a registered trademark of Oracle and/or its affiliates. Last updated 2025-08-20 UTC. [[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-20 UTC."],[],["AdUnitMapping resources connect AdMob ad units to third-party ad units. Key actions involve creating and listing these mappings. Each mapping includes a name, adapter ID, state (like ENABLED), and ad unit configurations—settings for the third-party ad network. The `displayName` is an optional name for the mapping. The `State` field indicates the mapping's status. `adUnitConfigurations` contains key-value pairs for the third party settings.\n"]] Product info Usage limits Pricing Terms of Service Programs Google Developer Program Google Developer Groups Google Developer Experts Accelerators Google Cloud & NVIDIA Developer consoles Google API Console Google Cloud Platform Console Google Play Console Firebase Console Actions on Google Console Cast SDK Developer Console Chrome Web Store Dashboard Google Home Developer Console Android Chrome Firebase Google Cloud Platform Google AI All products Terms Privacy Manage cookies English Deutsch Español Español – América Latina Français Indonesia Italiano Polski Português – Brasil Tiếng Việt Türkçe Русский עברית العربيّة فارسی हिंदी বাংলা ภาษาไทย 中文 – 简体 中文 – 繁體 日本語 한국어 | 2026-01-13T09:30:12 |
https://developers.cloudflare.com/ai-gateway/features/guardrails/supported-model-types/ | Supported model types · Cloudflare AI Gateway docs Skip to content Cloudflare Docs Search Docs Directory APIs SDKs Help Log in Select theme Dark Light Auto AI Gateway No results found. Try a different search term, or use our global search . Overview Getting started Using AI Gateway Unified API (OpenAI compat) Provider Native Workers AI Amazon Bedrock Anthropic Azure OpenAI Baseten Cartesia Cerebras Cohere Deepgram DeepSeek ElevenLabs Fal AI Google AI Studio Google Vertex AI Groq HuggingFace Ideogram Mistral AI OpenAI OpenRouter Parallel Perplexity Replicate xAI WebSockets API Beta Overview Realtime WebSockets API Non-realtime WebSockets API Features Overview Unified Billing Caching Rate limiting Dynamic routing Beta Overview Using a dynamic route JSON Configuration Data Loss Prevention (DLP) Beta Overview Set up Data Loss Prevention (DLP) Guardrails Beta Overview Set up Guardrails Supported model types Usage considerations Configuration BYOK (Store Keys) Beta Custom costs Custom Providers Beta Manage gateways Request handling Authenticated Gateway Observability Costs Custom metadata Analytics Logging Overview Workers Logpush Integrations Vercel AI SDK Agents ↗ AI Gateway Binding Methods Workers AI Tutorials Platform Overview Limits Pricing Audit logs Changelog Header Glossary REST API reference ↗ API MCP server ↗ MCP AI Assistant ↗ Architectures LLM resources llms.txt prompt.txt AI Gateway llms-full.txt Developer Platform llms-full.txt GitHub X.com YouTube Select theme Dark Light Auto On this page Overview On this page Overview Was this helpful? Edit Issue Directory … AI Gateway Features Guardrails Supported model types Copy page Supported model types AI Gateway's Guardrails detects the type of AI model being used and applies safety checks accordingly: Text generation models : Both prompts and responses are evaluated. Embedding models : Only the prompt is evaluated, as the response consists of numerical embeddings, which are not meaningful for moderation. Unknown models : If the model type cannot be determined, only the prompt is evaluated, while the response bypass Guardrails. Note Guardrails does not yet support streaming responses. Support for streaming is planned for a future update. Was this helpful? Edit page Last updated: Aug 19, 2025 Previous Set up Guardrails Next Usage considerations Resources API New to Cloudflare? Directory Sponsorships Open Source Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Speed Test Is BGP Safe Yet? RPKI Toolkit Certificate Transparency Community X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings | 2026-01-13T09:30:12 |
https://developers.cloudflare.com/ai-gateway/usage/providers/ideogram/ | Ideogram · Cloudflare AI Gateway docs Skip to content Cloudflare Docs Search Docs Directory APIs SDKs Help Log in Select theme Dark Light Auto AI Gateway No results found. Try a different search term, or use our global search . Overview Getting started Using AI Gateway Unified API (OpenAI compat) Provider Native Workers AI Amazon Bedrock Anthropic Azure OpenAI Baseten Cartesia Cerebras Cohere Deepgram DeepSeek ElevenLabs Fal AI Google AI Studio Google Vertex AI Groq HuggingFace Ideogram Mistral AI OpenAI OpenRouter Parallel Perplexity Replicate xAI WebSockets API Beta Overview Realtime WebSockets API Non-realtime WebSockets API Features Overview Unified Billing Caching Rate limiting Dynamic routing Beta Overview Using a dynamic route JSON Configuration Data Loss Prevention (DLP) Beta Overview Set up Data Loss Prevention (DLP) Guardrails Beta Overview Set up Guardrails Supported model types Usage considerations Configuration BYOK (Store Keys) Beta Custom costs Custom Providers Beta Manage gateways Request handling Authenticated Gateway Observability Costs Custom metadata Analytics Logging Overview Workers Logpush Integrations Vercel AI SDK Agents ↗ AI Gateway Binding Methods Workers AI Tutorials Platform Overview Limits Pricing Audit logs Changelog Header Glossary REST API reference ↗ API MCP server ↗ MCP AI Assistant ↗ Architectures LLM resources llms.txt prompt.txt AI Gateway llms-full.txt Developer Platform llms-full.txt GitHub X.com YouTube Select theme Dark Light Auto On this page Overview Endpoint Prerequisites Examples cURL Use with JavaScript On this page Overview Endpoint Prerequisites Examples cURL Use with JavaScript Was this helpful? Edit Issue Directory … AI Gateway Using AI Gateway Provider Native Ideogram Copy page Ideogram Ideogram ↗ provides advanced text-to-image generation models with exceptional text rendering capabilities and visual quality. Endpoint https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/ideogram Prerequisites When making requests to Ideogram, ensure you have the following: Your AI Gateway Account ID. Your AI Gateway gateway name. An active Ideogram API key. The name of the Ideogram model you want to use (e.g., V_3 ). Examples cURL Example fetch request curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/ideogram/v1/ideogram-v3/generate \ --header 'Api-Key: {ideogram_api_key}' \ --header 'Content-Type: application/json' \ --data '{ "prompt": "A serene landscape with mountains and a lake at sunset", "model": "V_3" }' Use with JavaScript JavaScript const accountId = "{account_id}" ; const gatewayId = "{gateway_id}" ; const ideogramApiKey = "{ideogram_api_key}" ; const baseURL = `https://gateway.ai.cloudflare.com/v1/ ${ accountId } / ${ gatewayId } /ideogram` ; const response = await fetch ( ` ${ baseURL } /v1/ideogram-v3/generate` , { method : "POST" , headers : { "Api-Key" : ideogramApiKey , "Content-Type" : "application/json" , }, body : JSON . stringify ( { prompt : "A serene landscape with mountains and a lake at sunset" , model : "V_3" , } ) , } ) ; const result = await response . json () ; console . log ( result ) ; Was this helpful? Edit page Last updated: Nov 25, 2025 Previous HuggingFace Next Mistral AI Resources API New to Cloudflare? Directory Sponsorships Open Source Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Speed Test Is BGP Safe Yet? RPKI Toolkit Certificate Transparency Community X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings | 2026-01-13T09:30:12 |
https://developers.cloudflare.com/ai-gateway/usage/providers/azureopenai/ | Azure OpenAI · Cloudflare AI Gateway docs Skip to content Cloudflare Docs Search Docs Directory APIs SDKs Help Log in Select theme Dark Light Auto AI Gateway No results found. Try a different search term, or use our global search . Overview Getting started Using AI Gateway Unified API (OpenAI compat) Provider Native Workers AI Amazon Bedrock Anthropic Azure OpenAI Baseten Cartesia Cerebras Cohere Deepgram DeepSeek ElevenLabs Fal AI Google AI Studio Google Vertex AI Groq HuggingFace Ideogram Mistral AI OpenAI OpenRouter Parallel Perplexity Replicate xAI WebSockets API Beta Overview Realtime WebSockets API Non-realtime WebSockets API Features Overview Unified Billing Caching Rate limiting Dynamic routing Beta Overview Using a dynamic route JSON Configuration Data Loss Prevention (DLP) Beta Overview Set up Data Loss Prevention (DLP) Guardrails Beta Overview Set up Guardrails Supported model types Usage considerations Configuration BYOK (Store Keys) Beta Custom costs Custom Providers Beta Manage gateways Request handling Authenticated Gateway Observability Costs Custom metadata Analytics Logging Overview Workers Logpush Integrations Vercel AI SDK Agents ↗ AI Gateway Binding Methods Workers AI Tutorials Platform Overview Limits Pricing Audit logs Changelog Header Glossary REST API reference ↗ API MCP server ↗ MCP AI Assistant ↗ Architectures LLM resources llms.txt prompt.txt AI Gateway llms-full.txt Developer Platform llms-full.txt GitHub X.com YouTube Select theme Dark Light Auto On this page Overview Endpoint Prerequisites URL structure Examples cURL Use openai JavaScript SDK On this page Overview Endpoint Prerequisites URL structure Examples cURL Use openai JavaScript SDK Was this helpful? Edit Issue Directory … AI Gateway Using AI Gateway Provider Native Azure OpenAI Copy page Azure OpenAI Azure OpenAI ↗ allows you apply natural language algorithms on your data. Endpoint https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/azure-openai/{resource_name}/{deployment_name} Prerequisites When making requests to Azure OpenAI, you will need: AI Gateway account ID AI Gateway gateway name Azure OpenAI API key Azure OpenAI resource name Azure OpenAI deployment name (aka model name) URL structure Your new base URL will use the data above in this structure: https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/azure-openai/{resource_name}/{deployment_name} . Then, you can append your endpoint and api-version at the end of the base URL, like .../chat/completions?api-version=2023-05-15 . Examples cURL Example fetch request curl 'https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway}/azure-openai/{resource_name}/{deployment_name}/chat/completions?api-version=2023-05-15' \ --header 'Content-Type: application/json' \ --header 'api-key: {azure_api_key}' \ --data '{ "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] }' Use openai JavaScript SDK JavaScript import { AzureOpenAI } from "openai" ; const azure_openai = new AzureOpenAI ( { apiKey : "{azure_api_key}" , baseURL : `https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway}/azure-openai/{resource_name}/` , apiVersion : "2023-05-15" , defaultHeaders : { "cf-aig-authorization" : "{cf-api-token}" }, // if authenticated } ) ; const result = await azure_openai . chat . completions . create ( { model : '{deployment_name}' , messages : [ { role : "user" , content : "Hello" } ] , } ) ; Was this helpful? Edit page Last updated: Dec 16, 2025 Previous Anthropic Next Baseten Resources API New to Cloudflare? Directory Sponsorships Open Source Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Speed Test Is BGP Safe Yet? RPKI Toolkit Certificate Transparency Community X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings | 2026-01-13T09:30:12 |
https://developers.cloudflare.com/ai-gateway/configuration/authentication/ | Authenticated Gateway · Cloudflare AI Gateway docs Skip to content Cloudflare Docs Search Docs Directory APIs SDKs Help Log in Select theme Dark Light Auto AI Gateway No results found. Try a different search term, or use our global search . Overview Getting started Using AI Gateway Unified API (OpenAI compat) Provider Native Workers AI Amazon Bedrock Anthropic Azure OpenAI Baseten Cartesia Cerebras Cohere Deepgram DeepSeek ElevenLabs Fal AI Google AI Studio Google Vertex AI Groq HuggingFace Ideogram Mistral AI OpenAI OpenRouter Parallel Perplexity Replicate xAI WebSockets API Beta Overview Realtime WebSockets API Non-realtime WebSockets API Features Overview Unified Billing Caching Rate limiting Dynamic routing Beta Overview Using a dynamic route JSON Configuration Data Loss Prevention (DLP) Beta Overview Set up Data Loss Prevention (DLP) Guardrails Beta Overview Set up Guardrails Supported model types Usage considerations Configuration BYOK (Store Keys) Beta Custom costs Custom Providers Beta Manage gateways Request handling Authenticated Gateway Observability Costs Custom metadata Analytics Logging Overview Workers Logpush Integrations Vercel AI SDK Agents ↗ AI Gateway Binding Methods Workers AI Tutorials Platform Overview Limits Pricing Audit logs Changelog Header Glossary REST API reference ↗ API MCP server ↗ MCP AI Assistant ↗ Architectures LLM resources llms.txt prompt.txt AI Gateway llms-full.txt Developer Platform llms-full.txt GitHub X.com YouTube Select theme Dark Light Auto On this page Overview Setting up Authenticated Gateway using the Dashboard Example requests with OpenAI Example requests with the Vercel AI SDK Expected behavior On this page Overview Setting up Authenticated Gateway using the Dashboard Example requests with OpenAI Example requests with the Vercel AI SDK Expected behavior Was this helpful? Edit Issue Directory … AI Gateway Configuration Authenticated Gateway Copy page Authenticated Gateway Using an Authenticated Gateway in AI Gateway adds security by requiring a valid authorization token for each request. This feature is especially useful when storing logs, as it prevents unauthorized access and protects against invalid requests that can inflate log storage usage and make it harder to find the data you need. With Authenticated Gateway enabled, only requests with the correct token are processed. Note We recommend enabling Authenticated Gateway when opting to store logs with AI Gateway. If Authenticated Gateway is enabled but a request does not include the required cf-aig-authorization header, the request will fail. This setting ensures that only verified requests pass through the gateway. To bypass the need for the cf-aig-authorization header, make sure to disable Authenticated Gateway. Setting up Authenticated Gateway using the Dashboard Go to the Settings for the specific gateway you want to enable authentication for. Select Create authentication token to generate a custom token with the required Run permissions. Be sure to securely save this token, as it will not be displayed again. Include the cf-aig-authorization header with your API token in each request for this gateway. Return to the settings page and toggle on Authenticated Gateway. Example requests with OpenAI Terminal window curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/openai/chat/completions \ --header 'cf-aig-authorization: Bearer {CF_AIG_TOKEN}' \ --header 'Authorization: Bearer OPENAI_TOKEN' \ --header 'Content-Type: application/json' \ --data '{"model": "gpt-5-mini", "messages": [{"role": "user", "content": "What is Cloudflare?"}]}' Using the OpenAI SDK: JavaScript import OpenAI from "openai" ; const openai = new OpenAI ( { apiKey : process . env . OPENAI_API_KEY , baseURL : "https://gateway.ai.cloudflare.com/v1/account-id/gateway/openai" , defaultHeaders : { "cf-aig-authorization" : `Bearer {token}` , }, } ) ; Example requests with the Vercel AI SDK JavaScript import { createOpenAI } from "@ai-sdk/openai" ; const openai = createOpenAI ( { baseURL : "https://gateway.ai.cloudflare.com/v1/account-id/gateway/openai" , headers : { "cf-aig-authorization" : `Bearer {token}` , }, } ) ; Expected behavior Note When an AI Gateway is accessed from a Cloudflare Worker using a binding , the cf-aig-authorization header does not need to be manually included. Requests made through bindings are pre-authenticated within the associated Cloudflare account. The following table outlines gateway behavior based on the authentication settings and header status: Authentication Setting Header Info Gateway State Response On Header present Authenticated gateway Request succeeds On No header Error Request fails due to missing authorization Off Header present Unauthenticated gateway Request succeeds Off No header Unauthenticated gateway Request succeeds Was this helpful? Edit page Last updated: Oct 7, 2025 Previous Request handling Next Costs Resources API New to Cloudflare? Directory Sponsorships Open Source Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Speed Test Is BGP Safe Yet? RPKI Toolkit Certificate Transparency Community X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings | 2026-01-13T09:30:12 |
https://developers.cloudflare.com/ai-gateway/usage/providers/elevenlabs/ | ElevenLabs · Cloudflare AI Gateway docs Skip to content Cloudflare Docs Search Docs Directory APIs SDKs Help Log in Select theme Dark Light Auto AI Gateway No results found. Try a different search term, or use our global search . Overview Getting started Using AI Gateway Unified API (OpenAI compat) Provider Native Workers AI Amazon Bedrock Anthropic Azure OpenAI Baseten Cartesia Cerebras Cohere Deepgram DeepSeek ElevenLabs Fal AI Google AI Studio Google Vertex AI Groq HuggingFace Ideogram Mistral AI OpenAI OpenRouter Parallel Perplexity Replicate xAI WebSockets API Beta Overview Realtime WebSockets API Non-realtime WebSockets API Features Overview Unified Billing Caching Rate limiting Dynamic routing Beta Overview Using a dynamic route JSON Configuration Data Loss Prevention (DLP) Beta Overview Set up Data Loss Prevention (DLP) Guardrails Beta Overview Set up Guardrails Supported model types Usage considerations Configuration BYOK (Store Keys) Beta Custom costs Custom Providers Beta Manage gateways Request handling Authenticated Gateway Observability Costs Custom metadata Analytics Logging Overview Workers Logpush Integrations Vercel AI SDK Agents ↗ AI Gateway Binding Methods Workers AI Tutorials Platform Overview Limits Pricing Audit logs Changelog Header Glossary REST API reference ↗ API MCP server ↗ MCP AI Assistant ↗ Architectures LLM resources llms.txt prompt.txt AI Gateway llms-full.txt Developer Platform llms-full.txt GitHub X.com YouTube Select theme Dark Light Auto On this page Overview Endpoint Prerequisites Example cURL On this page Overview Endpoint Prerequisites Example cURL Was this helpful? Edit Issue Directory … AI Gateway Using AI Gateway Provider Native ElevenLabs Copy page ElevenLabs ElevenLabs ↗ offers advanced text-to-speech services, enabling high-quality voice synthesis in multiple languages. Endpoint https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/elevenlabs Prerequisites When making requests to ElevenLabs, ensure you have the following: Your AI Gateway Account ID. Your AI Gateway gateway name. An active ElevenLabs API token. The model ID of the ElevenLabs voice model you want to use. Example cURL Request curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/elevenlabs/v1/text-to-speech/JBFqnCBsd6RMkjVDRZzb?output_format=mp3_44100_128 \ --header 'Content-Type: application/json' \ --header 'xi-api-key: {elevenlabs_api_token}' \ --data '{ "text": "Welcome to Cloudflare - AI Gateway!", "model_id": "eleven_multilingual_v2" }' Was this helpful? Edit page Last updated: Aug 19, 2025 Previous DeepSeek Next Fal AI Resources API New to Cloudflare? Directory Sponsorships Open Source Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Speed Test Is BGP Safe Yet? RPKI Toolkit Certificate Transparency Community X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings | 2026-01-13T09:30:12 |
https://www.imgix.com/jp | Imgix: AI搭載の画像最適化CDN Imgix uses cookies to maintain user sessions and track marketing efforts. By continuing to use our website, you agree to our use of cookies for these purposes. Read our Privacy Policy. Try Imgix for Free Get 30 days and 100 credits to transform, optimize, and deliver high-performance visuals. No credit card required. Start My Free Trial Smarter video creation is here! Explore image-to-video, automated previews, and smart cropping. Learn More → 導入事例 ソリューション より高速なウェブページ 解き放たれた創造性 開発の簡略化 eコマース向けソリューション 代理店向けソリューション メディア向けソリューション 自動車向けソリューション 不動産向けソリューション 製品 セットアップガイド ドキュメンテーション APIリファレンスガイド ライブラリとプラグイン Imgixの始め方 -AI トランスフォーメーション -資産管理 -自動画像最適化 -著作権とブランディング -デザインとイメージ変換 -画像編集プラットフォーム -グローバルコンテンツ配信 -ビデオ最適化 -監視ツール チュートリアル Imgix API の使用方法 価格設定 パートナー 会社 ブログ イベント リソース 私たちについて プレス 採用情報 人材を募集しています! その他のリソース ページウェイト Imgixの始め方 連絡を取る お問い合わせ ログイン/サインアップ ja English Japanese Try Imgix for Free Get 30 days and 100 credits to transform, optimize, and deliver high-performance visuals. No credit card required. Start My Free Trial Powering 8B+ images a day for brands like Unsplash, Skims, and Porsche ビジュアルを最適化し、自在に変換し、スケール配信する パフォーマンスを重視するチームのための、完全なビジュアルメディアプラットフォーム。画像・動画の自動圧縮、AIによる高度な変換、そして圧倒的に高速な配信を実現します。 無料で始める ) --> 動画のスマートクロッピング 動画のスマートクロッピング フォーカルポイント・クロッピング フォーカルポイント・クロッピング 1:3 1:1 生成AIによる補完 背景除去 背景除去 自動圧縮 187 kb 16 kb 自動圧縮 Trusted by The Power Behind Every Visual Imgix automates every part of your visual pipeline — from creation to delivery — giving your team speed, consistency, and control at any scale. Automate the Heavy Lifting Endless resizing, exporting, and reformatting slows teams down. Automatically compress, resize, and convert images and videos in real time to keep your visuals optimized with minimal effort. Explore Optimization Create with Intelligence Editing out distractions, replacing backgrounds, or generating on-brand visuals can take hours. Use AI-powered transformations to clean up, enhance, and create content in seconds so your team can stay focused on the creative, not the cleanup. Discover AI Tools Deliver at Global Scale Slow load times and inconsistent delivery kill engagement. Distribute visuals worldwide through a high-performance network that keeps content fast, reliable, and flawless for every viewer. See How Delivery Works 創造性を、もっと自由に 制作を止めないAIツールで、チームのアイデアをすぐに形に。 スマートな ワークフロー 自動化された編集プロセスで制作時間を半分に短縮し、キャンペーンをより早く公開できます。 グローバル 対応 世界中どの市場でも高品質なビジュアルを届ける、グローバルパフォーマンス設計。 高速なページ表示 瞬時に読み込まれる最適化ビジュアルで、ユーザー体験とコンバージョンを向上させます。 Imgixで最適化 すべての導入事例を見る ブログでもっと読む 最新トレンド先取り 画像最適化のヒント、パフォーマンス改善のベストプラクティス、新機能のお知らせをお届けします。 成功!あなたはリストに載っています。 おっと!フォームの送信中に問題が発生しました。 サービスステータス ポリシー ブログ ページウェイト お問い合わせ Contact Us LinkedIn Instagram Facebook X (Twitter) X (Twitter) © 2025 Imgix Imgix による最適化 あなたのイメージパートナー 無料で始める お問い合わせ ログイン | 2026-01-13T09:30:12 |
https://developers.google.com/admob/api/reference/rest/v1/LocalizationSettings | LocalizationSettings | AdMob API | Google for Developers Skip to main content AdMob API / English Deutsch Español Español – América Latina Français Indonesia Italiano Polski Português – Brasil Tiếng Việt Türkçe Русский עברית العربيّة فارسی हिंदी বাংলা ภาษาไทย 中文 – 简体 中文 – 繁體 日本語 한국어 Sign in AdMob Guides Reference Libraries & Examples Support AdMob API AdMob Guides Reference Libraries & Examples Support Release notes AdMob API v1 REST Resources accounts Overview get list accounts.adUnits Overview list accounts.apps Overview list accounts.mediationReport Overview generate accounts.networkReport Overview generate Types DateRange LocalizationSettings ReportFooter ReportHeader ReportRow SortOrder StringList v1beta REST Resources accounts Overview get list accounts.adSources Overview list accounts.adSources.adapters Overview list accounts.adUnitMappings Overview batchCreate accounts.adUnits Overview create list accounts.adUnits.adUnitMappings Overview create list accounts.apps Overview create list accounts.campaignReport Overview generate accounts.mediationGroups Overview create list patch accounts.mediationGroups.mediationAbExperiments Overview create stop accounts.mediationReport Overview generate accounts.networkReport Overview generate Types DateRange LocalizationSettings MediationGroupLine ReportFooter ReportHeader ReportRow SortOrder StringList API dictionary Ad sources Adapters Home Products AdMob API Reference LocalizationSettings Stay organized with collections Save and categorize content based on your preferences. Page Summary outlined_flag Localization settings control the currency and language used in reports. These settings impact how metrics, particularly earning-related ones, are calculated and displayed. The currencyCode and languageCode fields determine these settings, with default values if not specified. JSON representation Localization settings for reports, such as currency and language. It affects how metrics are calculated. JSON representation { "currencyCode" : string , "languageCode" : string } Fields currencyCode string Currency code of the earning related metrics, which is the 3-letter code defined in ISO 4217. The daily average rate is used for the currency conversion. Defaults to the account currency code if unspecified. languageCode string Language used for any localized text, such as some dimension value display labels. The language tag defined in the IETF BCP47. Defaults to 'en-US' if unspecified. Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License , and code samples are licensed under the Apache 2.0 License . For details, see the Google Developers Site Policies . Java is a registered trademark of Oracle and/or its affiliates. Last updated 2025-08-20 UTC. [[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-20 UTC."],[],["The JSON representation defines localization settings for reports, including `currencyCode` and `languageCode`. `currencyCode`, a string using ISO 4217, determines the currency for earnings metrics and defaults to the account currency. `languageCode`, a string using IETF BCP47, dictates the language for localized text and defaults to 'en-US'. These settings impact metric calculations and the display of localized elements within reports.\n"]] Product info Usage limits Pricing Terms of Service Programs Google Developer Program Google Developer Groups Google Developer Experts Accelerators Google Cloud & NVIDIA Developer consoles Google API Console Google Cloud Platform Console Google Play Console Firebase Console Actions on Google Console Cast SDK Developer Console Chrome Web Store Dashboard Google Home Developer Console Android Chrome Firebase Google Cloud Platform Google AI All products Terms Privacy Manage cookies English Deutsch Español Español – América Latina Français Indonesia Italiano Polski Português – Brasil Tiếng Việt Türkçe Русский עברית العربيّة فارسی हिंदी বাংলা ภาษาไทย 中文 – 简体 中文 – 繁體 日本語 한국어 | 2026-01-13T09:30:12 |
https://developer.android.com/games?hl=tr | Android oyunları geliştirme | Android game development | Android Developers Ana içeriğe atla Kaçırmamanız gereken oyunlar Yapay zeka deneyimleri oluşturma Gemini API'leri ve daha fazlasıyla yapay zeka destekli Android uygulamaları geliştirin. Başlama Başlama İlk uygulamanızı oluşturarak başlayın. Eğitim kurslarımızla daha ayrıntılı bilgi edinin veya uygulama geliştirmeyi kendi kendinize öğrenin. Hello world Eğitim kursları Eğitimler Ekipler için Compose Android için Kotlin Google Play ile para kazanma ↗️ Android Geliştirici Doğrulaması Cihaza göre genişletme Kullanıcılarınıza telefondan tablete, kol saatinden kulaklığa kadar her cihazda sorunsuz deneyimler sunan uygulamalar geliştirin. Uyarlanabilir uygulamalar Android XR Wear OS Arabalar için Android Android TV ChromeOS Kategoriye göre oluşturma Google'ın yönlendirici ve kişisel görüşe dayalı rehberliğini takip ederek kullanım alanınıza uygun çözümler geliştirmeyi öğrenin. Oyunlar Kamera ve medya Sosyal ve mesajlaşma Sağlık ve form koruma Verimlilik Kurumsal uygulamalar En son sürümünü edinin Yıl boyunca yeni çıkanları takip edin, önizleme programlarımıza katılın ve geri bildirimlerinizi bizimle paylaşın. Son güncellemeler Deneysel güncellemeler Android Studio önizlemesi Jetpack ve Compose kitaplıkları Wear OS sürümleri Özel Korumalı Alan ↗️ Tasarım ve Planlama Mükemmel deneyimler En iyi kullanıcılarınız için en iyi deneyimleri oluşturun. Daha fazla bilgi Kullanıcı arayüzü tasarımı Android'deki en iyi uygulamaları kullanarak güzel bir kullanıcı arayüzü tasarlayın. Android için tasarım Cep Uyarlanabilir kullanıcı arayüzü XR Kulaklıklar ve XR Gözlükler Yapay Zeka Gözlükleri Widget'lar Wear OS Android TV Arabalar için Android Mimari Güçlü, test edilebilir ve bakımı yapılabilir uygulama mantığı ve hizmetleri tasarlayın. Giriş Kütüphaneler Gezinme Modülerleştirme Test Kotlin Multiplatform Kalite Uygulama kalitesini planlayın ve Play Store yönergelerine uyun. Genel bakış Temel değer Kullanıcı deneyimi Erişilebilirlik Teknik kalite Mükemmel deneyimler Güvenlik Kullanıcıları tehditlere karşı koruyun ve güvenli bir Android deneyimi sağlayın. Genel bakış Gizlilik İzinler Kimlik Sahtekarlığı önleme Geliştirme Android Studio'da Gemini Android geliştirmede yapay zeka geliştirme arkadaşınız. Daha fazla bilgi Android Studio'yu edinme Temel alanlar İhtiyacınız olan özelliklerle ilgili örnekleri ve dokümanları edinin. Örnekler Kullanıcı arayüzleri Arka plan çalışması Veriler ve dosyalar Bağlanabilirlik Tüm temel alanlar ⤵️ Araçlar ve iş akışı Uygulamanızı yazmak ve oluşturmak için IDE'yi kullanın veya kendi işlem hattınızı oluşturun. Kod yazma ve hata ayıklama Proje oluşturma Uygulamanızı test etme Performans Komut satırı araçları Gradle eklentisi API'si Cihaz teknolojisi Form faktörleri için kod yazma Cihazları bağlayın ve verileri paylaşın. Uyarlanabilir kullanıcı arayüzü Wear OS Android XR Android Health Arabalar için Android Android TV Tüm cihazlar ⤵️ Kütüphaneler Tüm ayrıntıları içeren API referans belgelerine göz atın. Android platformu Jetpack kitaplıkları Compose kitaplıkları Google Play Hizmetleri ↗️ Google Play SDK Dizini ↗️ Google Play Play Console Uygulamanızı veya oyununuzu yayınlayın ve Google Play'de işinizi büyütün. Play Console'a git Daha fazla bilgi ↗️ Temel Bilgiler Kullanıcılarla etkileşim kurmayı, uygulamanızdan para kazanmayı ve uygulamanızı güvenli hale getirmeyi öğrenin. Play'de para kazanma Play Integrity Play Politikaları Play Programları ↗️ Games Dev Center Oyun geliştirme ve yayınlama Araçlar, indirilenler ve örnekler Genel bakış Play Asset Delivery Play Games Hizmetleri PC Üzerinde Play Games Tüm Play rehberleri ⤵️ Kütüphaneler Tüm ayrıntıları içeren API referans belgelerine göz atın. Play Özellik Dağıtımı Play uygulama içi güncellemeleri Play uygulama içi yorumları Play Install Referrer Google Play Hizmetleri ↗️ Google Play SDK Dizini ↗️ Tüm Play kitaplıkları ⤵️ Araçlar ve kaynaklar Uygulamanızı yayınlama, tanıtma ve yönetme araçları. Android App Bundle Marka ve pazarlama Play Console API'leri ↗️ Topluluk / English Deutsch Español – América Latina Français Indonesia Italiano Polski Português – Brasil Tiếng Việt Türkçe Русский עברית العربيّة فارسی हिंदी বাংলা ภาษาไทย 中文 – 简体 中文 – 繁體 日本語 한국어 Android Studio Oturum aç Games dev center Genel bakış İndirilenler Örnekler Rehberler Başvuru Kaynakları Topluluk Kaçırmamanız gereken oyunlar Diğer Tasarım ve Planlama Diğer Geliştirme Diğer Google Play Diğer Genel bakış İndirilenler Örnekler Rehberler Başvuru Kaynakları Topluluk Topluluk Android Studio Yapay zeka deneyimleri oluşturma Başlama Başlama Hello world Eğitim kursları Eğitimler Ekipler için Compose Android için Kotlin Google Play ile para kazanma ↗️ Android Geliştirici Doğrulaması Cihaza göre genişletme Uyarlanabilir uygulamalar Android XR Wear OS Arabalar için Android Android TV ChromeOS Kategoriye göre oluşturma Oyunlar Kamera ve medya Sosyal ve mesajlaşma Sağlık ve form koruma Verimlilik Kurumsal uygulamalar En son sürümünü edinin Son güncellemeler Deneysel güncellemeler Android Studio önizlemesi Jetpack ve Compose kitaplıkları Wear OS sürümleri Özel Korumalı Alan ↗️ Mükemmel deneyimler Daha fazla bilgi Kullanıcı arayüzü tasarımı Android için tasarım Cep Uyarlanabilir kullanıcı arayüzü XR Kulaklıklar ve XR Gözlükler Yapay Zeka Gözlükleri Widget'lar Wear OS Android TV Arabalar için Android Mimari Giriş Kütüphaneler Gezinme Modülerleştirme Test Kotlin Multiplatform Kalite Genel bakış Temel değer Kullanıcı deneyimi Erişilebilirlik Teknik kalite Mükemmel deneyimler Güvenlik Genel bakış Gizlilik İzinler Kimlik Sahtekarlığı önleme Android Studio'da Gemini Daha fazla bilgi Android Studio'yu edinme Temel alanlar Örnekler Kullanıcı arayüzleri Arka plan çalışması Veriler ve dosyalar Bağlanabilirlik Tüm temel alanlar ⤵️ Araçlar ve iş akışı Kod yazma ve hata ayıklama Proje oluşturma Uygulamanızı test etme Performans Komut satırı araçları Gradle eklentisi API'si Cihaz teknolojisi Uyarlanabilir kullanıcı arayüzü Wear OS Android XR Android Health Arabalar için Android Android TV Tüm cihazlar ⤵️ Kütüphaneler Android platformu Jetpack kitaplıkları Compose kitaplıkları Google Play Hizmetleri ↗️ Google Play SDK Dizini ↗️ Play Console Play Console'a git Daha fazla bilgi ↗️ Temel Bilgiler Play'de para kazanma Play Integrity Play Politikaları Play Programları ↗️ Games Dev Center Genel bakış Play Asset Delivery Play Games Hizmetleri PC Üzerinde Play Games Tüm Play rehberleri ⤵️ Kütüphaneler Play Özellik Dağıtımı Play uygulama içi güncellemeleri Play uygulama içi yorumları Play Install Referrer Google Play Hizmetleri ↗️ Google Play SDK Dizini ↗️ Tüm Play kitaplıkları ⤵️ Araçlar ve kaynaklar Android App Bundle Marka ve pazarlama Play Console API'leri ↗️ Android Developers Google Play Games dev center Geri bildirim gönderin Koleksiyonlar ile düzeninizi koruyun İçeriği tercihlerinize göre kaydedin ve kategorilere ayırın. Geliştirici merkezi Android Oyunları Geliştirme Merkezi Android'de oyun geliştirmek ve yayınlamak için ihtiyacınız olan her şeyi (araçlar, indirmeler, örnekler, kitaplıklar ve rehberlik) burada bulabilirsiniz. Başlama Yenilikler Blog Google Play Games Level Up programı ile tanışın Google Play Games Level Up, oyuncu deneyimini iyileştirmek ve işletmenizin başarısını artırmak için sunduğumuz yeni bir programdır. Daha Fazla Bilgi GDC 2025'te Öne Çıkan Anlar Android Oyunları: Grafik ve Performans Yükseltmeleri Vulkan ve Android Dinamik Performans Çerçevesi (ADPF) gibi yeni araçların, geliştiricilerin Android ekosistemindeki oyun deneyimlerini iyileştirmesini nasıl kolaylaştırdığını öğrenmek için yayını takip edin. PC Üzerinde Google Play Games: Yeni Özellikler ve Daha Fazla Oyun Oynama Yöntemi PC Üzerinde Google Play Games'in, bu yıl önemli platform yükseltmeleri, genişletilmiş destek ve genel kullanıma sunma sayesinde geliştiricilerin cihazlar arasında erişimlerini genişletmesine nasıl yardımcı olduğunu öğrenmek için yayını takip edin. En yeni videolarımızı inceleyin Öncelikli iş akışları Grafik Performansı ve Kalitesi Yavaş oturumları azaltmak veya grafik kalitesini iyileştirmek için grafik performansını iyileştirin. Daha fazla bilgi Termal ve iş yükü yönetimi ADPF ile termal kısıtlamadan kaynaklanan yavaş oturumları önlemek için termal değişikliklere tepki verin. Daha iyi performans için ADPF, sistemin oyun iş yükündeki değişikliklere tepki vermesine de yardımcı olur. Daha fazla bilgi Çoklu platform ve form faktörleri Çok platformlu destek ve büyük ekranlara yönelik optimizasyonlarla oyununuzun her yerde çalışmasını sağlayın. Daha fazla bilgi Geliştirici hikayeleri Oyun geliştiricileri Android araçlarıyla nasıl başarıya ulaşıyor? Oyunla ilgili diğer hikayeleri göster Öne çıkan kaynaklar Optimize et Android GPU Denetleyicisi (AGI) Bu güçlü grafik profil aracını kullanarak oyununuzun Android cihazlar üzerindeki etkisini analiz edin. Böylece performans sorunlarını ve optimize edilecek alanları belirleyebilirsiniz. Belgeleri oku Yayınlayın Android, ChromeOS ve Windows'a dağıtın Profiller, skor tabloları ve başarılar gibi sosyal ve rekabetçi oyun hizmetleri ekleyin, ardından Android oyununuzu Google Play Store üzerinden dağıtın. Belgeleri oku İndirilenler Tüm araçlarınız tek bir yerde. Örnekler Örnek uygulamaları ve örnek kodu bulun. Eğitimler Oyun geliştirme görevlerini tamamlamak için rehberli, adım adım açıklamalı codelab'leri takip edin. Topluluk kaynakları Mobil Analizleri Raporu Oyun geliştirme işleriyle ilgili istatistik ve analizlere ulaşın. Raporu incele Üç aylık bülten Oyunlarınızın büyümesini sağlayacak en son haberleri ve ipuçlarını alın. Google'ın Topluluk kaynakları sayfası En yeni bloglarımıza, videolarımıza, programlarımıza, topluluğumuza ve destek kaynaklarımıza göz atın. Sayfayı ziyaret edin Bize geri bildirimde bulunmak mı istiyorsunuz? [[["Anlaması kolay","easyToUnderstand","thumb-up"],["Sorunumu çözdü","solvedMyProblem","thumb-up"],["Diğer","otherUp","thumb-up"]],[["İhtiyacım olan bilgiler yok","missingTheInformationINeed","thumb-down"],["Çok karmaşık / çok fazla adım var","tooComplicatedTooManySteps","thumb-down"],["Güncel değil","outOfDate","thumb-down"],["Çeviri sorunu","translationIssue","thumb-down"],["Örnek veya kod sorunu","samplesCodeIssue","thumb-down"],["Diğer","otherDown","thumb-down"]],[],[],[]] X X'te @AndroidDev'i takip edin YouTube YouTube'da Android Developers'a göz atın LinkedIn Connect with the Android Developers community on LinkedIn Android hakkında daha fazla Android İşletmeler için Android Güvenlik Kaynak Haber Blog Podcast'ler Keşfet Oyun Makine Öğrenimi Sağlık ve Fitness Kamera ve Medya Gizlilik 5G Android Cihazlar Büyük ekranlar Wear OS ChromeOS cihazlar Arabalar için Android Android TV Sürümler Android 15 Android 14 Android 13 Android 12 Android 11 Android 10 Pie Belgeler ve İndirmeler Android Studio kılavuzu Geliştirici kılavuzları API referansı Studio'yu indir Android NDK Destek Platform hatası bildir Belge hatası bildir Google Play support Araştırma çalışmalarına katıl Android Chrome Firebase Google Cloud Platform Tüm ürünler Gizlilik Lisans Marka kuralları Manage cookies E-postayla haberler ve ipuçları al Abone ol English Deutsch Español – América Latina Français Indonesia Italiano Polski Português – Brasil Tiếng Việt Türkçe Русский עברית العربيّة فارسی हिंदी বাংলা ภาษาไทย 中文 – 简体 中文 – 繁體 日本語 한국어 | 2026-01-13T09:30:12 |
https://developers.cloudflare.com/ai-gateway/get-started/#ai:local:ai-gateway | Getting started · Cloudflare AI Gateway docs Skip to content Cloudflare Docs Search Docs Directory APIs SDKs Help Log in Select theme Dark Light Auto AI Gateway No results found. Try a different search term, or use our global search . Overview Getting started Using AI Gateway Unified API (OpenAI compat) Provider Native Workers AI Amazon Bedrock Anthropic Azure OpenAI Baseten Cartesia Cerebras Cohere Deepgram DeepSeek ElevenLabs Fal AI Google AI Studio Google Vertex AI Groq HuggingFace Ideogram Mistral AI OpenAI OpenRouter Parallel Perplexity Replicate xAI WebSockets API Beta Overview Realtime WebSockets API Non-realtime WebSockets API Features Overview Unified Billing Caching Rate limiting Dynamic routing Beta Overview Using a dynamic route JSON Configuration Data Loss Prevention (DLP) Beta Overview Set up Data Loss Prevention (DLP) Guardrails Beta Overview Set up Guardrails Supported model types Usage considerations Configuration BYOK (Store Keys) Beta Custom costs Custom Providers Beta Manage gateways Request handling Authenticated Gateway Observability Costs Custom metadata Analytics Logging Overview Workers Logpush Integrations Vercel AI SDK Agents ↗ AI Gateway Binding Methods Workers AI Tutorials Platform Overview Limits Pricing Audit logs Changelog Header Glossary REST API reference ↗ API MCP server ↗ MCP AI Assistant ↗ Architectures LLM resources llms.txt prompt.txt AI Gateway llms-full.txt Developer Platform llms-full.txt GitHub X.com YouTube Select theme Dark Light Auto On this page Overview Authenticated gateway 🔒 Provider Authentication Integration Options Unified API Endpoint Provider-specific endpoints Next steps On this page Overview Authenticated gateway 🔒 Provider Authentication Integration Options Unified API Endpoint Provider-specific endpoints Next steps Was this helpful? Edit Issue Directory … AI Gateway Getting started Copy page Getting started Last reviewed: over 1 year ago In this guide, you will learn how to create and use your first AI Gateway. Dashboard API Go to AI Gateway Log into the Cloudflare dashboard ↗ and select your account. Go to AI > AI Gateway . Select Create Gateway . Enter your Gateway name . Note: Gateway name has a 64 character limit. Select Create . To set up an AI Gateway using the API: Create an API token with the following permissions: AI Gateway - Read AI Gateway - Edit Get your Account ID . Using that API token and Account ID, send a POST request to the Cloudflare API. Authenticated gateway 🔒 When you enable authentication on gateway each request is required to include a valid Cloudflare API token, adding an extra layer of security. We recommend using an authenticated gateway to prevent unauthorized access. Learn more . Provider Authentication Authenticate with your upstream AI provider using one of the following options: Unified Billing: Use the AI Gateway billing to pay for and authenticate your inference requests. Refer to Unified Billing . BYOK (Store Keys): Store your own provider API Keys with Cloudflare, and AI Gateway will include them at runtime. Refer to BYOK . Request headers: Include your provider API Key in the request headers as you normally would (for example, Authorization: Bearer <OPENAI_API_KEY> ). Integration Options Unified API Endpoint OpenAI Compatible Recommended The easiest way to get started with AI Gateway is through our OpenAI-compatible /chat/completions endpoint. This allows you to use existing OpenAI SDKs and tools with minimal code changes while gaining access to multiple AI providers. https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_name}/compat/chat/completions Key benefits: Drop-in replacement for OpenAI API, works with existing OpenAI SDKs and other OpenAI compliant clients Switch between providers by changing the model parameter Dynamic Routing - Define complex routing scenarios requiring conditional logic, conduct A/B tests, set rate / budget limits, etc Example: Make a request to OpenAI using OpenAI JS SDK with Stored Key (BYOK) import OpenAI from "openai" ; const client = new OpenAI ( { apiKey : "{cf_api_token}" , baseURL : "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat" , } ) ; const response = await client . chat . completions . create ( { model : "openai/gpt-5.2" , messages : [ { role : "user" , content : "Hello, world!" } ] , } ) ; import OpenAI from "openai" ; const client = new OpenAI ( { apiKey : "{cf_api_token}" , baseURL : "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat" , } ) ; const response = await client . chat . completions . create ( { model : "anthropic/claude-4-5-sonnet" , messages : [ { role : "user" , content : "Hello, world!" } ] , } ) ; import OpenAI from "openai" ; const client = new OpenAI ( { apiKey : "{cf_api_token}" , baseURL : "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat" , } ) ; const response = await client . chat . completions . create ( { model : "google/gemini-2.5-pro" , messages : [ { role : "user" , content : "Hello, world!" } ] , } ) ; import OpenAI from "openai" ; const client = new OpenAI ( { apiKey : "{cf_api_token}" , baseURL : "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat" , } ) ; const response = await client . chat . completions . create ( { model : "grok/grok-4" , messages : [ { role : "user" , content : "Hello, world!" } ] , } ) ; import OpenAI from "openai" ; const client = new OpenAI ( { apiKey : "{cf_api_token}" , baseURL : "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat" , } ) ; const response = await client . chat . completions . create ( { model : "dynamic/customer-support" , messages : [ { role : "user" , content : "Hello, world!" } ] , } ) ; import OpenAI from "openai" ; const client = new OpenAI ( { apiKey : "{cf_api_token}" , baseURL : "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat" , } ) ; const response = await client . chat . completions . create ( { model : "workers-ai/@cf/meta/llama-3.3-70b-instruct-fp8-fast" , messages : [ { role : "user" , content : "Hello, world!" } ] , } ) ; import OpenAI from "openai" ; const client = new OpenAI ( { apiKey : "{openai_api_token}" , defaultHeaders : { // if gateway is authenticated "cf-aig-authorization" : `Bearer {cf_api_token}` , }, baseURL : "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat" , } ) ; const response = await client . chat . completions . create ( { model : "openai/gpt-5.2" , messages : [ { role : "user" , content : "Hello, world!" } ] , } ) ; import OpenAI from "openai" ; const client = new OpenAI ( { apiKey : "{anthropic_api_token}" , defaultHeaders : { // if gateway is authenticated "cf-aig-authorization" : `Bearer {cf_api_token}` , }, baseURL : "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat" , } ) ; const response = await client . chat . completions . create ( { model : "anthropic/claude-4-5-sonnet" , messages : [ { role : "user" , content : "Hello, world!" } ] , } ) ; import OpenAI from "openai" ; const client = new OpenAI ( { apiKey : "{google_api_token}" , defaultHeaders : { // if gateway is authenticated "cf-aig-authorization" : `Bearer {cf_api_token}` , }, baseURL : "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat" , } ) ; const response = await client . chat . completions . create ( { model : "google/gemini-2.5-pro" , messages : [ { role : "user" , content : "Hello, world!" } ] , } ) ; import OpenAI from "openai" ; const client = new OpenAI ( { apiKey : "{grok_api_token}" , defaultHeaders : { // if gateway is authenticated "cf-aig-authorization" : `Bearer {cf_api_token}` , }, baseURL : "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat" , } ) ; const response = await client . chat . completions . create ( { model : "grok/grok-4" , messages : [ { role : "user" , content : "Hello, world!" } ] , } ) ; import OpenAI from "openai" ; const client = new OpenAI ( { apiKey : "{dynamic_api_token}" , defaultHeaders : { // if gateway is authenticated "cf-aig-authorization" : `Bearer {cf_api_token}` , }, baseURL : "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat" , } ) ; const response = await client . chat . completions . create ( { model : "dynamic/customer-support" , messages : [ { role : "user" , content : "Hello, world!" } ] , } ) ; import OpenAI from "openai" ; const client = new OpenAI ( { apiKey : "{workers-ai_api_token}" , defaultHeaders : { // if gateway is authenticated "cf-aig-authorization" : `Bearer {cf_api_token}` , }, baseURL : "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat" , } ) ; const response = await client . chat . completions . create ( { model : "workers-ai/@cf/meta/llama-3.3-70b-instruct-fp8-fast" , messages : [ { role : "user" , content : "Hello, world!" } ] , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified () ; const { text } = await generateText ( { model : aigateway ( unified ( 'openai/gpt-5.2' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified () ; const { text } = await generateText ( { model : aigateway ( unified ( 'anthropic/claude-4-5-sonnet' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified () ; const { text } = await generateText ( { model : aigateway ( unified ( 'google/gemini-2.5-pro' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified () ; const { text } = await generateText ( { model : aigateway ( unified ( 'grok/grok-4' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified () ; const { text } = await generateText ( { model : aigateway ( unified ( 'dynamic/customer-support' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified () ; const { text } = await generateText ( { model : aigateway ( unified ( 'workers-ai/@cf/meta/llama-3.3-70b-instruct-fp8-fast' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( unified ( 'openai/gpt-5.2' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( unified ( 'anthropic/claude-4-5-sonnet' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( unified ( 'google/gemini-2.5-pro' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( unified ( 'grok/grok-4' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( unified ( 'dynamic/customer-support' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( unified ( 'workers-ai/@cf/meta/llama-3.3-70b-instruct-fp8-fast' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createOpenAI } from 'ai-gateway-provider/providers/openai' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const openai = createOpenAI () ; const { text } = await generateText ( { model : aigateway ( openai . chat ( 'gpt-5.2' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createAnthropic } from 'ai-gateway-provider/providers/anthropic' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const anthropic = createAnthropic () ; const { text } = await generateText ( { model : aigateway ( anthropic ( 'claude-4-5-sonnet' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createGoogle } from 'ai-gateway-provider/providers/google' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const google = createGoogle () ; const { text } = await generateText ( { model : aigateway ( google ( 'gemini-2.5-pro' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createXai } from 'ai-gateway-provider/providers/xai' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const xai = createXai () ; const { text } = await generateText ( { model : aigateway ( xai ( 'grok-4' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified () ; const { text } = await generateText ( { model : aigateway ( unified ( 'customer-support' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified () ; const { text } = await generateText ( { model : aigateway ( unified ( '@cf/meta/llama-3.3-70b-instruct-fp8-fast' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createOpenAI } from 'ai-gateway-provider/providers/openai' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const openai = createOpenAI ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( openai . chat ( 'gpt-5.2' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createAnthropic } from 'ai-gateway-provider/providers/anthropic' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const anthropic = createAnthropic ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( anthropic ( 'claude-4-5-sonnet' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createGoogle } from 'ai-gateway-provider/providers/google' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const google = createGoogle ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( google ( 'gemini-2.5-pro' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createXai } from 'ai-gateway-provider/providers/xai' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const xai = createXai ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( xai ( 'grok-4' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( unified ( 'customer-support' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( unified ( '@cf/meta/llama-3.3-70b-instruct-fp8-fast' )) , prompt : 'What is Cloudflare?' , } ) ; curl -X POST https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions \ --header 'cf-aig-authorization: Bearer {CF_AIG_TOKEN}' \ --header 'Content-Type: application/json' \ --data '{ "model": "openai/gpt-5.2", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] }' curl -X POST https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions \ --header 'cf-aig-authorization: Bearer {CF_AIG_TOKEN}' \ --header 'Content-Type: application/json' \ --data '{ "model": "anthropic/claude-4-5-sonnet", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] }' curl -X POST https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions \ --header 'cf-aig-authorization: Bearer {CF_AIG_TOKEN}' \ --header 'Content-Type: application/json' \ --data '{ "model": "google/gemini-2.5-pro", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] }' curl -X POST https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions \ --header 'cf-aig-authorization: Bearer {CF_AIG_TOKEN}' \ --header 'Content-Type: application/json' \ --data '{ "model": "grok/grok-4", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] }' curl -X POST https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions \ --header 'cf-aig-authorization: Bearer {CF_AIG_TOKEN}' \ --header 'Content-Type: application/json' \ --data '{ "model": "dynamic/customer-support", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] }' curl -X POST https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions \ --header 'cf-aig-authorization: Bearer {CF_AIG_TOKEN}' \ --header 'Content-Type: application/json' \ --data '{ "model": "workers-ai/@cf/meta/llama-3.3-70b-instruct-fp8-fast", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] }' curl -X POST https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions \ --header 'cf-aig-authorization: Bearer {CF_AIG_TOKEN}' \ --header 'Authorization: Bearer {openai_api_token}' \ --header 'Content-Type: application/json' \ --data '{ "model": "openai/gpt-5.2", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] }' curl -X POST https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions \ --header 'cf-aig-authorization: Bearer {CF_AIG_TOKEN}' \ --header 'Authorization: Bearer {anthropic_api_token}' \ --header 'Content-Type: application/json' \ --data '{ "model": "anthropic/claude-4-5-sonnet", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] }' curl -X POST https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions \ --header 'cf-aig-authorization: Bearer {CF_AIG_TOKEN}' \ --header 'Authorization: Bearer {google_api_token}' \ --header 'Content-Type: application/json' \ --data '{ "model": "google/gemini-2.5-pro", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] }' curl -X POST https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions \ --header 'cf-aig-authorization: Bearer {CF_AIG_TOKEN}' \ --header 'Authorization: Bearer {grok_api_token}' \ --header 'Content-Type: application/json' \ --data '{ "model": "grok/grok-4", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] }' curl -X POST https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions \ --header 'cf-aig-authorization: Bearer {CF_AIG_TOKEN}' \ --header 'Authorization: Bearer {dynamic_api_token}' \ --header 'Content-Type: application/json' \ --data '{ "model": "dynamic/customer-support", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] }' curl -X POST https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions \ --header 'cf-aig-authorization: Bearer {CF_AIG_TOKEN}' \ --header 'Authorization: Bearer {workers-ai_api_token}' \ --header 'Content-Type: application/json' \ --data '{ "model": "workers-ai/@cf/meta/llama-3.3-70b-instruct-fp8-fast", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] }' Refer to Unified API to learn more about OpenAI compatibility. Provider-specific endpoints For direct integration with specific AI providers, use dedicated endpoints that maintain the original provider's API schema while adding AI Gateway features. https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/{provider} Available providers: OpenAI - GPT models and embeddings Anthropic - Claude models Google AI Studio - Gemini models Workers AI - Cloudflare's inference platform AWS Bedrock - Amazon's managed AI service Azure OpenAI - Microsoft's OpenAI service and more... Next steps Learn more about caching for faster requests and cost savings and rate limiting to control how your application scales. Explore how to specify model or provider fallbacks, ratelimits, A/B tests for resiliency. Learn how to use low-cost, open source models on Workers AI - our AI inference service. Was this helpful? Edit page Last updated: Jan 7, 2026 Previous Overview Next Unified API (OpenAI compat) Resources API New to Cloudflare? Directory Sponsorships Open Source Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Speed Test Is BGP Safe Yet? RPKI Toolkit Certificate Transparency Community X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings | 2026-01-13T09:30:12 |
https://developers.cloudflare.com/ai-gateway/observability/custom-metadata/ | Custom metadata · Cloudflare AI Gateway docs Skip to content Cloudflare Docs Search Docs Directory APIs SDKs Help Log in Select theme Dark Light Auto AI Gateway No results found. Try a different search term, or use our global search . Overview Getting started Using AI Gateway Unified API (OpenAI compat) Provider Native Workers AI Amazon Bedrock Anthropic Azure OpenAI Baseten Cartesia Cerebras Cohere Deepgram DeepSeek ElevenLabs Fal AI Google AI Studio Google Vertex AI Groq HuggingFace Ideogram Mistral AI OpenAI OpenRouter Parallel Perplexity Replicate xAI WebSockets API Beta Overview Realtime WebSockets API Non-realtime WebSockets API Features Overview Unified Billing Caching Rate limiting Dynamic routing Beta Overview Using a dynamic route JSON Configuration Data Loss Prevention (DLP) Beta Overview Set up Data Loss Prevention (DLP) Guardrails Beta Overview Set up Guardrails Supported model types Usage considerations Configuration BYOK (Store Keys) Beta Custom costs Custom Providers Beta Manage gateways Request handling Authenticated Gateway Observability Costs Custom metadata Analytics Logging Overview Workers Logpush Integrations Vercel AI SDK Agents ↗ AI Gateway Binding Methods Workers AI Tutorials Platform Overview Limits Pricing Audit logs Changelog Header Glossary REST API reference ↗ API MCP server ↗ MCP AI Assistant ↗ Architectures LLM resources llms.txt prompt.txt AI Gateway llms-full.txt Developer Platform llms-full.txt GitHub X.com YouTube Select theme Dark Light Auto On this page Overview Key Features Supported Metadata Types Implementations Using cURL Using SDK Using Binding On this page Overview Key Features Supported Metadata Types Implementations Using cURL Using SDK Using Binding Was this helpful? Edit Issue Directory … AI Gateway Observability Custom metadata Copy page Custom metadata Custom metadata in AI Gateway allows you to tag requests with user IDs or other identifiers, enabling better tracking and analysis of your requests. Metadata values can be strings, numbers, or booleans, and will appear in your logs, making it easy to search and filter through your data. Key Features Custom Tagging : Add user IDs, team names, test indicators, and other relevant information to your requests. Enhanced Logging : Metadata appears in your logs, allowing for detailed inspection and troubleshooting. Search and Filter : Use metadata to efficiently search and filter through logged requests. Note AI Gateway allows you to pass up to five custom metadata entries per request. If more than five entries are provided, only the first five will be saved; additional entries will be ignored. Ensure your custom metadata is limited to five entries to avoid unprocessed or lost data. Supported Metadata Types String Number Boolean Note Objects are not supported as metadata values. Implementations Using cURL To include custom metadata in your request using cURL: Terminal window curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/openai/chat/completions \ --header 'Authorization: Bearer {api_token}' \ --header 'Content-Type: application/json' \ --header 'cf-aig-metadata: {"team": "AI", "user": 12345, "test":true}' \ --data '{"model": "gpt-4o", "messages": [{"role": "user", "content": "What should I eat for lunch?"}]}' Using SDK To include custom metadata in your request using the OpenAI SDK: JavaScript import OpenAI from "openai" ; export default { async fetch ( request , env , ctx ) { const openai = new OpenAI ( { apiKey : env . OPENAI_API_KEY , baseURL : "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/openai" , } ) ; try { const chatCompletion = await openai . chat . completions . create ( { model : "gpt-4o" , messages : [ { role : "user" , content : "What should I eat for lunch?" } ] , max_tokens : 50 , }, { headers : { "cf-aig-metadata" : JSON . stringify ( { user : "JaneDoe" , team : 12345 , test : true } ) , }, } ) ; const response = chatCompletion . choices [ 0 ] . message ; return new Response ( JSON . stringify ( response )) ; } catch ( e ) { console . log ( e ) ; return new Response ( e ) ; } }, }; Using Binding To include custom metadata in your request using Bindings : JavaScript export default { async fetch ( request , env , ctx ) { const aiResp = await env . AI . run ( '@cf/mistral/mistral-7b-instruct-v0.1' , { prompt : 'What should I eat for lunch?' }, { gateway : { id : 'gateway_id' , metadata : { "team" : "AI" , "user" : 12345 , "test" : true } } } ) ; return new Response ( aiResp ) ; }, }; Was this helpful? Edit page Last updated: Aug 19, 2025 Previous Costs Next Analytics Resources API New to Cloudflare? Directory Sponsorships Open Source Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Speed Test Is BGP Safe Yet? RPKI Toolkit Certificate Transparency Community X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings | 2026-01-13T09:30:12 |
https://developers.cloudflare.com/ai-gateway/configuration/request-handling/ | Request handling · Cloudflare AI Gateway docs Skip to content Cloudflare Docs Search Docs Directory APIs SDKs Help Log in Select theme Dark Light Auto AI Gateway No results found. Try a different search term, or use our global search . Overview Getting started Using AI Gateway Unified API (OpenAI compat) Provider Native Workers AI Amazon Bedrock Anthropic Azure OpenAI Baseten Cartesia Cerebras Cohere Deepgram DeepSeek ElevenLabs Fal AI Google AI Studio Google Vertex AI Groq HuggingFace Ideogram Mistral AI OpenAI OpenRouter Parallel Perplexity Replicate xAI WebSockets API Beta Overview Realtime WebSockets API Non-realtime WebSockets API Features Overview Unified Billing Caching Rate limiting Dynamic routing Beta Overview Using a dynamic route JSON Configuration Data Loss Prevention (DLP) Beta Overview Set up Data Loss Prevention (DLP) Guardrails Beta Overview Set up Guardrails Supported model types Usage considerations Configuration BYOK (Store Keys) Beta Custom costs Custom Providers Beta Manage gateways Request handling Authenticated Gateway Observability Costs Custom metadata Analytics Logging Overview Workers Logpush Integrations Vercel AI SDK Agents ↗ AI Gateway Binding Methods Workers AI Tutorials Platform Overview Limits Pricing Audit logs Changelog Header Glossary REST API reference ↗ API MCP server ↗ MCP AI Assistant ↗ Architectures LLM resources llms.txt prompt.txt AI Gateway llms-full.txt Developer Platform llms-full.txt GitHub X.com YouTube Select theme Dark Light Auto On this page Overview Request timeouts Definitions Configuration Request retries Definitions Configuration On this page Overview Request timeouts Definitions Configuration Request retries Definitions Configuration Was this helpful? Edit Issue Directory … AI Gateway Configuration Request handling Copy page Request handling Deprecated While the request handling features described on this page still work, Dynamic Routing is now the preferred way to achieve advanced request handling, including timeouts, retries, and fallbacks. Dynamic Routing provides a more powerful and flexible approach with a visual interface for managing complex routing scenarios. Your AI gateway supports different strategies for handling requests to providers, which allows you to manage AI interactions effectively and ensure your applications remain responsive and reliable. Request timeouts A request timeout allows you to trigger fallbacks or a retry if a provider takes too long to respond. These timeouts help: Improve user experience, by preventing users from waiting too long for a response Proactively handle errors, by detecting unresponsive providers and triggering a fallback option Request timeouts can be set on a Universal Endpoint or directly on a request to any provider. Definitions A timeout is set in milliseconds. Additionally, the timeout is based on when the first part of the response comes back. As long as the first part of the response returns within the specified timeframe - such as when streaming a response - your gateway will wait for the response. Configuration Universal Endpoint If set on a Universal Endpoint , a request timeout specifies the timeout duration for requests and triggers a fallback. For a Universal Endpoint, configure the timeout value by setting a requestTimeout property within the provider-specific config object. Each provider can have a different requestTimeout value for granular customization. Provider-level config curl 'https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}' \ --header 'Content-Type: application/json' \ --data '[ { "provider": "workers-ai", "endpoint": "@cf/meta/llama-3.1-8b-instruct", "headers": { "Authorization": "Bearer {cloudflare_token}", "Content-Type": "application/json" }, "config": { "requestTimeout": 1000 }, "query": { 34 collapsed lines "messages": [ { "role": "system", "content": "You are a friendly assistant" }, { "role": "user", "content": "What is Cloudflare?" } ] } }, { "provider": "workers-ai", "endpoint": "@cf/meta/llama-3.1-8b-instruct-fast", "headers": { "Authorization": "Bearer {cloudflare_token}", "Content-Type": "application/json" }, "query": { "messages": [ { "role": "system", "content": "You are a friendly assistant" }, { "role": "user", "content": "What is Cloudflare?" } ] }, "config": { "requestTimeout": 3000 }, } ]' Direct provider If set on a provider request, request timeout specifies the timeout duration for a request and - if exceeded - returns an error. For a provider-specific endpoint, configure the timeout value by adding a cf-aig-request-timeout header. Provider-specific endpoint example curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/workers-ai/@cf/meta/llama-3.1-8b-instruct \ --header 'Authorization: Bearer {cf_api_token}' \ --header 'Content-Type: application/json' \ --header 'cf-aig-request-timeout: 5000' --data '{"prompt": "What is Cloudflare?"}' Request retries AI Gateway also supports automatic retries for failed requests, with a maximum of five retry attempts. This feature improves your application's resiliency, ensuring you can recover from temporary issues without manual intervention. Request timeouts can be set on a Universal Endpoint or directly on a request to any provider. Definitions With request retries, you can adjust a combination of three properties: Number of attempts (maximum of 5 tries) How long before retrying (in milliseconds, maximum of 5 seconds) Backoff method (constant, linear, or exponential) On the final retry attempt, your gateway will wait until the request completes, regardless of how long it takes. Configuration Universal endpoint If set on a Universal Endpoint , a request retry will automatically retry failed requests up to five times before triggering any configured fallbacks. For a Universal Endpoint, configure the retry settings with the following properties in the provider-specific config : config: { maxAttempts? : number; retryDelay?: number; backoff?: "constant" | "linear" | "exponential" ; } As with the request timeout , each provider can have a different retry settings for granular customization. Provider-level config curl 'https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}' \ --header 'Content-Type: application/json' \ --data '[ { "provider": "workers-ai", "endpoint": "@cf/meta/llama-3.1-8b-instruct", "headers": { "Authorization": "Bearer {cloudflare_token}", "Content-Type": "application/json" }, "config": { "maxAttempts": 2, "retryDelay": 1000, "backoff": "constant" }, 39 collapsed lines "query": { "messages": [ { "role": "system", "content": "You are a friendly assistant" }, { "role": "user", "content": "What is Cloudflare?" } ] } }, { "provider": "workers-ai", "endpoint": "@cf/meta/llama-3.1-8b-instruct-fast", "headers": { "Authorization": "Bearer {cloudflare_token}", "Content-Type": "application/json" }, "query": { "messages": [ { "role": "system", "content": "You are a friendly assistant" }, { "role": "user", "content": "What is Cloudflare?" } ] }, "config": { "maxAttempts": 4, "retryDelay": 1000, "backoff": "exponential" }, } ]' Direct provider If set on a provider request, a request retry will automatically retry failed requests up to five times. On the final retry attempt, your gateway will wait until the request completes, regardless of how long it takes. For a provider-specific endpoint, configure the retry settings by adding different header values: cf-aig-max-attempts (number) cf-aig-retry-delay (number) cf-aig-backoff ("constant" | "linear" | "exponential) Was this helpful? Edit page Last updated: Aug 19, 2025 Previous Manage gateways Next Authenticated Gateway Resources API New to Cloudflare? Directory Sponsorships Open Source Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Speed Test Is BGP Safe Yet? RPKI Toolkit Certificate Transparency Community X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings | 2026-01-13T09:30:12 |
https://developers.google.com/admob/api/reference/rest/v1beta/accounts.mediationGroups.mediationAbExperiments/create | Method: accounts.mediationGroups.mediationAbExperiments.create | AdMob API | Google for Developers Skip to main content AdMob API / English Deutsch Español Español – América Latina Français Indonesia Italiano Polski Português – Brasil Tiếng Việt Türkçe Русский עברית العربيّة فارسی हिंदी বাংলা ภาษาไทย 中文 – 简体 中文 – 繁體 日本語 한국어 Sign in AdMob Guides Reference Libraries & Examples Support AdMob API AdMob Guides Reference Libraries & Examples Support Release notes AdMob API v1 REST Resources accounts Overview get list accounts.adUnits Overview list accounts.apps Overview list accounts.mediationReport Overview generate accounts.networkReport Overview generate Types DateRange LocalizationSettings ReportFooter ReportHeader ReportRow SortOrder StringList v1beta REST Resources accounts Overview get list accounts.adSources Overview list accounts.adSources.adapters Overview list accounts.adUnitMappings Overview batchCreate accounts.adUnits Overview create list accounts.adUnits.adUnitMappings Overview create list accounts.apps Overview create list accounts.campaignReport Overview generate accounts.mediationGroups Overview create list patch accounts.mediationGroups.mediationAbExperiments Overview create stop accounts.mediationReport Overview generate accounts.networkReport Overview generate Types DateRange LocalizationSettings MediationGroupLine ReportFooter ReportHeader ReportRow SortOrder StringList API dictionary Ad sources Adapters Home Products AdMob API Reference Method: accounts.mediationGroups.mediationAbExperiments.create Stay organized with collections Save and categorize content based on your preferences. Page Summary outlined_flag This method creates an A/B testing experiment for a specified AdMob account and mediation group. Access to this method is limited and requires reaching out to an account manager for access if a 403 permission denied error is encountered. The HTTP request uses a POST method with a URL that includes the parent account and mediation group ID. The request body should contain an instance of MediationAbExperiment . A successful response body will contain a newly created instance of MediationAbExperiment . HTTP request Path parameters Request body Response body Authorization scopes Examples Try it! Create an A/B testing experiment for a specified AdMob account and a mediation group. This method has limited access. If you see a 403 permission denied error, please reach out to your account manager for access. HTTP request POST https://admob.googleapis.com/v1beta/{parent=accounts/*/mediationGroups/*}/mediationAbExperiments The URL uses gRPC Transcoding syntax. Path parameters Parameters parent string Required. The parent which owns the mediation group. Format: accounts/{publisherId}/mediationGroups/{mediationGroupId} Request body The request body contains an instance of MediationAbExperiment . Response body If successful, the response body contains a newly created instance of MediationAbExperiment . Authorization scopes Requires the following OAuth scope: https://www.googleapis.com/auth/admob.monetization For more information, see the OAuth 2.0 Overview . Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License , and code samples are licensed under the Apache 2.0 License . For details, see the Google Developers Site Policies . Java is a registered trademark of Oracle and/or its affiliates. Last updated 2025-08-20 UTC. [[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-20 UTC."],[],["This documentation outlines the process of creating an A/B testing experiment for an AdMob mediation group using a POST request. The request is sent to a specific URL, defined by the parent account and mediation group ID, supplied as a path parameter. The request body includes the `MediationAbExperiment` data. Successful requests return a newly created `MediationAbExperiment` instance in the response body. Authorization requires the `admob.monetization` OAuth scope. Access may be restricted.\n"]] Product info Usage limits Pricing Terms of Service Programs Google Developer Program Google Developer Groups Google Developer Experts Accelerators Google Cloud & NVIDIA Developer consoles Google API Console Google Cloud Platform Console Google Play Console Firebase Console Actions on Google Console Cast SDK Developer Console Chrome Web Store Dashboard Google Home Developer Console Android Chrome Firebase Google Cloud Platform Google AI All products Terms Privacy Manage cookies English Deutsch Español Español – América Latina Français Indonesia Italiano Polski Português – Brasil Tiếng Việt Türkçe Русский עברית العربيّة فارسی हिंदी বাংলা ภาษาไทย 中文 – 简体 中文 – 繁體 日本語 한국어 | 2026-01-13T09:30:12 |
https://developers.cloudflare.com/ai-gateway/tutorials/ | Tutorials · Cloudflare AI Gateway docs Skip to content Cloudflare Docs Search Docs Directory APIs SDKs Help Log in Select theme Dark Light Auto AI Gateway No results found. Try a different search term, or use our global search . Overview Getting started Using AI Gateway Unified API (OpenAI compat) Provider Native Workers AI Amazon Bedrock Anthropic Azure OpenAI Baseten Cartesia Cerebras Cohere Deepgram DeepSeek ElevenLabs Fal AI Google AI Studio Google Vertex AI Groq HuggingFace Ideogram Mistral AI OpenAI OpenRouter Parallel Perplexity Replicate xAI WebSockets API Beta Overview Realtime WebSockets API Non-realtime WebSockets API Features Overview Unified Billing Caching Rate limiting Dynamic routing Beta Overview Using a dynamic route JSON Configuration Data Loss Prevention (DLP) Beta Overview Set up Data Loss Prevention (DLP) Guardrails Beta Overview Set up Guardrails Supported model types Usage considerations Configuration BYOK (Store Keys) Beta Custom costs Custom Providers Beta Manage gateways Request handling Authenticated Gateway Observability Costs Custom metadata Analytics Logging Overview Workers Logpush Integrations Vercel AI SDK Agents ↗ AI Gateway Binding Methods Workers AI Tutorials Platform Overview Limits Pricing Audit logs Changelog Header Glossary REST API reference ↗ API MCP server ↗ MCP AI Assistant ↗ Architectures LLM resources llms.txt prompt.txt AI Gateway llms-full.txt Developer Platform llms-full.txt GitHub X.com YouTube Select theme Dark Light Auto On this page Overview Docs Videos On this page Overview Docs Videos Was this helpful? Edit Issue Directory … AI Gateway Tutorials Copy page Tutorials View A tutorial is a practical lesson that takes you from a clear starting to ending point. " class="border-b-2 border-dashed border-accent" tabindex="0">tutorials to help you get started with AI Gateway. Docs Name Last Updated Difficulty AI Gateway Binding Methods 10 months ago Workers AI about 1 year ago Create your first AI Gateway using Workers AI over 1 year ago Beginner Deploy a Worker that connects to OpenAI via AI Gateway over 2 years ago Beginner Videos Play Cloudflare Workflows | Introduction (Part 1 of 3) In this video, we introduce Cloudflare Workflows, the Newest Developer Platform Primitive at Cloudflare. Play Cloudflare Workflows | Batching and Monitoring Your Durable Execution (Part 2 of 3) Workflows exposes metrics such as execution, error rates, steps, and total duration! Play Welcome to the Cloudflare Developer Channel Welcome to the Cloudflare Developers YouTube channel. We've got tutorials and working demos and everything you need to level up your projects. Whether you're working on your next big thing or just dorking around with some side projects, we've got you covered! So why don't you come hang out, subscribe to our developer channel and together we'll build something awesome. You're gonna love it. Play Optimize your AI App & fine-tune models (AI Gateway, R2) In this workshop, Kristian Freeman, Cloudflare Developer Advocate, shows how to optimize your existing AI applications with Cloudflare AI Gateway, and how to finetune OpenAI models using R2. Play How to use Cloudflare AI models and inference in Python with Jupyter Notebooks Cloudflare Workers AI provides a ton of AI models and inference capabilities. In this video, we will explore how to make use of Cloudflare’s AI model catalog using a Python Jupyter Notebook. Was this helpful? Edit page Last updated: May 9, 2025 Previous Workers AI Next Platform Resources API New to Cloudflare? Directory Sponsorships Open Source Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Speed Test Is BGP Safe Yet? RPKI Toolkit Certificate Transparency Community X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings | 2026-01-13T09:30:12 |
https://developers.cloudflare.com/ai-gateway/usage/providers/deepgram/ | Deepgram · Cloudflare AI Gateway docs Skip to content Cloudflare Docs Search Docs Directory APIs SDKs Help Log in Select theme Dark Light Auto AI Gateway No results found. Try a different search term, or use our global search . Overview Getting started Using AI Gateway Unified API (OpenAI compat) Provider Native Workers AI Amazon Bedrock Anthropic Azure OpenAI Baseten Cartesia Cerebras Cohere Deepgram DeepSeek ElevenLabs Fal AI Google AI Studio Google Vertex AI Groq HuggingFace Ideogram Mistral AI OpenAI OpenRouter Parallel Perplexity Replicate xAI WebSockets API Beta Overview Realtime WebSockets API Non-realtime WebSockets API Features Overview Unified Billing Caching Rate limiting Dynamic routing Beta Overview Using a dynamic route JSON Configuration Data Loss Prevention (DLP) Beta Overview Set up Data Loss Prevention (DLP) Guardrails Beta Overview Set up Guardrails Supported model types Usage considerations Configuration BYOK (Store Keys) Beta Custom costs Custom Providers Beta Manage gateways Request handling Authenticated Gateway Observability Costs Custom metadata Analytics Logging Overview Workers Logpush Integrations Vercel AI SDK Agents ↗ AI Gateway Binding Methods Workers AI Tutorials Platform Overview Limits Pricing Audit logs Changelog Header Glossary REST API reference ↗ API MCP server ↗ MCP AI Assistant ↗ Architectures LLM resources llms.txt prompt.txt AI Gateway llms-full.txt Developer Platform llms-full.txt GitHub X.com YouTube Select theme Dark Light Auto On this page Overview Endpoint URL Structure Prerequisites Example SDK On this page Overview Endpoint URL Structure Prerequisites Example SDK Was this helpful? Edit Issue Directory … AI Gateway Using AI Gateway Provider Native Deepgram Copy page Deepgram Deepgram ↗ provides Voice AI APIs for speech-to-text, text-to-speech, and voice agents. Note Deepgram is also available through Workers AI, see Deepgram Workers AI . Endpoint https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/deepgram URL Structure When making requests to Deepgram, replace https://api.deepgram.com/ in the URL you are currently using with https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/deepgram/ . Prerequisites When making requests to Deepgram, ensure you have the following: Your AI Gateway Account ID. Your AI Gateway gateway name. An active Deepgram API token. Example SDK TS import { createClient , LiveTranscriptionEvents } from "@deepgram/sdk" ; const deepgram = createClient ( "{deepgram_api_key}" , { global : { websocket : { options : { url : "wss://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/deepgram/" , _nodeOnlyHeaders : { "cf-aig-authorization" : "Bearer {CF_AIG_TOKEN}" } } } } } ) ; const connection = deepgram . listen . live ( { model : "nova-3" , language : "en-US" , smart_format : true , } ) ; connection . send ( ... ) ; Was this helpful? Edit page Last updated: Nov 3, 2025 Previous Cohere Next DeepSeek Resources API New to Cloudflare? Directory Sponsorships Open Source Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Speed Test Is BGP Safe Yet? RPKI Toolkit Certificate Transparency Community X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings | 2026-01-13T09:30:12 |
https://developers.cloudflare.com/ai-gateway/integrations/aig-workers-ai-binding/ | Workers AI · Cloudflare AI Gateway docs Skip to content Cloudflare Docs Search Docs Directory APIs SDKs Help Log in Select theme Dark Light Auto AI Gateway No results found. Try a different search term, or use our global search . Overview Getting started Using AI Gateway Unified API (OpenAI compat) Provider Native Workers AI Amazon Bedrock Anthropic Azure OpenAI Baseten Cartesia Cerebras Cohere Deepgram DeepSeek ElevenLabs Fal AI Google AI Studio Google Vertex AI Groq HuggingFace Ideogram Mistral AI OpenAI OpenRouter Parallel Perplexity Replicate xAI WebSockets API Beta Overview Realtime WebSockets API Non-realtime WebSockets API Features Overview Unified Billing Caching Rate limiting Dynamic routing Beta Overview Using a dynamic route JSON Configuration Data Loss Prevention (DLP) Beta Overview Set up Data Loss Prevention (DLP) Guardrails Beta Overview Set up Guardrails Supported model types Usage considerations Configuration BYOK (Store Keys) Beta Custom costs Custom Providers Beta Manage gateways Request handling Authenticated Gateway Observability Costs Custom metadata Analytics Logging Overview Workers Logpush Integrations Vercel AI SDK Agents ↗ AI Gateway Binding Methods Workers AI Tutorials Platform Overview Limits Pricing Audit logs Changelog Header Glossary REST API reference ↗ API MCP server ↗ MCP AI Assistant ↗ Architectures LLM resources llms.txt prompt.txt AI Gateway llms-full.txt Developer Platform llms-full.txt GitHub X.com YouTube Select theme Dark Light Auto On this page Overview Prerequisites 1. Create a Worker Project 2. Connect your Worker to Workers AI 3. Run an inference task containing AI Gateway in your Worker 4. Develop locally with Wrangler 5. Deploy your AI Worker On this page Overview Prerequisites 1. Create a Worker Project 2. Connect your Worker to Workers AI 3. Run an inference task containing AI Gateway in your Worker 4. Develop locally with Wrangler 5. Deploy your AI Worker Was this helpful? Edit Issue Directory … AI Gateway Integrations Workers AI Copy page Workers AI Last reviewed: about 1 year ago This guide will walk you through setting up and deploying a Workers AI project. You will use Workers , an AI Gateway binding, and a large language model (LLM), to deploy your first AI-powered application on the Cloudflare global network. Prerequisites Sign up for a Cloudflare account ↗ . Install Node.js ↗ . Node.js version manager Use a Node version manager like Volta ↗ or nvm ↗ to avoid permission issues and change Node.js versions. Wrangler , discussed later in this guide, requires a Node version of 16.17.0 or later. 1. Create a Worker Project You will create a new Worker project using the create-Cloudflare CLI (C3). C3 is a command-line tool designed to help you set up and deploy new applications to Cloudflare. Create a new project named hello-ai by running: npm yarn pnpm Terminal window npm create cloudflare@latest -- hello-ai Terminal window yarn create cloudflare hello-ai Terminal window pnpm create cloudflare@latest hello-ai Running npm create cloudflare@latest will prompt you to install the create-cloudflare package and lead you through setup. C3 will also install Wrangler , the Cloudflare Developer Platform CLI. For setup, select the following options: For What would you like to start with? , choose Hello World example . For Which template would you like to use? , choose Worker only . For Which language do you want to use? , choose TypeScript . For Do you want to use git for version control? , choose Yes . For Do you want to deploy your application? , choose No (we will be making some changes before deploying). This will create a new hello-ai directory. Your new hello-ai directory will include: A "Hello World" Worker at src/index.ts . A Wrangler configuration file Go to your application directory: Terminal window cd hello-ai 2. Connect your Worker to Workers AI You must create an AI binding for your Worker to connect to Workers AI. Bindings allow your Workers to interact with resources, like Workers AI, on the Cloudflare Developer Platform. To bind Workers AI to your Worker, add the following to the end of your Wrangler configuration file : wrangler.jsonc wrangler.toml { " $schema " : "./node_modules/wrangler/config-schema.json" , " ai " : { " binding " : "AI" } } [ ai ] binding = "AI" Your binding is available in your Worker code on env.AI . You will need to have your gateway id for the next step. You can learn how to create an AI Gateway in this tutorial . 3. Run an inference task containing AI Gateway in your Worker You are now ready to run an inference task in your Worker. In this case, you will use an LLM, llama-3.1-8b-instruct-fast , to answer a question. Your gateway ID is found on the dashboard. Update the index.ts file in your hello-ai application directory with the following code: src/index.ts export interface Env { // If you set another name in the [Wrangler configuration file](/workers/wrangler/configuration/) as the value for 'binding', // replace "AI" with the variable name you defined. AI : Ai ; } export default { async fetch ( request , env ) : Promise < Response > { // Specify the gateway label and other options here const response = await env . AI . run ( "@cf/meta/llama-3.1-8b-instruct-fast" , { prompt : "What is the origin of the phrase Hello, World" , }, { gateway : { id : "GATEWAYID" , // Use your gateway label here skipCache : true , // Optional: Skip cache if needed }, }, ) ; // Return the AI response as a JSON object return new Response ( JSON . stringify ( response ) , { headers : { "Content-Type" : "application/json" }, } ) ; }, } satisfies ExportedHandler < Env >; { // Specify the gateway label and other options here const response = await env.AI.run( "@cf/meta/llama-3.1-8b-instruct-fast", { prompt: "What is the origin of the phrase Hello, World", }, { gateway: { id: "GATEWAYID", // Use your gateway label here skipCache: true, // Optional: Skip cache if needed }, }, ); // Return the AI response as a JSON object return new Response(JSON.stringify(response), { headers: { "Content-Type": "application/json" }, }); },} satisfies ExportedHandler ;"> Up to this point, you have created an AI binding for your Worker and configured your Worker to be able to execute the Llama 3.1 model. You can now test your project locally before you deploy globally. 4. Develop locally with Wrangler While in your project directory, test Workers AI locally by running wrangler dev : Terminal window npx wrangler dev Workers AI local development usage charges Using Workers AI always accesses your Cloudflare account in order to run AI models and will incur usage charges even in local development. You will be prompted to log in after you run wrangler dev . When you run npx wrangler dev , Wrangler will give you a URL (most likely localhost:8787 ) to review your Worker. After you go to the URL Wrangler provides, you will see a message that resembles the following example: { " response " : "A fascinating question! \n\n The phrase \" Hello, World! \" originates from a simple computer program written in the early days of programming. It is often attributed to Brian Kernighan, a Canadian computer scientist and a pioneer in the field of computer programming. \n\n In the early 1970s, Kernighan, along with his colleague Dennis Ritchie, were working on the C programming language. They wanted to create a simple program that would output a message to the screen to demonstrate the basic structure of a program. They chose the phrase \" Hello, World! \" because it was a simple and recognizable message that would illustrate how a program could print text to the screen. \n\n The exact code was written in the 5th edition of Kernighan and Ritchie's book \" The C Programming Language, \" published in 1988. The code, literally known as \" Hello, World! \" is as follows: \n\n ``` main() { printf( \" Hello, World! \" ); } ``` \n\n This code is still often used as a starting point for learning programming languages, as it demonstrates how to output a simple message to the console. \n\n The phrase \" Hello, World! \" has since become a catch-all phrase to indicate the start of a new program or a small test program, and is widely used in computer science and programming education. \n\n Sincerely, I'm glad I could help clarify the origin of this iconic phrase for you!" } 5. Deploy your AI Worker Before deploying your AI Worker globally, log in with your Cloudflare account by running: Terminal window npx wrangler login You will be directed to a web page asking you to log in to the Cloudflare dashboard. After you have logged in, you will be asked if Wrangler can make changes to your Cloudflare account. Scroll down and select Allow to continue. Finally, deploy your Worker to make your project accessible on the Internet. To deploy your Worker, run: Terminal window npx wrangler deploy Once deployed, your Worker will be available at a URL like: Terminal window https://hello-ai.<YOUR_SUBDOMAIN>.workers.dev .workers.dev"> Your Worker will be deployed to your custom workers.dev subdomain. You can now visit the URL to run your AI Worker. By completing this tutorial, you have created a Worker, connected it to Workers AI through an AI Gateway binding, and successfully ran an inference task using the Llama 3.1 model. Was this helpful? Edit page Last updated: Oct 9, 2025 Previous AI Gateway Binding Methods Next Tutorials Resources API New to Cloudflare? Directory Sponsorships Open Source Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Speed Test Is BGP Safe Yet? RPKI Toolkit Certificate Transparency Community X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings | 2026-01-13T09:30:12 |
https://developers.cloudflare.com/ai-gateway/observability/analytics/ | Analytics · Cloudflare AI Gateway docs Skip to content Cloudflare Docs Search Docs Directory APIs SDKs Help Log in Select theme Dark Light Auto AI Gateway No results found. Try a different search term, or use our global search . Overview Getting started Using AI Gateway Unified API (OpenAI compat) Provider Native Workers AI Amazon Bedrock Anthropic Azure OpenAI Baseten Cartesia Cerebras Cohere Deepgram DeepSeek ElevenLabs Fal AI Google AI Studio Google Vertex AI Groq HuggingFace Ideogram Mistral AI OpenAI OpenRouter Parallel Perplexity Replicate xAI WebSockets API Beta Overview Realtime WebSockets API Non-realtime WebSockets API Features Overview Unified Billing Caching Rate limiting Dynamic routing Beta Overview Using a dynamic route JSON Configuration Data Loss Prevention (DLP) Beta Overview Set up Data Loss Prevention (DLP) Guardrails Beta Overview Set up Guardrails Supported model types Usage considerations Configuration BYOK (Store Keys) Beta Custom costs Custom Providers Beta Manage gateways Request handling Authenticated Gateway Observability Costs Custom metadata Analytics Logging Overview Workers Logpush Integrations Vercel AI SDK Agents ↗ AI Gateway Binding Methods Workers AI Tutorials Platform Overview Limits Pricing Audit logs Changelog Header Glossary REST API reference ↗ API MCP server ↗ MCP AI Assistant ↗ Architectures LLM resources llms.txt prompt.txt AI Gateway llms-full.txt Developer Platform llms-full.txt GitHub X.com YouTube Select theme Dark Light Auto On this page Overview View analytics On this page Overview View analytics Was this helpful? Edit Issue Directory … AI Gateway Observability Analytics Copy page Analytics Your AI Gateway dashboard shows metrics on requests, tokens, caching, errors, and cost. You can filter these metrics by time. These analytics help you understand traffic patterns, token consumption, and potential issues across AI providers. You can view the following analytics: Requests : Track the total number of requests processed by AI Gateway. Token Usage : Analyze token consumption across requests, giving insight into usage patterns. Costs : Gain visibility into the costs associated with using different AI providers, allowing you to track spending, manage budgets, and optimize resources. Errors : Monitor the number of errors across the gateway, helping to identify and troubleshoot issues. Cached Responses : View the percentage of responses served from cache, which can help reduce costs and improve speed. View analytics Dashboard graphql To view analytics in the dashboard: Log into the Cloudflare dashboard ↗ and select your account. Go to AI > AI Gateway . Make sure you have your gateway selected. You can use GraphQL to query your usage data outside of the AI Gateway dashboard. See the example query below. You will need to use your Cloudflare token when making the request, and change {account_id} to match your account tag. Request curl https://api.cloudflare.com/client/v4/graphql \ --header 'Authorization: Bearer TOKEN \ --header 'Content-Type: application/json' \ --data '{ "query" : "query{\n viewer {\n accounts(filter: { accountTag: \" {account_id} \" }) {\n requests: aiGatewayRequestsAdaptiveGroups(\n limit: $limit \n filter: { datetimeHour_geq: $start , datetimeHour_leq: $end }\n orderBy: [datetimeMinute_ASC]\n ) {\n count,\n dimensions {\n model,\n provider,\n gateway,\n ts: datetimeMinute\n }\n \n }\n \n }\n }\n}", "variables" : { "limit" : 1000, "start" : "2023-09-01T10:00:00.000Z", "end" : "2023-09-30T10:00:00.000Z", "orderBy" : "date_ASC" } }' Was this helpful? Edit page Last updated: Aug 20, 2025 Previous Custom metadata Next Logging Resources API New to Cloudflare? Directory Sponsorships Open Source Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Speed Test Is BGP Safe Yet? RPKI Toolkit Certificate Transparency Community X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings | 2026-01-13T09:30:12 |
https://jitsi.org/ | Free Video Conferencing Software for Web & Mobile | Jitsi JaaS: the Team that Builds Jitsi Can Now Also Run it for You! Start now JaaS: the Team that Builds Jitsi Can Now Also Run it for You! Start now Docs Projects Blog Community About About Powered by Jitsi™ Partners Jitsi in the News User FAQ Download More secure, more flexible, and completely free video conferencing Learn more See it in Action! Start a Meeting Introducing Receiver Audio Subscriptions October 1, 2025 Jitsi Meet has had support for ReceiverConstraints for video for a long time. Receivers can specify which streams they wish to receive, and at what resolutions, and the backend will attempt to satisfy these constraints […] Read more GSoC 2025, let’s do this! February 28, 2025 We’re excited to share that Jitsi has been accepted into Google Summer of Code 2025! This is a great opportunity to get hands-on experience, collaborate with our awesome community, and contribute to the Jitsi open-source […] Read more Connecting anything to everything via SIP May 21, 2024 In the evolving landscape of virtual meetings, seamless connectivity remains paramount. SIP integration enables participants to join meetings from various devices, including hardware phones or softphones such as Bria, video conferencing systems such as Zoom, […] Read more Read all Blog articles The Tor Project @torproject If you want an alternative to Zoom: try Jitsi Meet. It’s encrypted, open source, and you don’t need an account. Meet Jitsi . tmcnet.com @tmcnet Italian Schools Using WeSchool Platform Based on 8×8’s Jitsi for Distance Learning. LangSciPress @LangSciPress Somewhat unexpected, but we now run our own videoconferencing software, #Jitsi It is 100% privacy friendly, 100% open source and runs on our own servers. Who is using Jitsi? Download Jitsi today. App Store Google Play F-Droid Frequently Asked Questions Read More Ask the Community Check It Out Jitsi is a trademark of © 8x8, Inc. All Rights Reserved. | 2026-01-13T09:30:12 |
https://extensionworkshop.com/documentation/publish/add-on-policies/#user-experience | Add-on Policies | Firefox Extension Workshop Extension Workshop Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Submit or Manage Extensions Search Submit or Manage Extensions Search Select a section Page Name Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents <a href="#know-your-privacy-se | 2026-01-13T09:30:12 |
https://www.epa.gov/haps/initial-list-hazardous-air-pollutants-modifications | Initial List of Hazardous Air Pollutants with Modifications | US EPA Skip to main content An official website of the United States government Here’s how you know Here’s how you know Official websites use .gov A .gov website belongs to an official government organization in the United States. Secure .gov websites use HTTPS A lock ( Lock A locked padlock ) or https:// means you’ve safely connected to the .gov website. Share sensitive information only on official, secure websites. JavaScript appears to be disabled on this computer. Please click here to see any active alerts . Menu Search Search Primary navigation Environmental Topics Environmental Topics Air Bed Bugs Chemicals, Toxics, and Pesticide Emergency Response Environmental Information by Location Health Land, Waste, and Cleanup Lead Mold Radon Research Science Topics Water Topics A-Z Topic Index Laws & Regulations Laws & Regulations By Business Sector By Topic Compliance Enforcement Guidance Laws and Executive Orders Regulations Report a Violation Report a Violation Environmental Violations Fraud, Waste or Abuse About EPA About EPA Our Mission and What We Do Headquarters Offices Regional Offices Labs and Research Centers Planning, Budget, and Results Organization Chart EPA History Breadcrumb Home Hazardous Air Pollutants Initial List of Hazardous Air Pollutants with Modifications Under the Clean Air Act, EPA is required to regulate emissions of hazardous air pollutants. This original list included 189 pollutants. Since 1990, EPA has modified the list through rulemaking to include 188 hazardous air pollutants. CAS Number Chemical Name 75070 Acetaldehyde 60355 Acetamide 75058 Acetonitrile 98862 Acetophenone 53963 2-Acetylaminofluorene 107028 Acrolein 79061 Acrylamide 79107 Acrylic acid 107131 Acrylonitrile 107051 Allyl chloride 92671 4-Aminobiphenyl 62533 Aniline 90040 o-Anisidine 1332214 Asbestos 71432 Benzene (including benzene from gasoline) 92875 Benzidine 98077 Benzotrichloride 100447 Benzyl chloride 92524 Biphenyl 117817 Bis(2-ethylhexyl)phthalate (DEHP) 542881 Bis(chloromethyl)ether 75252 Bromoform 106945 1-Bromopropane ( See Modification ) 106990 1,3-Butadiene 156627 Calcium cyanamide 105602 Caprolactam ( See Modification ) 133062 Captan 63252 Carbaryl 75150 Carbon disulfide 56235 Carbon tetrachloride 463581 Carbonyl sulfide 120809 Catechol 133904 Chloramben 57749 Chlordane 7782505 Chlorine 79118 Chloroacetic acid 532274 2-Chloroacetophenone 108907 Chlorobenzene 510156 Chlorobenzilate 67663 Chloroform 107302 Chloromethyl methyl ether 126998 Chloroprene 1319773 Cresols/Cresylic acid (isomers and mixture) 95487 o-Cresol 108394 m-Cresol 106445 p-Cresol 98828 Cumene 94757 2,4-D, salts and esters 3547044 DDE 334883 Diazomethane 132649 Dibenzofurans 96128 1,2-Dibromo-3-chloropropane 84742 Dibutylphthalate 106467 1,4-Dichlorobenzene(p) 91941 3,3-Dichlorobenzidene 111444 Dichloroethyl ether (Bis(2-chloroethyl)ether) 542756 1,3-Dichloropropene 62737 Dichlorvos 111422 Diethanolamine 121697 N,N-Dimethylaniline 64675 Diethyl sulfate 119904 3,3-Dimethoxybenzidine 60117 Dimethyl aminoazobenzene 119937 3,3'-Dimethyl benzidine 79447 Dimethyl carbamoyl chloride 68122 Dimethyl formamide 57147 1,1-Dimethyl hydrazine 131113 Dimethyl phthalate 77781 Dimethyl sulfate 534521 4,6-Dinitro-o-cresol, and salts 51285 2,4-Dinitrophenol 121142 2,4-Dinitrotoluene 123911 1,4-Dioxane (1,4-Diethyleneoxide) 122667 1,2-Diphenylhydrazine 106898 Epichlorohydrin (l-Chloro-2,3-epoxypropane) 106887 1,2-Epoxybutane 140885 Ethyl acrylate 100414 Ethyl benzene 51796 Ethyl carbamate (Urethane) 75003 Ethyl chloride (Chloroethane) 106934 Ethylene dibromide (Dibromoethane) 107062 Ethylene dichloride (1,2-Dichloroethane) 107211 Ethylene glycol 151564 Ethylene imine (Aziridine) 75218 Ethylene oxide 96457 Ethylene thiourea 75343 Ethylidene dichloride (1,1-Dichloroethane) 50000 Formaldehyde 76448 Heptachlor 118741 Hexachlorobenzene 87683 Hexachlorobutadiene 77474 Hexachlorocyclopentadiene 67721 Hexachloroethane 822060 Hexamethylene-1,6-diisocyanate 680319 Hexamethylphosphoramide 110543 Hexane 302012 Hydrazine 7647010 Hydrochloric acid 7664393 Hydrogen fluoride (Hydrofluoric acid) 7783064 Hydrogen sulfide ( See Modification ) 123319 Hydroquinone 78591 Isophorone 58899 Lindane (all isomers) 108316 Maleic anhydride 67561 Methanol 72435 Methoxychlor 74839 Methyl bromide (Bromomethane) 74873 Methyl chloride (Chloromethane) 71556 Methyl chloroform (1,1,1-Trichloroethane) 78933 Methyl ethyl ketone (2-Butanone) ( See Modification ) 60344 Methyl hydrazine 74884 Methyl iodide (Iodomethane) 108101 Methyl isobutyl ketone (Hexone) 624839 Methyl isocyanate 80626 Methyl methacrylate 1634044 Methyl tert butyl ether 101144 4,4-Methylene bis(2-chloroaniline) 75092 Methylene chloride (Dichloromethane) 101688 Methylene diphenyl diisocyanate (MDI) 101779 4,4'-Methylenedianiline 91203 Naphthalene 98953 Nitrobenzene 92933 4-Nitrobiphenyl 100027 4-Nitrophenol 79469 2-Nitropropane 684935 N-Nitroso-N-methylurea 62759 N-Nitrosodimethylamine 59892 N-Nitrosomorpholine 56382 Parathion 82688 Pentachloronitrobenzene (Quintobenzene) 87865 Pentachlorophenol 108952 Phenol 106503 p-Phenylenediamine 75445 Phosgene 7803512 Phosphine 7723140 Phosphorus 85449 Phthalic anhydride 1336363 Polychlorinated biphenyls (Aroclors) 1120714 1,3-Propane sultone 57578 beta-Propiolactone 123386 Propionaldehyde 114261 Propoxur (Baygon) 78875 Propylene dichloride (1,2-Dichloropropane) 75569 Propylene oxide 75558 1,2-Propylenimine (2-Methyl aziridine) 91225 Quinoline 106514 Quinone 100425 Styrene 96093 Styrene oxide 1746016 2,3,7,8-Tetrachlorodibenzo-p-dioxin 79345 1,1,2,2-Tetrachloroethane 127184 Tetrachloroethylene (Perchloroethylene) 7550450 Titanium tetrachloride 108883 Toluene 95807 2,4-Toluene diamine 584849 2,4-Toluene diisocyanate 95534 o-Toluidine 8001352 Toxaphene (chlorinated camphene) 120821 1,2,4-Trichlorobenzene 79005 1,1,2-Trichloroethane 79016 Trichloroethylene 95954 2,4,5-Trichlorophenol 88062 2,4,6-Trichlorophenol 121448 Triethylamine 1582098 Trifluralin 540841 2,2,4-Trimethylpentane 108054 Vinyl acetate 593602 Vinyl bromide 75014 Vinyl chloride 75354 Vinylidene chloride (1,1-Dichloroethylene) 1330207 Xylenes (isomers and mixture) 95476 o-Xylenes 108383 m-Xylenes 106423 p-Xylenes 0 Antimony Compounds 0 Arsenic Compounds (inorganic including arsine) 0 Beryllium Compounds 0 Cadmium Compounds 0 Chromium Compounds 0 Cobalt Compounds 0 Coke Oven Emissions 0 Cyanide Compounds 1 0 Glycol ethers 2 ( See Modification ) 0 Lead Compounds 0 Manganese Compounds 0 Mercury Compounds 0 Fine mineral fibers 3 0 Nickel Compounds 0 Polycyclic Organic Matter 4 0 Radionuclides (including radon) 5 0 Selenium Compounds NOTE: For all listings above which contain the word "compounds" and for glycol ethers, the following applies: Unless otherwise specified, these listings are defined as including any unique chemical substance that contains the named chemical (i.e., antimony, arsenic, etc.) as part of that chemical's infrastructure. 1 - X'CN where X = H' or any other group where a formal dissociation may occur. For example KCN or Ca(CN)2 2 - Includes mono- and di- ethers of ethylene glycol, diethylene glycol, and triethylene glycol R-(OCH2CH2)n -OR' where n = 1, 2, or 3 R = alkyl or aryl groups R' = R, H, or groups which, when removed, yield glycol ethers with the structure: R-(OCH2CH)n-OH. Polymers are excluded from the glycol category. ( See Modification ) 3 - Includes mineral fiber emissions from facilities manufacturing or processing glass, rock, or slag fibers (or other mineral derived fibers) of average diameter 1 micrometer or less. 4 - Includes organic compounds with more than one benzene ring, and which have a boiling point greater than or equal to 100 ºC. 5 - A type of atom which spontaneously undergoes radioactive decay. Hazardous Air Pollutants Open Sidenav Menu Close Sidenav Menu About Hazardous Air Pollutants expand or collapse the child menu What are Hazardous Air Pollutants? Health and Environmental Effects Sources and Exposure Reducing Emissions Urban Air Toxics expand or collapse the child menu About Urban Air Toxics Integrated Urban Air Toxics Strategy Pollutants Area Sources of Urban Air Toxics State/Local/Tribal Program Structure Reports to Congress Hazardous Air Pollutant Data and Control Strategies expand or collapse the child menu Air Toxics Data Update Contact Us About Hazardous Air Pollutants Contact Us About Hazardous Air Pollutants to ask a question, provide feedback, or report a problem. Last updated on December 18, 2025 Assistance Spanish Arabic Chinese (simplified) Chinese (traditional) French Haitian Creole Korean Portuguese Russian Tagalog Vietnamese Discover. Accessibility Statement EPA Administrator Budget & Performance Contracting EPA www Web Snapshot Grants No FEAR Act Data Plain Writing Privacy and Security Notice Connect. Data Inspector General Jobs Newsroom Regulations.gov Subscribe USA.gov White House Ask. Contact EPA EPA Disclaimers Hotlines FOIA Requests Frequent Questions Site Feedback Follow. | 2026-01-13T09:30:12 |
https://developers.cloudflare.com/ai-gateway/features/caching/ | Caching · Cloudflare AI Gateway docs Skip to content Cloudflare Docs Search Docs Directory APIs SDKs Help Log in Select theme Dark Light Auto AI Gateway No results found. Try a different search term, or use our global search . Overview Getting started Using AI Gateway Unified API (OpenAI compat) Provider Native Workers AI Amazon Bedrock Anthropic Azure OpenAI Baseten Cartesia Cerebras Cohere Deepgram DeepSeek ElevenLabs Fal AI Google AI Studio Google Vertex AI Groq HuggingFace Ideogram Mistral AI OpenAI OpenRouter Parallel Perplexity Replicate xAI WebSockets API Beta Overview Realtime WebSockets API Non-realtime WebSockets API Features Overview Unified Billing Caching Rate limiting Dynamic routing Beta Overview Using a dynamic route JSON Configuration Data Loss Prevention (DLP) Beta Overview Set up Data Loss Prevention (DLP) Guardrails Beta Overview Set up Guardrails Supported model types Usage considerations Configuration BYOK (Store Keys) Beta Custom costs Custom Providers Beta Manage gateways Request handling Authenticated Gateway Observability Costs Custom metadata Analytics Logging Overview Workers Logpush Integrations Vercel AI SDK Agents ↗ AI Gateway Binding Methods Workers AI Tutorials Platform Overview Limits Pricing Audit logs Changelog Header Glossary REST API reference ↗ API MCP server ↗ MCP AI Assistant ↗ Architectures LLM resources llms.txt prompt.txt AI Gateway llms-full.txt Developer Platform llms-full.txt GitHub X.com YouTube Select theme Dark Light Auto On this page Overview Benefits of Using Caching Default configuration Per-request caching Skip cache (cf-aig-skip-cache) Cache TTL (cf-aig-cache-ttl) Custom cache key (cf-aig-cache-key) On this page Overview Benefits of Using Caching Default configuration Per-request caching Skip cache (cf-aig-skip-cache) Cache TTL (cf-aig-cache-ttl) Custom cache key (cf-aig-cache-key) Was this helpful? Edit Issue Directory … AI Gateway Features Caching Copy page Caching AI Gateway can cache responses from your AI model providers, serving them directly from Cloudflare's cache for identical requests. Benefits of Using Caching Reduced Latency: Serve responses faster to your users by avoiding a round trip to the origin AI provider for repeated requests. Cost Savings: Minimize the number of paid requests made to your AI provider, especially for frequently accessed or non-dynamic content. Increased Throughput: Offload repetitive requests from your AI provider, allowing it to handle unique requests more efficiently. Note Currently caching is supported only for text and image responses, and it applies only to identical requests. This configuration benefits use cases with limited prompt options. For example, a support bot that asks "How can I help you?" and lets the user select an answer from a limited set of options works well with the current caching configuration. We plan on adding semantic search for caching in the future to improve cache hit rates. Default configuration Dashboard API To set the default caching configuration in the dashboard: Log into the Cloudflare dashboard ↗ and select your account. Select AI > AI Gateway . Select Settings . Enable Cache Responses . Change the default caching to whatever value you prefer. To set the default caching configuration using the API: Create an API token with the following permissions: AI Gateway - Read AI Gateway - Edit Get your Account ID . Using that API token and Account ID, send a POST request to create a new Gateway and include a value for the cache_ttl . This caching behavior will be uniformly applied to all requests that support caching. If you need to modify the cache settings for specific requests, you have the flexibility to override this setting on a per-request basis. To check whether a response comes from cache or not, cf-aig-cache-status will be designated as HIT or MISS . Per-request caching While your gateway's default cache settings provide a good baseline, you might need more granular control. These situations could be data freshness, content with varying lifespans, or dynamic or personalized responses. To address these needs, AI Gateway allows you to override default cache behaviors on a per-request basis using specific HTTP headers. This gives you the precision to optimize caching for individual API calls. The following headers allow you to define this per-request cache behavior: Note The following headers have been updated to new names, though the old headers will still function. We recommend updating to the new headers to ensure future compatibility: cf-cache-ttl is now cf-aig-cache-ttl cf-skip-cache is now cf-aig-skip-cache Skip cache (cf-aig-skip-cache) Skip cache refers to bypassing the cache and fetching the request directly from the original provider, without utilizing any cached copy. You can use the header cf-aig-skip-cache to bypass the cached version of the request. As an example, when submitting a request to OpenAI, include the header in the following manner: Request skipping the cache curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/openai/chat/completions \ --header "Authorization: Bearer $TOKEN " \ --header 'Content-Type: application/json' \ --header 'cf-aig-skip-cache: true' \ --data ' { "model": "gpt-4o-mini", "messages": [ { "role": "user", "content": "how to build a wooden spoon in 3 short steps? give as short as answer as possible" } ] } ' Cache TTL (cf-aig-cache-ttl) Cache TTL, or Time To Live, is the duration a cached request remains valid before it expires and is refreshed from the original source. You can use cf-aig-cache-ttl to set the desired caching duration in seconds. The minimum TTL is 60 seconds and the maximum TTL is one month. For example, if you set a TTL of one hour, it means that a request is kept in the cache for an hour. Within that hour, an identical request will be served from the cache instead of the original API. After an hour, the cache expires and the request will go to the original API for a fresh response, and that response will repopulate the cache for the next hour. As an example, when submitting a request to OpenAI, include the header in the following manner: Request to be cached for an hour curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/openai/chat/completions \ --header "Authorization: Bearer $TOKEN " \ --header 'Content-Type: application/json' \ --header 'cf-aig-cache-ttl: 3600' \ --data ' { "model": "gpt-4o-mini", "messages": [ { "role": "user", "content": "how to build a wooden spoon in 3 short steps? give as short as answer as possible" } ] } ' Custom cache key (cf-aig-cache-key) Custom cache keys let you override the default cache key in order to precisely set the cacheability setting for any resource. To override the default cache key, you can use the header cf-aig-cache-key . When you use the cf-aig-cache-key header for the first time, you will receive a response from the provider. Subsequent requests with the same header will return the cached response. If the cf-aig-cache-ttl header is used, responses will be cached according to the specified Cache Time To Live. Otherwise, responses will be cached according to the cache settings in the dashboard. If caching is not enabled for the gateway, responses will be cached for 5 minutes by default. As an example, when submitting a request to OpenAI, include the header in the following manner: Request with custom cache key curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/openai/chat/completions \ --header 'Authorization: Bearer {openai_token}' \ --header 'Content-Type: application/json' \ --header 'cf-aig-cache-key: responseA' \ --data ' { "model": "gpt-4o-mini", "messages": [ { "role": "user", "content": "how to build a wooden spoon in 3 short steps? give as short as answer as possible" } ] } ' AI Gateway caching behavior Cache in AI Gateway is volatile. If two identical requests are sent simultaneously, the first request may not cache in time for the second request to use it, which may result in the second request retrieving data from the original source. Was this helpful? Edit page Last updated: Aug 19, 2025 Previous Unified Billing Next Rate limiting Resources API New to Cloudflare? Directory Sponsorships Open Source Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Speed Test Is BGP Safe Yet? RPKI Toolkit Certificate Transparency Community X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings | 2026-01-13T09:30:12 |
https://developers.cloudflare.com/ai-gateway/usage/providers/vertex/ | Google Vertex AI · Cloudflare AI Gateway docs Skip to content Cloudflare Docs Search Docs Directory APIs SDKs Help Log in Select theme Dark Light Auto AI Gateway No results found. Try a different search term, or use our global search . Overview Getting started Using AI Gateway Unified API (OpenAI compat) Provider Native Workers AI Amazon Bedrock Anthropic Azure OpenAI Baseten Cartesia Cerebras Cohere Deepgram DeepSeek ElevenLabs Fal AI Google AI Studio Google Vertex AI Groq HuggingFace Ideogram Mistral AI OpenAI OpenRouter Parallel Perplexity Replicate xAI WebSockets API Beta Overview Realtime WebSockets API Non-realtime WebSockets API Features Overview Unified Billing Caching Rate limiting Dynamic routing Beta Overview Using a dynamic route JSON Configuration Data Loss Prevention (DLP) Beta Overview Set up Data Loss Prevention (DLP) Guardrails Beta Overview Set up Guardrails Supported model types Usage considerations Configuration BYOK (Store Keys) Beta Custom costs Custom Providers Beta Manage gateways Request handling Authenticated Gateway Observability Costs Custom metadata Analytics Logging Overview Workers Logpush Integrations Vercel AI SDK Agents ↗ AI Gateway Binding Methods Workers AI Tutorials Platform Overview Limits Pricing Audit logs Changelog Header Glossary REST API reference ↗ API MCP server ↗ MCP AI Assistant ↗ Architectures LLM resources llms.txt prompt.txt AI Gateway llms-full.txt Developer Platform llms-full.txt GitHub X.com YouTube Select theme Dark Light Auto On this page Overview Endpoint Prerequisites URL structure Authenticating with Vertex AI Option 1: Service Account JSON Option 2: Direct Access Token Using Unified Chat Completions API Endpoint Example with OpenAI SDK Example with cURL Using Provider-Specific Endpoint cURL On this page Overview Endpoint Prerequisites URL structure Authenticating with Vertex AI Option 1: Service Account JSON Option 2: Direct Access Token Using Unified Chat Completions API Endpoint Example with OpenAI SDK Example with cURL Using Provider-Specific Endpoint cURL Was this helpful? Edit Issue Directory … AI Gateway Using AI Gateway Provider Native Google Vertex AI Copy page Google Vertex AI Google Vertex AI ↗ enables developers to easily build and deploy enterprise ready generative AI experiences. Below is a quick guide on how to set your Google Cloud Account: Google Cloud Platform (GCP) Account Sign up for a GCP account ↗ . New users may be eligible for credits (valid for 90 days). Enable the Vertex AI API Navigate to Enable Vertex AI API ↗ and activate the API for your project. Apply for access to desired models. Endpoint https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/google-vertex-ai Prerequisites When making requests to Google Vertex, you will need: AI Gateway account tag AI Gateway gateway name Google Vertex API key Google Vertex Project Name Google Vertex Region (for example, us-east4) Google Vertex model URL structure Your new base URL will use the data above in this structure: https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/google-vertex-ai/v1/projects/{project_name}/locations/{region} . Then you can append the endpoint you want to hit, for example: /publishers/google/models/{model}:{generative_ai_rest_resource} So your final URL will come together as: https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/google-vertex-ai/v1/projects/{project_name}/locations/{region}/publishers/google/models/gemini-2.5-flash:generateContent Authenticating with Vertex AI Authenticating with Vertex AI normally requires generating short-term credentials using the Google Cloud SDKs ↗ with a complicated setup, but AI Gateway simplifies this for you with multiple options: Option 1: Service Account JSON AI Gateway supports passing a Google service account JSON directly in the Authorization header on requests or through AI Gateway's Bring Your Own Keys feature. You can create a service account key ↗ in the Google Cloud Console. Ensure that the service account has the required permissions for the Vertex AI endpoints and models you plan to use. AI Gateway uses your service account JSON to generate short-term access tokens which are cached and used for consecutive requests, and are automatically refreshed when they expire. Note The service account JSON must include an additional key called region with the GCP region code (for example, us-east1 ) you intend to use for your Vertex AI endpoint ↗ . You can also pass the region code global to use the global endpoint. Example service account JSON structure { " type " : "service_account" , " project_id " : "your-project-id" , " private_key_id " : "your-private-key-id" , " private_key " : "-----BEGIN PRIVATE KEY----- \n YOUR_PRIVATE_KEY \n -----END PRIVATE KEY----- \n " , " client_email " : "your-service-account@your-project.iam.gserviceaccount.com" , " client_id " : "your-client-id" , " auth_uri " : "https://accounts.google.com/o/oauth2/auth" , " token_uri " : "https://oauth2.googleapis.com/token" , " auth_provider_x509_cert_url " : "https://www.googleapis.com/oauth2/v1/certs" , " client_x509_cert_url " : "https://www.googleapis.com/robot/v1/metadata/x509/your-service-account%40your-project.iam.gserviceaccount.com" , " region " : "us-east1" } You can pass this JSON in the Authorization header or configure it in Bring Your Own Keys . Option 2: Direct Access Token If you are already using the Google Cloud SDKs and generating a short-term access token (for example, with gcloud auth print-access-token ), you can directly pass this as a Bearer token in the Authorization header of the request. Note This option is only supported for the provider-specific endpoint, not for the unified chat completions endpoint. Terminal window curl "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/google-vertex-ai/v1/projects/{project_name}/locations/{region}/publishers/google/models/gemini-2.5-flash:generateContent" \ -H "Authorization: Bearer ya29.c.b0Aaekm1K..." \ -H 'Content-Type: application/json' \ -d '{ "contents": { "role": "user", "parts": [ { "text": "Tell me more about Cloudflare" } ] } }' Using Unified Chat Completions API AI Gateway provides a Unified API that works across providers. For Google Vertex AI, you can use the standard chat completions format. Note that the model field includes the provider prefix, so your model string will look like google-vertex-ai/google/gemini-2.5-pro . Endpoint https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions Example with OpenAI SDK JavaScript import OpenAI from 'openai' ; const client = new OpenAI ( { apiKey : '{service_account_json}' , baseURL : 'https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat' } ) ; const response = await client . chat . completions . create ( { model : 'google-vertex-ai/google/gemini-2.5-pro' , messages : [ { role : 'user' , content : 'What is Cloudflare?' } ] } ) ; console . log ( response . choices [ 0 ] . message . content ) ; Example with cURL Terminal window curl "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions" \ -H "Authorization: Bearer {service_account_json}" \ -H 'Content-Type: application/json' \ -d '{ "model": "google-vertex-ai/google/gemini-2.5-pro", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] }' Note See the Authenticating with Vertex AI section below for details on the service account JSON structure and authentication options. Using Provider-Specific Endpoint You can also use the provider-specific endpoint to access the full Vertex AI API. cURL Example fetch request curl "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/google-vertex-ai/v1/projects/{project_name}/locations/{region}/publishers/google/models/gemini-2.5-flash:generateContent" \ -H "Authorization: Bearer {vertex_api_key}" \ -H 'Content-Type: application/json' \ -d '{ "contents": { "role": "user", "parts": [ { "text": "Tell me more about Cloudflare" } ] }' Was this helpful? Edit page Last updated: Nov 24, 2025 Previous Google AI Studio Next Groq Resources API New to Cloudflare? Directory Sponsorships Open Source Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Speed Test Is BGP Safe Yet? RPKI Toolkit Certificate Transparency Community X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings | 2026-01-13T09:30:12 |
https://developers.cloudflare.com/ai-gateway/integrations/vercel-ai-sdk/ | Vercel AI SDK · Cloudflare AI Gateway docs Skip to content Cloudflare Docs Search Docs Directory APIs SDKs Help Log in Select theme Dark Light Auto AI Gateway No results found. Try a different search term, or use our global search . Overview Getting started Using AI Gateway Unified API (OpenAI compat) Provider Native Workers AI Amazon Bedrock Anthropic Azure OpenAI Baseten Cartesia Cerebras Cohere Deepgram DeepSeek ElevenLabs Fal AI Google AI Studio Google Vertex AI Groq HuggingFace Ideogram Mistral AI OpenAI OpenRouter Parallel Perplexity Replicate xAI WebSockets API Beta Overview Realtime WebSockets API Non-realtime WebSockets API Features Overview Unified Billing Caching Rate limiting Dynamic routing Beta Overview Using a dynamic route JSON Configuration Data Loss Prevention (DLP) Beta Overview Set up Data Loss Prevention (DLP) Guardrails Beta Overview Set up Guardrails Supported model types Usage considerations Configuration BYOK (Store Keys) Beta Custom costs Custom Providers Beta Manage gateways Request handling Authenticated Gateway Observability Costs Custom metadata Analytics Logging Overview Workers Logpush Integrations Vercel AI SDK Agents ↗ AI Gateway Binding Methods Workers AI Tutorials Platform Overview Limits Pricing Audit logs Changelog Header Glossary REST API reference ↗ API MCP server ↗ MCP AI Assistant ↗ Architectures LLM resources llms.txt prompt.txt AI Gateway llms-full.txt Developer Platform llms-full.txt GitHub X.com YouTube Select theme Dark Light Auto On this page Overview Installation Examples Fallback Providers On this page Overview Installation Examples Fallback Providers Was this helpful? Edit Issue Directory … AI Gateway Integrations Vercel AI SDK Copy page Vercel AI SDK The Vercel AI SDK ↗ is a TypeScript library for building AI applications. The SDK supports many different AI providers, tools for streaming completions, and more. To use Cloudflare AI Gateway with Vercel AI SDK, you will need to use the ai-gateway-provider package. Installation Terminal window npm install ai-gateway-provider Examples Make a request to OpenAI Unified API with Stored Key (BYOK) import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified () ; const { text } = await generateText ( { model : aigateway ( unified ( 'openai/gpt-5.2' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified () ; const { text } = await generateText ( { model : aigateway ( unified ( 'anthropic/claude-4-5-sonnet' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified () ; const { text } = await generateText ( { model : aigateway ( unified ( 'google/gemini-2.5-pro' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified () ; const { text } = await generateText ( { model : aigateway ( unified ( 'grok/grok-4' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified () ; const { text } = await generateText ( { model : aigateway ( unified ( 'dynamic/customer-support' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified () ; const { text } = await generateText ( { model : aigateway ( unified ( 'workers-ai/@cf/meta/llama-3.3-70b-instruct-fp8-fast' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( unified ( 'openai/gpt-5.2' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( unified ( 'anthropic/claude-4-5-sonnet' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( unified ( 'google/gemini-2.5-pro' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( unified ( 'grok/grok-4' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( unified ( 'dynamic/customer-support' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( unified ( 'workers-ai/@cf/meta/llama-3.3-70b-instruct-fp8-fast' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createOpenAI } from 'ai-gateway-provider/providers/openai' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const openai = createOpenAI () ; const { text } = await generateText ( { model : aigateway ( openai . chat ( 'gpt-5.2' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createAnthropic } from 'ai-gateway-provider/providers/anthropic' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const anthropic = createAnthropic () ; const { text } = await generateText ( { model : aigateway ( anthropic ( 'claude-4-5-sonnet' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createGoogle } from 'ai-gateway-provider/providers/google' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const google = createGoogle () ; const { text } = await generateText ( { model : aigateway ( google ( 'gemini-2.5-pro' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createXai } from 'ai-gateway-provider/providers/xai' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const xai = createXai () ; const { text } = await generateText ( { model : aigateway ( xai ( 'grok-4' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified () ; const { text } = await generateText ( { model : aigateway ( unified ( 'customer-support' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified () ; const { text } = await generateText ( { model : aigateway ( unified ( '@cf/meta/llama-3.3-70b-instruct-fp8-fast' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createOpenAI } from 'ai-gateway-provider/providers/openai' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const openai = createOpenAI ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( openai . chat ( 'gpt-5.2' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createAnthropic } from 'ai-gateway-provider/providers/anthropic' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const anthropic = createAnthropic ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( anthropic ( 'claude-4-5-sonnet' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createGoogle } from 'ai-gateway-provider/providers/google' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const google = createGoogle ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( google ( 'gemini-2.5-pro' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createXai } from 'ai-gateway-provider/providers/xai' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const xai = createXai ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( xai ( 'grok-4' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( unified ( 'customer-support' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( unified ( '@cf/meta/llama-3.3-70b-instruct-fp8-fast' )) , prompt : 'What is Cloudflare?' , } ) ; Fallback Providers To specify model or provider fallbacks to handle request failures and ensure reliability, you can pass an array of models to the model option. const { text } = await generateText ( { model : aigateway ([ openai . chat ( "gpt-5.1" ) , anthropic ( "claude-sonnet-4-5" ) ]) , prompt : 'Write a vegetarian lasagna recipe for 4 people.' , } ) ; Was this helpful? Edit page Last updated: Jan 7, 2026 Previous Workers Logpush Next Agents ↗ Resources API New to Cloudflare? Directory Sponsorships Open Source Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Speed Test Is BGP Safe Yet? RPKI Toolkit Certificate Transparency Community X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings | 2026-01-13T09:30:12 |
https://developers.cloudflare.com/ai-gateway/usage/providers/deepseek/ | DeepSeek · Cloudflare AI Gateway docs Skip to content Cloudflare Docs Search Docs Directory APIs SDKs Help Log in Select theme Dark Light Auto AI Gateway No results found. Try a different search term, or use our global search . Overview Getting started Using AI Gateway Unified API (OpenAI compat) Provider Native Workers AI Amazon Bedrock Anthropic Azure OpenAI Baseten Cartesia Cerebras Cohere Deepgram DeepSeek ElevenLabs Fal AI Google AI Studio Google Vertex AI Groq HuggingFace Ideogram Mistral AI OpenAI OpenRouter Parallel Perplexity Replicate xAI WebSockets API Beta Overview Realtime WebSockets API Non-realtime WebSockets API Features Overview Unified Billing Caching Rate limiting Dynamic routing Beta Overview Using a dynamic route JSON Configuration Data Loss Prevention (DLP) Beta Overview Set up Data Loss Prevention (DLP) Guardrails Beta Overview Set up Guardrails Supported model types Usage considerations Configuration BYOK (Store Keys) Beta Custom costs Custom Providers Beta Manage gateways Request handling Authenticated Gateway Observability Costs Custom metadata Analytics Logging Overview Workers Logpush Integrations Vercel AI SDK Agents ↗ AI Gateway Binding Methods Workers AI Tutorials Platform Overview Limits Pricing Audit logs Changelog Header Glossary REST API reference ↗ API MCP server ↗ MCP AI Assistant ↗ Architectures LLM resources llms.txt prompt.txt AI Gateway llms-full.txt Developer Platform llms-full.txt GitHub X.com YouTube Select theme Dark Light Auto On this page Overview Endpoint Prerequisites URL structure Examples cURL Use DeepSeek with JavaScript OpenAI-Compatible Endpoint On this page Overview Endpoint Prerequisites URL structure Examples cURL Use DeepSeek with JavaScript OpenAI-Compatible Endpoint Was this helpful? Edit Issue Directory … AI Gateway Using AI Gateway Provider Native DeepSeek Copy page DeepSeek DeepSeek ↗ helps you build quickly with DeepSeek's advanced AI models. Endpoint https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/deepseek Prerequisites When making requests to DeepSeek, ensure you have the following: Your AI Gateway Account ID. Your AI Gateway gateway name. An active DeepSeek AI API token. The name of the DeepSeek AI model you want to use. URL structure Your new base URL will use the data above in this structure: https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/deepseek/ . You can then append the endpoint you want to hit, for example: chat/completions . So your final URL will come together as: https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/deepseek/chat/completions . Examples cURL Example fetch request curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/deepseek/chat/completions \ --header 'content-type: application/json' \ --header 'Authorization: Bearer DEEPSEEK_TOKEN' \ --data '{ "model": "deepseek-chat", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] }' Use DeepSeek with JavaScript If you are using the OpenAI SDK, you can set your endpoint like this: JavaScript import OpenAI from "openai" ; const openai = new OpenAI ( { apiKey : env . DEEPSEEK_TOKEN , baseURL : "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/deepseek" , } ) ; try { const chatCompletion = await openai . chat . completions . create ( { model : "deepseek-chat" , messages : [ { role : "user" , content : "What is Cloudflare?" } ] , } ) ; const response = chatCompletion . choices [ 0 ] . message ; return new Response ( JSON . stringify ( response )) ; } catch ( e ) { return new Response ( e ) ; } OpenAI-Compatible Endpoint You can also use the OpenAI-compatible endpoint ( /ai-gateway/usage/chat-completion/ ) to access DeepSeek models using the OpenAI API schema. To do so, send your requests to: https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions Specify: { " model " : "deepseek/{model}" } Was this helpful? Edit page Last updated: Nov 24, 2025 Previous Deepgram Next ElevenLabs Resources API New to Cloudflare? Directory Sponsorships Open Source Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Speed Test Is BGP Safe Yet? RPKI Toolkit Certificate Transparency Community X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings | 2026-01-13T09:30:12 |
https://extensionworkshop.com/documentation/publish/add-on-policies/#test-and-debug | Add-on Policies | Firefox Extension Workshop Extension Workshop Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Submit or Manage Extensions Search Submit or Manage Extensions Search Select a section Page Name Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise <a href="https://support.mozilla.org/kb | 2026-01-13T09:30:12 |
https://extensionworkshop.com/documentation/publish/add-on-policies/#developer-preview-changes | Add-on Policies | Firefox Extension Workshop Extension Workshop Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Submit or Manage Extensions Search Submit or Manage Extensions Search Select a section Page Name Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Add-on Policies Add-ons extend the core capabilities of Firefox, enabling users to modify and personalize their web experience. A healthy ecosystem, built on trust, is vital for developers to be successful and users to feel safe making Firefox their own. For these reasons, Mozilla requires all add-ons to comply with the following policies. These policies are not intended to serve as legal advice: depending on where you are located, additional requirements may apply. All add-ons are subject to these policies, regardless of how they are distributed. When an add-on is given human review or otherwise assessed by Mozilla, these policies act as guiding principles for those reviews. Add-ons that do not comply with these policies may be rejected or disabled by Mozilla. Contents No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking No Surprises Users should be able to easily discern the functionality of your add-on based on the listing, and should not be presented with unexpected user experiences after installing it. The listing should include an easy-to-read description of what the add-on does, and what information it transmits. Please consult our best practices guide for creating an appealing listing . Unexpected features “Unexpected” features are those that are unrelated to the add-on’s primary function, and are not clearly indicated by the add-on name or description. This may include features that impact user privacy or security, make unexpected changes to web content, or change default settings like the new tab page, homepage, or search engine. Any “unexpected” feature(s) must adhere to all of the following requirements: The add-on description must clearly state any changes made by these features. The features must be “opt-in”, meaning the user has to take non-default action to enact the change. Changes prompted by Firefox after the add-on is installed do not require an additional opt-in. The permissions prompt shown when installing an add-on does not alleviate the need for an opt-in. The opt-in interface must clearly state the name of the add-on requesting the change. Content Add-ons that make use of Mozilla trademarks must comply with the Mozilla Trademark Guidelines . If the add-on uses “Firefox” in its name, the naming standard the add-on is expected to follow is “<Add-on name> for Firefox”. In addition, add-ons listed on addons.mozilla.org must adhere to the following policies: All add-ons submitted for listing on addons.mozilla.org are subject to Mozilla’s Acceptable Use Policy . Listings must disclose when payment is required to enable any add-on functionality. Add-ons and their content must conform to the laws of the United States. (Add-ons that violate or have content that violates the law in other jurisdictions may also be removed or have access limited.) If the add-on is a fork of another add-on, the name must clearly distinguish it from the original and provide a significant difference in functionality and/or code. Add-ons with the sole purpose of promoting, installing, loading or launching an outside website, application or add-on are not permitted. Themes that feature low-quality, stretched, or blank images, as well as those themes in which the header image is misaligned, are not permitted. Duplicate themes are not permitted. Submission Guidelines Add-ons must function only as described. During review, the add-on undergoes basic functional testing in addition to code review. To facilitate the functional testing, the add-on author must provide testing information and, if an account is needed for any part of the add-on’s functionality, testing credentials to allow use of the add-on. If corrections have been requested and are submitted as part of a new version, the new version should not contain unrelated changes, as this complicates the review process and can lead to further delays or rejections. Source Code Submission Code must be provided in a way that is reviewable. Add-ons may contain transpiled, minified or otherwise machine-generated code, but Mozilla needs to review a copy of the source code before any of these steps have been applied. The author must provide this information to Mozilla during submission along with instructions on how to reproduce the build. All dependencies must either be included in the source code package directly or downloaded only through the respective official package managers during the build process. Build tools or environments that no longer appear to be supported by their maintainers are not accepted. Reviewers may ask you to refactor parts of the code if it is not reviewable. The provided source code is reviewed by an administrator and is not redistributed in any way. The code is only used for the purpose of reviewing the add-on. Failure to provide this information results in rejection or blocking. Add-ons are not allowed to contain obfuscated code, nor code that hides the purpose of the functionality involved. If external resources are used in combination with add-on code, the functionality of the code must not be obscured. Minification of code with the intent to reduce file size is permitted. Please read our Source Code Submission guidelines to avoid unexpected rejections or blocks. Development Practices In general, developers are free to maintain their add-ons in the manner they choose. However, in order to maintain appropriate data security measures and allow us to effectively review code, we have certain technical requirements that all add-ons must meet. In particular, potentially dangerous APIs may only be used in ways that are demonstrably safe, and code within add-ons that cannot be verified as behaving safely and correctly may need to be refactored. The following requirements are of particular importance: Add-ons must only request those permissions that are necessary for them to function. Add-ons must be self-contained and not load remote code for execution. Add-ons must not load or redirect to a remote new tab page. The new tab page must be contained within the add-on. Add-ons must not relax web page security headers, such as the Content Security Policy. Add-ons must use encryption when transporting data remotely. Add-ons should avoid including redundant code or files. Add-ons must not negatively impact the performance or stability of Firefox. Only release versions of third-party libraries and/or frameworks may be included with an add-on. Modifications to these libraries/frameworks are not permitted. Please read our third party library guidelines to better understand related requirements. User Scripts Usage of the userScripts API is allowed for user script managers only. A user script manager is an extension that allows users to manage website-specific scripts. The userScripts API cannot be used to extend or modify the functionality of the user script manager itself. The user must: Proactively install a user script using an explicit action, for instance a click on a button labeled “Install this user script”. Be able to see which user scripts are currently installed and remove scripts without impacting the extension. Data Collection and Transmission Disclosure and Control Add-ons must limit data transmission to what is necessary for functionality, and must use the data only for the purpose for which it was transmitted. For the purposes of this policy, data transmission refers to any data that is collected, used, transferred, shared, or handled outside of the add-on or the local browser. If the add-on uses native messaging, the Add-on Policies (including those related to user consent and control) apply to any data sent to the native application as well. Prohibited Data Collection and Transmission Search functionality provided or loaded by the add-on must not transmit search terms or intercept searches that are going to a third-party search provider. Transmitting or facilitating the transmission of ancillary information (e.g. any data not required for the add-on’s functionality as stated in the description) is prohibited. The transmission of browsing activity is only permitted as part of the add-on’s primary function. User Consent and Control The user must be provided with a clear way to control the add-on’s data transmission, either through a consent experience created by the add-on developer, or by using Firefox’s built in data collection and transmission consent experience. In the case of add-ons that qualify for implicit consent, under the “Implicit Consent for Self-Evident, Single-Use Extension” policy, installation is the consent. Add-ons installed in an enterprise environment can bypass asking for data collection consent when they are installed by enterprise policy. For more information, refer to the enterprise documentation . If the add-on uses Firefox’s built-in data collection and transmission consent experience, then the browser will bypass this by default. If the add-on is only compatible with Firefox 140 or later and uses Firefox’s built-in data collection and transmission consent experience: It must accurately state the data collection practices in the extension manifest, including when it does not collect data, in line with the Firefox add-on data classification taxonomy . If the add-on is compatible with Firefox 139 and earlier or does not use Firefox’s built-in data collection and transmission consent experience: The user must be provided with a clear way to control the add-on’s data transmission immediately after installation of the add-on. If data transmission starts or changes in an add-on update, or the consent and control is introduced in an update, it must be shown to all new and upgrading users immediately after the update. The data transmission consent and control must be contained within the add-on. The consent experience must: Be unmissable. It is recommended to present it in a new focused tab in the current window. Other ways that could be missed or accidentally hidden, like a popup window, will result in a rejection. Be presented on a single page, including all choices and decision options. Present users with a clear, readable data transmission consent. Information explaining the data transmitted must be prominently stated and not buried or hidden. Avoid deceptive design patterns that make it harder to understand your data transmission policy, including, but not limited to, illegible font sizes, reduced color contrast, hidden options, multi-step consent decline flows, and similar techniques indicative of deceptive design. Clearly state what type of data is being transmitted. Inform about the impact of accepting or declining the data transmission If both personal and technical data is being transmitted, the user must be provided separate choices. If the user declines the transmission, any resulting impact on their experience or use of the add-on must be limited to the data not being available. Please refer to our best practices for advice and examples on how to design and implement a data transmission consent prompt. Personal Data (opt-in) Personally identifiable information can be actively provided by the user or obtained through extension APIs. It includes, but is not limited to names, email addresses, search terms and browsing activity data, as well as access to and placement of cookies. Before an add-on may transmit personal information, it must clearly describe, and the user must affirmatively consent (i.e., explicitly opt-in) to the type of personal data being transmitted. If the primary function of the add-on does not work without transmitting personal data, the add-on must provide a choice for the user to either accept the data transmission or uninstall the add-on. Implicit Consent for Self-Evident, Single-Use Extension Implicit consent applies only to add-ons hosted on addons.mozilla.org when all of the following conditions are satisfied. Otherwise the standard explicit consent rules apply. Conditions Purpose-bounded and user-initiated – Data may be transmitted only as a direct, immediate consequence of a single, deliberate user command (for example, a click or tap) on a clearly labelled control supplied by the browser or the add-on. Any passive, continuous, or background transmission requires explicit consent. Self-evident listing disclosure – The add-ons name and addons.mozilla.org listing must, in combination, make it clear what data will be transmitted and why, consistent with the “No Surprises” policy. Self-evident user interface – At the point of interaction, the in-product UI must plainly signal which data will be sent and to what type of service, so the user can foresee the consequence of their action without additional prompts. Purpose-limited data scope – The transmission: a. is strictly limited to the content element the user acted upon (for example, selected text, current page URL, chosen file or image); and b. must not include persistent identifiers, analytics beacons, cookies, advertising IDs, or any data unrelated to completing the primary function of the add-on. Transmission of certain data requires explicit consent, regardless of the above. For more information, refer to the Firefox add-on data classification taxonomy . Review authority – Mozilla reviewers may require the add-on to obtain explicit user consent if they judge an add-on’s disclosure inadequate or detect attempts to broaden data collection. When all the above conditions are met, invoking the primary function is deemed implicit consent for transmitting the user-supplied data needed to perform that function. No additional dialog needs to be shown at install time. If any other data is transmitted, explicit consent at time of install is required. Technical & User Interaction Data (opt-out) Technical data describes information about the environment the user is running, such as browser settings, platform information and hardware properties. User interaction data includes how the user interacts with Firefox and the installed add-ons, metrics for product improvement, and error information. When an add-on transmits either of these types of information, it must allow the user to disable that data transmission (opt-out) during the initial consent experience. The add-on functionality must not be restricted if the user declines transmission of this data. Additional Privacy Protocols Leaking local or user-specific information to websites or other applications (e.g. through native messaging) is prohibited. Data from private browsing sessions must not be stored. Information that identifies a user across browsing sessions or containers must not be made available to web content. Monetization An add-on injecting advertising into web page content must clearly identify the injected content as originating from the add-on. The inclusion of any cryptocurrency miners in an add-on is prohibited. Modifying web content or facilitating redirects to include affiliate promotion tags is not permitted. Conversely, the inclusion of affiliate promotions in user interface elements that are clearly identified as belonging to the add-on are acceptable. Security, Compliance and Blocking We expect all add-ons, whether hosted on addons.mozilla.org or not, to be secure and well-maintained in how they handle both their own data and their users’ data. They must also securely manage all of their interactions with the web and the browser and the operating system. Policy Enforcement Mozilla may reject or block affected versions or entire add-ons that don’t comply with the above policies, depending on the extent of their non-compliance. Mozilla may attempt to contact the add-on’s developer(s) and provide a reasonable time frame for the problems to be corrected before a block is deployed. If an add-on appears to intentionally or repeatedly violate the policies, or its developers have proven unreachable, unresponsive, or uncooperative, blocking may be immediate. Mozilla reserves the right to block or delete any developer’s account on addons.mozilla.org, thereby preventing further use of the service, for certain violations of Mozilla’s policies. For more information about rejection and blocking, see What does review rejection mean to users? Tags: add-ons review policies Contributors: kewisch rebloor wagnerand atsay jvillalobos wbamberg kmaglione dotproto Last update: dotproto Sep 17, 2025 Up Next Publish Add-on Policies FAQ Publish Firefox Add-on Distribution Agreement Publish Add-ons Blocking Process Documentation Topics Develop Publish Manage Enterprise Themes Connect With Us Twitter For developers: @mozamo For end users: @rockyourfirefox More Matrix Community forum Extensions Developer Newsletter Stay up-to-date on news and events for Firefox extension developers. Email Address I’m okay with Mozilla handling my info as explained in this Privacy Notice . Sign up Thanks! Please check your inbox to confirm your subscription. If you haven’t previously confirmed a subscription to a Mozilla-related newsletter you may have to do so. Please check your inbox or your spam filter for an email from us. Mozilla Add-ons About Blog Developer Hub Developer Policies Forum Firefox Download Firefox Desktop Mobile Features Beta, Nightly, Developer Edition Twitter (@firefox) YouTube (firefoxchannel) Github (mozilla) Website Privacy Notice Cookies Legal Edit this page on GitHub Portions of this content are ©1998–2025 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T09:30:12 |
https://jitsi.org/blog/page/2/ | Video Conferencing Software Blog | Jitsi Blog & News JaaS: the Team that Builds Jitsi Can Now Also Run it for You! Start now Docs Projects Blog Community About About Powered by Jitsi™ Partners Jitsi in the News User FAQ Download News from the Jitsi Community New Jitsi Meet Mobile now with Live Streaming, better performance and more! August 30, 2018 It’s been a while since we have last written about our mobile apps. We have been busy improving them, and now that 1.18 is available for Android and iOS, let’s talk about the release! This […] Read more GSoC 2018 Results August 27, 2018 We are happy to present the results of another year with the Google Summer of Code program. We had three students complete phase 2 of the program and all of them went on to complete […] Read more Use Jitsi with Slack Today! August 20, 2018 World’s most powerful open video conferencing platform now also available for Slack! Enable Jitsi for your team today https://jitsi.org/slack Read more New feature: Brady Bunch style layout August 13, 2018 Here’s the story of a lovely video layout and a powerful video engine that came together to form a new Brady Bunch style video layout: Each call participant’s individual video size is put into the […] Read more New off-stage layer suppression feature August 7, 2018 We have a new feature called off-stage layer suppression that helps save bandwidth and CPU for both end users and the Videobridge. To help handle the varying video qualities needed for the active speaker and […] Read more Seen the news? July 27, 2018 Hey all, we’ve been having plenty of questions so quick update: the recent news you have seen about Atlassian does not affect Jitsi. We are keeping course! So, have a great day everyone! Read more Jitsi meets Docker July 17, 2018 Jitsi Meet is composed of several components which work together for delivering the best video conferences, as you are used to already. When it comes to deploying these to production, there are, of course, many […] Read more New tutorial video: Scaling Jitsi Meet in the Cloud July 10, 2018 In Yasen Pramatarov’s latest tutorial video, he walks through concepts on how to scale and load balance a Jitsi Meet install in the cloud: Yasen uses Amazon Web Services (AWS) as an example, but […] Read more Learn how to Live Stream and Record on your Jitsi Meet Install July 3, 2018 Yasen Pramatarov just released this third tutorial video. This one covers how to setup live streaming and recording using the Jibri module for Jitsi Meet. Jibri is a module that acts as a silent participant […] Read more Tutorial video: How to Load Balance Jitsi Meet June 25, 2018 The second in our series of video tutorials is now available. This one covers how to load balance Jitsi Meet with multiple Jitsi Videobridges like this: Load balancing is important for additional redundancy in production […] Read more We have a new Community Forum! June 18, 2018 Jitsi has a new Community Forum. Check it out at community.jitsi.org! This was way past due Previously we handled most of our community discussions via our Users and Dev mailing lists, which were originally setup […] Read more New tutorial: Installing Jitsi Meet on your own Linux Server June 12, 2018 We are working on a new series of video tutorials. We are happy to announce the first one today – a step-by-step guide on how to setup Jitsi Meet on your own server. The video […] Read more The Atlassian Acquisition – 3 years later June 4, 2018 It has been 3 years Atlassian became Jitsi’s new home! To help give us an objective view on our accomplishments and where we are going next, we asked Chad Hart of webrtcHacks to do a […] Read more Jitsi Meet stable releases, now more discoverable! May 4, 2018 If you have been following the Jitsi Meet development for some time, you might have noticed the sheer amount of git tags. We make tags for every successful build our CI makes, and also every […] Read more GSoC 2018: ready fuels! April 25, 2018 It’s that time of the year again! We are incredibly happy to have been chosen again as an organization for Google Summer of Code. After the tough process of choosing candidates and projects, here are […] Read more Jitsi Meet Simplified! April 6, 2018 Did you ever think that all the features in Jitsi Meet kind of made you work too hard in order to find what you were really looking for? Was it in the side toolbar? Or […] Read more Help us with our Jitsi User Survey! March 30, 2018 Calling out to all Jitsi users and aficionados! Please take a minute to make Jitsi better by answering 9 quick questions on our user survey: Help us improve the Jitsi community with your feedback. The […] Read more GSoC student applications are open March 12, 2018 Hey everyone, Student applications for Google Summer of Code 2018 are now open. If you would like to apply with the Jitsi organization, please refer to this page for some useful tips. We encourage students […] Read more Jitsi wins LinuxLinks’ 2018 award for Best Open Source Video Conferencing Software February 25, 2018 We were just alerted by @linuxlinks that we are the winner of their 2018 award for Best Open Source Video Conferencing Software. That’s always a pleasure for us and obviously a good reason for everyone to […] Read more Hello GSoC 2018! Here we come! February 13, 2018 It is happening! Again! Our friends at Google Summer of Code have graciously accepted us as a participant in the 2018 edition of the program! Dear students, all over the world, this is probably one […] Read more meet.jit.si now fully available over IPv6 February 8, 2018 This would have been hard to believe a few years ago but, today, there are a number of cases where one could find themselves in an IPv6-only network. For example, accessing the Internet from some […] Read more New Jitsi Meet mobile versions released! December 29, 2017 With 2017 close to ending, we have one more Jitsi Meet mobile release for you! In this release we focused on two main areas: the welcome page and error handling. The welcome page has been […] Read more Improving WebRTC Call Quality with Machine Learning. Check out Emil’s talk from Kranky Geek 2017 October 31, 2017 One of the most challenging problems in Video transport is the ability to determine exactly how much data exactly one can send without overwhelming their peer. In this video Emil talks about how machine learning […] Read more Jitsi Meet wins the Open Source Classic award at DINAcon 2017 October 24, 2017 We are humbled to share that Jitsi Meet has won the Open Source Classic award at the DINAcon awards 2017, which took place in Bern (Switzerland) last Friday. The list of nominees was impressive, so […] Read more Jitsi Meet mobile now supports authentication! September 28, 2017 A good number of you have been setting up Jitsi Meet with authentication regardless of the fact that merely making sense of our tutorial on the subject is a notable act of heroism (anyone interested in […] Read more GSoC 2017 final results September 7, 2017 Another summer of code is behind us, and we’re here to present what our GSoC students accomplished throughout the program. We had four students this year, and three of them completed their projects while one […] Read more Matrix adds support for video with Jitsi August 26, 2017 Our friends from Matrix have just finished their Jitsi integration and now have first class video conferencing support! Go Matrix! Read more A speech-to-text prototype August 1, 2017 We now have a working prototype of speech-to-text in jitsi-meet, implemented as part of jigasi. In this first version the transcribed text is just added to the chat, but a better interface is in the […] Read more Introducing the Jitsi Meet mobile SDK August 1, 2017 Jitsi Meet has been available on mobile for some time now. The app works on both Android and iOS, and while it uses meet.jit.si to create conferences by default, it works with any custom Jitsi […] Read more P2P4121 July 17, 2017 If you are wondering, we use this for: “Peer-to-peer for 1 to 1″. It does what it says: every time there are only two participants in a call, instead of using Jitsi Videobridge, Jitsi Meet […] Read more Audio Only Mode in Jitsi Meet July 12, 2017 Audio Only Mode in Jitsi Meet We often hear from our users that they’d like to have a low bandwidth mode. This is sometimes because they are on expensive satellite links that charge by the […] Read more GSoC 2017 Progress Report July 3, 2017 We are already a month into the coding period of the Google Summer of Code 2017 program, and we are excited to report on our students’ progress so far. This year we are fortunate to […] Read more Telephony Support on meet.jit.si June 29, 2017 Yes! You heard, or rather, read that right . You can now call into meet.jit.si conferences. Just head out to your Jitsi Meet Contact List, then click on “Share the link” and use the telephone numbers and […] Read more Jitsi on the VUC June 26, 2017 Check out episode 651 the VoIP User’s Conference with Jitsi’s Saul Ibarra Corretge and Emil Ivov, for an update on Jitsi’s latest and greatest. And, of course, the call was hosted on Jitsi Meet. Try it […] Read more Adaptivity June 22, 2017 Alright Everybody, this is a big one! We have been at it for about 10 months now and we are really, really, really happy to now bring it to you. Adaptivity is all about getting Jitsi […] Read more Speaker Times in Jitsi Meet June 15, 2017 Speaker Times in Jitsi Meet Ever felt like your standups are taking more time than they should be? Or maybe wondered whether you spoke for longer than you let your peers respond? Well, we certainly did! […] Read more Control the Volume for Every Meet Participant June 8, 2017 Ever been in a situation where one of your contacts comes through really loudly, while another one is almost silent and you have to constantly play with your volume in order to have a productive […] Read more New Layouts in Jitsi Meet June 7, 2017 New layout for your 1:1s on meet.jit.si In the past people have often been confused about one specific aspect of our user interface: Notice how in both of the above cases there is a black […] Read more Jitsi Meet now on mobile!!! March 8, 2017 Yes! Jitsi Meet is now available for Android and iOS!!! Join your Jitsi Meetings from your phone! Read more Google Summer of Code ’17 is ON! March 3, 2017 After a break of a couple of years, Jitsi is once again proudly participating in Google Summer of Code! Check out our project ideas and let’s have fun together this summer (while you are getting […] Read more Jitsi: State of The Union February 1, 2017 Check out what’s in and what’s coming for Jitsi in @saghul’s FOSDEM presentation. Read more Mobile WebRTC with React Native November 21, 2016 In their Kranky/Geek video Emil and Lyubo share Jitsi’s experience building a WebRTC app, for mobile with React Native. Read more Live Streaming with Jitsi and YouTube May 10, 2016 Checkout the new YouTube Live Streaming support on meet.jit.si and invite unlimited numbers of viewers to your conferences. Read more Simulcast now in production on meet.jit.si! April 23, 2016 Tired of having to choose between 1080p and reasonable bandwidth consumption? The new simulcast support on meet.jit.si should make you happy then! Also run it yourself by installing Jitsi Meet and Jitsi Videobridge. Read more Co-watch YouTube videos on the new meet.jit.si April 6, 2016 Want to share YouTube videos and watch them together with friends? Try the new meet.jit.si! Read more WebRTC Beyond P2P October 11, 2015 Interested in what video routers (SFUs) bring to your table? Check out Emil’s presentation from the Kranky/Geek event and also learn what simulcast and SVC are. Read more Temasys contributes Safari/IE plugin to meet.jit.si October 7, 2015 Following a contribution from Temasys, it is now possible to join meet.jit.si conferences through Safari and IE. Read more Switching to the Apache License June 18, 2015 We are happy to announce that all projects in the Jitsi community are switching to the Apache License! Enjoy! 🙂 Read more Firefox multistream and renegotiation for Jitsi Videobridge June 3, 2015 After a few months of hard work by Mozilla and Jitsi developers, both Firefox and Jitsi have added the missing pieces and can now work together! In this Mozilla Hacks post we’ll tell you more about the nitty-gritty details of our collaborative adventure. Read more Research on Last N April 28, 2015 We recently published a research paper about our “Last N” approach to videoconferencing. It describes how it all works and shows our evaluation based on the implementation in Jitsi Meet and Jitsi Videobridge. Read more Recent Posts Introducing Receiver Audio Subscriptions GSoC 2025, let’s do this! AV1 and more … how does Jitsi Meet pick video codecs? Connecting anything to everything via SIP Improving performance on very large calls: introducing SSRC rewriting Categories Apache (1) Atlassian (1) Featured (17) GSoC (11) Guest Post (1) Jitsi as a Service (6) Jitsi Community (30) Jitsi Meet (56) Jitsi Videobridge (17) Kranky Geek (1) Live Streaming (3) meet.jit.si (16) Mobile (7) New Feature (10) Press Release (9) Security and Privacy (4) Simulcast (3) SVC (1) Uncategorized (25) Video Conferencing (8) WebRTC (12) YouTube (6) Jitsi is a trademark of © 8x8, Inc. All Rights Reserved. | 2026-01-13T09:30:12 |
https://extensionworkshop.com/documentation/publish/add-on-policies/#firefox-for-android | Add-on Policies | Firefox Extension Workshop Extension Workshop Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Submit or Manage Extensions Search Submit or Manage Extensions Search Select a section Page Name Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise <a href="https://support.mozilla.org/kb | 2026-01-13T09:30:12 |
https://developers.cloudflare.com/ai-gateway/usage/providers/cerebras/ | Cerebras · Cloudflare AI Gateway docs Skip to content Cloudflare Docs Search Docs Directory APIs SDKs Help Log in Select theme Dark Light Auto AI Gateway No results found. Try a different search term, or use our global search . Overview Getting started Using AI Gateway Unified API (OpenAI compat) Provider Native Workers AI Amazon Bedrock Anthropic Azure OpenAI Baseten Cartesia Cerebras Cohere Deepgram DeepSeek ElevenLabs Fal AI Google AI Studio Google Vertex AI Groq HuggingFace Ideogram Mistral AI OpenAI OpenRouter Parallel Perplexity Replicate xAI WebSockets API Beta Overview Realtime WebSockets API Non-realtime WebSockets API Features Overview Unified Billing Caching Rate limiting Dynamic routing Beta Overview Using a dynamic route JSON Configuration Data Loss Prevention (DLP) Beta Overview Set up Data Loss Prevention (DLP) Guardrails Beta Overview Set up Guardrails Supported model types Usage considerations Configuration BYOK (Store Keys) Beta Custom costs Custom Providers Beta Manage gateways Request handling Authenticated Gateway Observability Costs Custom metadata Analytics Logging Overview Workers Logpush Integrations Vercel AI SDK Agents ↗ AI Gateway Binding Methods Workers AI Tutorials Platform Overview Limits Pricing Audit logs Changelog Header Glossary REST API reference ↗ API MCP server ↗ MCP AI Assistant ↗ Architectures LLM resources llms.txt prompt.txt AI Gateway llms-full.txt Developer Platform llms-full.txt GitHub X.com YouTube Select theme Dark Light Auto On this page Overview Endpoint Prerequisites Examples cURL OpenAI-Compatible Endpoint On this page Overview Endpoint Prerequisites Examples cURL OpenAI-Compatible Endpoint Was this helpful? Edit Issue Directory … AI Gateway Using AI Gateway Provider Native Cerebras Copy page Cerebras Cerebras ↗ offers developers a low-latency solution for AI model inference. Endpoint https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/cerebras Prerequisites When making requests to Cerebras, ensure you have the following: Your AI Gateway Account ID. Your AI Gateway gateway name. An active Cerebras API token. The name of the Cerebras model you want to use. Examples cURL Example fetch request curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/cerebras/chat/completions \ --header 'content-type: application/json' \ --header 'Authorization: Bearer CEREBRAS_TOKEN' \ --data '{ "model": "llama3.1-8b", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] }' OpenAI-Compatible Endpoint You can also use the OpenAI-compatible endpoint ( /ai-gateway/usage/chat-completion/ ) to access Cerebras models using the OpenAI API schema. To do so, send your requests to: https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions Specify: { " model " : "cerebras/{model}" } Was this helpful? Edit page Last updated: Aug 27, 2025 Previous Cartesia Next Cohere Resources API New to Cloudflare? Directory Sponsorships Open Source Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Speed Test Is BGP Safe Yet? RPKI Toolkit Certificate Transparency Community X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings | 2026-01-13T09:30:12 |
https://developers.cloudflare.com/ai-gateway/get-started/#_top | Getting started · Cloudflare AI Gateway docs Skip to content Cloudflare Docs Search Docs Directory APIs SDKs Help Log in Select theme Dark Light Auto AI Gateway No results found. Try a different search term, or use our global search . Overview Getting started Using AI Gateway Unified API (OpenAI compat) Provider Native Workers AI Amazon Bedrock Anthropic Azure OpenAI Baseten Cartesia Cerebras Cohere Deepgram DeepSeek ElevenLabs Fal AI Google AI Studio Google Vertex AI Groq HuggingFace Ideogram Mistral AI OpenAI OpenRouter Parallel Perplexity Replicate xAI WebSockets API Beta Overview Realtime WebSockets API Non-realtime WebSockets API Features Overview Unified Billing Caching Rate limiting Dynamic routing Beta Overview Using a dynamic route JSON Configuration Data Loss Prevention (DLP) Beta Overview Set up Data Loss Prevention (DLP) Guardrails Beta Overview Set up Guardrails Supported model types Usage considerations Configuration BYOK (Store Keys) Beta Custom costs Custom Providers Beta Manage gateways Request handling Authenticated Gateway Observability Costs Custom metadata Analytics Logging Overview Workers Logpush Integrations Vercel AI SDK Agents ↗ AI Gateway Binding Methods Workers AI Tutorials Platform Overview Limits Pricing Audit logs Changelog Header Glossary REST API reference ↗ API MCP server ↗ MCP AI Assistant ↗ Architectures LLM resources llms.txt prompt.txt AI Gateway llms-full.txt Developer Platform llms-full.txt GitHub X.com YouTube Select theme Dark Light Auto On this page Overview Authenticated gateway 🔒 Provider Authentication Integration Options Unified API Endpoint Provider-specific endpoints Next steps On this page Overview Authenticated gateway 🔒 Provider Authentication Integration Options Unified API Endpoint Provider-specific endpoints Next steps Was this helpful? Edit Issue Directory … AI Gateway Getting started Copy page Getting started Last reviewed: over 1 year ago In this guide, you will learn how to create and use your first AI Gateway. Dashboard API Go to AI Gateway Log into the Cloudflare dashboard ↗ and select your account. Go to AI > AI Gateway . Select Create Gateway . Enter your Gateway name . Note: Gateway name has a 64 character limit. Select Create . To set up an AI Gateway using the API: Create an API token with the following permissions: AI Gateway - Read AI Gateway - Edit Get your Account ID . Using that API token and Account ID, send a POST request to the Cloudflare API. Authenticated gateway 🔒 When you enable authentication on gateway each request is required to include a valid Cloudflare API token, adding an extra layer of security. We recommend using an authenticated gateway to prevent unauthorized access. Learn more . Provider Authentication Authenticate with your upstream AI provider using one of the following options: Unified Billing: Use the AI Gateway billing to pay for and authenticate your inference requests. Refer to Unified Billing . BYOK (Store Keys): Store your own provider API Keys with Cloudflare, and AI Gateway will include them at runtime. Refer to BYOK . Request headers: Include your provider API Key in the request headers as you normally would (for example, Authorization: Bearer <OPENAI_API_KEY> ). Integration Options Unified API Endpoint OpenAI Compatible Recommended The easiest way to get started with AI Gateway is through our OpenAI-compatible /chat/completions endpoint. This allows you to use existing OpenAI SDKs and tools with minimal code changes while gaining access to multiple AI providers. https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_name}/compat/chat/completions Key benefits: Drop-in replacement for OpenAI API, works with existing OpenAI SDKs and other OpenAI compliant clients Switch between providers by changing the model parameter Dynamic Routing - Define complex routing scenarios requiring conditional logic, conduct A/B tests, set rate / budget limits, etc Example: Make a request to OpenAI using OpenAI JS SDK with Stored Key (BYOK) import OpenAI from "openai" ; const client = new OpenAI ( { apiKey : "{cf_api_token}" , baseURL : "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat" , } ) ; const response = await client . chat . completions . create ( { model : "openai/gpt-5.2" , messages : [ { role : "user" , content : "Hello, world!" } ] , } ) ; import OpenAI from "openai" ; const client = new OpenAI ( { apiKey : "{cf_api_token}" , baseURL : "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat" , } ) ; const response = await client . chat . completions . create ( { model : "anthropic/claude-4-5-sonnet" , messages : [ { role : "user" , content : "Hello, world!" } ] , } ) ; import OpenAI from "openai" ; const client = new OpenAI ( { apiKey : "{cf_api_token}" , baseURL : "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat" , } ) ; const response = await client . chat . completions . create ( { model : "google/gemini-2.5-pro" , messages : [ { role : "user" , content : "Hello, world!" } ] , } ) ; import OpenAI from "openai" ; const client = new OpenAI ( { apiKey : "{cf_api_token}" , baseURL : "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat" , } ) ; const response = await client . chat . completions . create ( { model : "grok/grok-4" , messages : [ { role : "user" , content : "Hello, world!" } ] , } ) ; import OpenAI from "openai" ; const client = new OpenAI ( { apiKey : "{cf_api_token}" , baseURL : "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat" , } ) ; const response = await client . chat . completions . create ( { model : "dynamic/customer-support" , messages : [ { role : "user" , content : "Hello, world!" } ] , } ) ; import OpenAI from "openai" ; const client = new OpenAI ( { apiKey : "{cf_api_token}" , baseURL : "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat" , } ) ; const response = await client . chat . completions . create ( { model : "workers-ai/@cf/meta/llama-3.3-70b-instruct-fp8-fast" , messages : [ { role : "user" , content : "Hello, world!" } ] , } ) ; import OpenAI from "openai" ; const client = new OpenAI ( { apiKey : "{openai_api_token}" , defaultHeaders : { // if gateway is authenticated "cf-aig-authorization" : `Bearer {cf_api_token}` , }, baseURL : "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat" , } ) ; const response = await client . chat . completions . create ( { model : "openai/gpt-5.2" , messages : [ { role : "user" , content : "Hello, world!" } ] , } ) ; import OpenAI from "openai" ; const client = new OpenAI ( { apiKey : "{anthropic_api_token}" , defaultHeaders : { // if gateway is authenticated "cf-aig-authorization" : `Bearer {cf_api_token}` , }, baseURL : "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat" , } ) ; const response = await client . chat . completions . create ( { model : "anthropic/claude-4-5-sonnet" , messages : [ { role : "user" , content : "Hello, world!" } ] , } ) ; import OpenAI from "openai" ; const client = new OpenAI ( { apiKey : "{google_api_token}" , defaultHeaders : { // if gateway is authenticated "cf-aig-authorization" : `Bearer {cf_api_token}` , }, baseURL : "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat" , } ) ; const response = await client . chat . completions . create ( { model : "google/gemini-2.5-pro" , messages : [ { role : "user" , content : "Hello, world!" } ] , } ) ; import OpenAI from "openai" ; const client = new OpenAI ( { apiKey : "{grok_api_token}" , defaultHeaders : { // if gateway is authenticated "cf-aig-authorization" : `Bearer {cf_api_token}` , }, baseURL : "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat" , } ) ; const response = await client . chat . completions . create ( { model : "grok/grok-4" , messages : [ { role : "user" , content : "Hello, world!" } ] , } ) ; import OpenAI from "openai" ; const client = new OpenAI ( { apiKey : "{dynamic_api_token}" , defaultHeaders : { // if gateway is authenticated "cf-aig-authorization" : `Bearer {cf_api_token}` , }, baseURL : "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat" , } ) ; const response = await client . chat . completions . create ( { model : "dynamic/customer-support" , messages : [ { role : "user" , content : "Hello, world!" } ] , } ) ; import OpenAI from "openai" ; const client = new OpenAI ( { apiKey : "{workers-ai_api_token}" , defaultHeaders : { // if gateway is authenticated "cf-aig-authorization" : `Bearer {cf_api_token}` , }, baseURL : "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat" , } ) ; const response = await client . chat . completions . create ( { model : "workers-ai/@cf/meta/llama-3.3-70b-instruct-fp8-fast" , messages : [ { role : "user" , content : "Hello, world!" } ] , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified () ; const { text } = await generateText ( { model : aigateway ( unified ( 'openai/gpt-5.2' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified () ; const { text } = await generateText ( { model : aigateway ( unified ( 'anthropic/claude-4-5-sonnet' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified () ; const { text } = await generateText ( { model : aigateway ( unified ( 'google/gemini-2.5-pro' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified () ; const { text } = await generateText ( { model : aigateway ( unified ( 'grok/grok-4' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified () ; const { text } = await generateText ( { model : aigateway ( unified ( 'dynamic/customer-support' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified () ; const { text } = await generateText ( { model : aigateway ( unified ( 'workers-ai/@cf/meta/llama-3.3-70b-instruct-fp8-fast' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( unified ( 'openai/gpt-5.2' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( unified ( 'anthropic/claude-4-5-sonnet' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( unified ( 'google/gemini-2.5-pro' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( unified ( 'grok/grok-4' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( unified ( 'dynamic/customer-support' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( unified ( 'workers-ai/@cf/meta/llama-3.3-70b-instruct-fp8-fast' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createOpenAI } from 'ai-gateway-provider/providers/openai' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const openai = createOpenAI () ; const { text } = await generateText ( { model : aigateway ( openai . chat ( 'gpt-5.2' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createAnthropic } from 'ai-gateway-provider/providers/anthropic' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const anthropic = createAnthropic () ; const { text } = await generateText ( { model : aigateway ( anthropic ( 'claude-4-5-sonnet' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createGoogle } from 'ai-gateway-provider/providers/google' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const google = createGoogle () ; const { text } = await generateText ( { model : aigateway ( google ( 'gemini-2.5-pro' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createXai } from 'ai-gateway-provider/providers/xai' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const xai = createXai () ; const { text } = await generateText ( { model : aigateway ( xai ( 'grok-4' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified () ; const { text } = await generateText ( { model : aigateway ( unified ( 'customer-support' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified () ; const { text } = await generateText ( { model : aigateway ( unified ( '@cf/meta/llama-3.3-70b-instruct-fp8-fast' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createOpenAI } from 'ai-gateway-provider/providers/openai' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const openai = createOpenAI ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( openai . chat ( 'gpt-5.2' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createAnthropic } from 'ai-gateway-provider/providers/anthropic' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const anthropic = createAnthropic ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( anthropic ( 'claude-4-5-sonnet' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createGoogle } from 'ai-gateway-provider/providers/google' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const google = createGoogle ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( google ( 'gemini-2.5-pro' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createXai } from 'ai-gateway-provider/providers/xai' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const xai = createXai ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( xai ( 'grok-4' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( unified ( 'customer-support' )) , prompt : 'What is Cloudflare?' , } ) ; import { createAiGateway } from 'ai-gateway-provider' ; import { createUnified } from 'ai-gateway-provider/providers/unified' ; import { generateText } from "ai" ; const aigateway = createAiGateway ( { accountId : "{CLOUDFLARE_ACCOUNT_ID}" , gateway : '{GATEWAY_NAME}' , apiKey : '{CF_AIG_TOKEN}' , } ) ; const unified = createUnified ( { apiKey : '{API_KEY}' } ) ; const { text } = await generateText ( { model : aigateway ( unified ( '@cf/meta/llama-3.3-70b-instruct-fp8-fast' )) , prompt : 'What is Cloudflare?' , } ) ; curl -X POST https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions \ --header 'cf-aig-authorization: Bearer {CF_AIG_TOKEN}' \ --header 'Content-Type: application/json' \ --data '{ "model": "openai/gpt-5.2", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] }' curl -X POST https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions \ --header 'cf-aig-authorization: Bearer {CF_AIG_TOKEN}' \ --header 'Content-Type: application/json' \ --data '{ "model": "anthropic/claude-4-5-sonnet", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] }' curl -X POST https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions \ --header 'cf-aig-authorization: Bearer {CF_AIG_TOKEN}' \ --header 'Content-Type: application/json' \ --data '{ "model": "google/gemini-2.5-pro", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] }' curl -X POST https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions \ --header 'cf-aig-authorization: Bearer {CF_AIG_TOKEN}' \ --header 'Content-Type: application/json' \ --data '{ "model": "grok/grok-4", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] }' curl -X POST https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions \ --header 'cf-aig-authorization: Bearer {CF_AIG_TOKEN}' \ --header 'Content-Type: application/json' \ --data '{ "model": "dynamic/customer-support", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] }' curl -X POST https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions \ --header 'cf-aig-authorization: Bearer {CF_AIG_TOKEN}' \ --header 'Content-Type: application/json' \ --data '{ "model": "workers-ai/@cf/meta/llama-3.3-70b-instruct-fp8-fast", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] }' curl -X POST https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions \ --header 'cf-aig-authorization: Bearer {CF_AIG_TOKEN}' \ --header 'Authorization: Bearer {openai_api_token}' \ --header 'Content-Type: application/json' \ --data '{ "model": "openai/gpt-5.2", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] }' curl -X POST https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions \ --header 'cf-aig-authorization: Bearer {CF_AIG_TOKEN}' \ --header 'Authorization: Bearer {anthropic_api_token}' \ --header 'Content-Type: application/json' \ --data '{ "model": "anthropic/claude-4-5-sonnet", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] }' curl -X POST https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions \ --header 'cf-aig-authorization: Bearer {CF_AIG_TOKEN}' \ --header 'Authorization: Bearer {google_api_token}' \ --header 'Content-Type: application/json' \ --data '{ "model": "google/gemini-2.5-pro", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] }' curl -X POST https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions \ --header 'cf-aig-authorization: Bearer {CF_AIG_TOKEN}' \ --header 'Authorization: Bearer {grok_api_token}' \ --header 'Content-Type: application/json' \ --data '{ "model": "grok/grok-4", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] }' curl -X POST https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions \ --header 'cf-aig-authorization: Bearer {CF_AIG_TOKEN}' \ --header 'Authorization: Bearer {dynamic_api_token}' \ --header 'Content-Type: application/json' \ --data '{ "model": "dynamic/customer-support", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] }' curl -X POST https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat/chat/completions \ --header 'cf-aig-authorization: Bearer {CF_AIG_TOKEN}' \ --header 'Authorization: Bearer {workers-ai_api_token}' \ --header 'Content-Type: application/json' \ --data '{ "model": "workers-ai/@cf/meta/llama-3.3-70b-instruct-fp8-fast", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] }' Refer to Unified API to learn more about OpenAI compatibility. Provider-specific endpoints For direct integration with specific AI providers, use dedicated endpoints that maintain the original provider's API schema while adding AI Gateway features. https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/{provider} Available providers: OpenAI - GPT models and embeddings Anthropic - Claude models Google AI Studio - Gemini models Workers AI - Cloudflare's inference platform AWS Bedrock - Amazon's managed AI service Azure OpenAI - Microsoft's OpenAI service and more... Next steps Learn more about caching for faster requests and cost savings and rate limiting to control how your application scales. Explore how to specify model or provider fallbacks, ratelimits, A/B tests for resiliency. Learn how to use low-cost, open source models on Workers AI - our AI inference service. Was this helpful? Edit page Last updated: Jan 7, 2026 Previous Overview Next Unified API (OpenAI compat) Resources API New to Cloudflare? Directory Sponsorships Open Source Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Speed Test Is BGP Safe Yet? RPKI Toolkit Certificate Transparency Community X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings | 2026-01-13T09:30:12 |
https://docs.google.com/document/d/10AfaGCgDd72K74ogfFzBhC_f9fIsBzwR7hVGJmJSKaY/copy | :root{--gm3-sys-color-on-surface-rgb:31,31,31}@media screen and (prefers-color-scheme:dark){:root{--gm3-sys-color-on-surface-rgb:227,227,227}}:root{--wf-harmonize-filter-light:none;--wf-harmonize-filter-dark:none}.q4Wquf,.nfoC7c{display:block;height:25vh;position:relative}@media (min-width:600px){.q4Wquf,.nfoC7c{height:150px}}.q4Wquf.Irjbwb{height:auto}@media screen and (prefers-color-scheme:dark){.q4Wquf:not(.GtvzYd){display:none}}.nfoC7c{margin:0;overflow:hidden}.PwpMUe,.lVUmD{display:block;height:100%;margin:0 auto;width:100%}.St9mde{display:block;-webkit-filter:var(--wf-harmonize-filter-light);filter:var(--wf-harmonize-filter-light);height:100%;max-width:100%;min-height:110px;position:relative;-webkit-transform:translate(-43%,-3%);-ms-transform:translate(-43%,-3%);transform:translate(-43%,-3%);width:auto;z-index:3}@media screen and (prefers-color-scheme:dark){.St9mde{-webkit-filter:var(--wf-harmonize-filter-dark);filter:var(--wf-harmonize-filter-dark)}}.PwpMUe,.lVUmD,.St9mde{-o-object-fit:contain;object-fit:contain}.wsArZ[data-ss-mode="1"] .q4Wquf,.wsArZ[data-ss-mode="1"] .St9mde{height:auto;width:100%}.wsArZ[data-ss-mode="1"] .St9mde{max-width:400px}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .q4Wquf,.NQ5OL .St9mde{height:auto;width:100%}.NQ5OL .St9mde{max-width:400px}}.q4Wquf.NWba7e,.q4Wquf.NWba7e .St9mde{height:auto}.q4Wquf.NWba7e .St9mde{height:auto;max-width:312px;width:100%}.q4Wquf.NWba7e.zpCp3 .St9mde{max-width:unset}.q4Wquf.IiQozc .St9mde{margin:0 auto;-webkit-transform:none;-ms-transform:none;transform:none}.q4Wquf.Irjbwb .St9mde{height:auto;width:100%}.q4Wquf.EEeaqf .St9mde{max-height:144px;max-width:144px}.SnAaEd{background-image:-webkit-gradient(linear,left top,left bottom,from(rgba(233,233,233,0)),color-stop(62.22%,rgba(233,233,233,0)),color-stop(40.22%,rgb(233,233,233)),to(rgba(233,233,233,0)));background-image:-webkit-linear-gradient(top,rgba(233,233,233,0) 0,rgba(233,233,233,0) 62.22%,rgb(233,233,233) 40.22%,rgba(233,233,233,0) 100%);background-image:linear-gradient(to bottom,rgba(233,233,233,0) 0,rgba(233,233,233,0) 62.22%,rgb(233,233,233) 40.22%,rgba(233,233,233,0) 100%);height:100%;left:0;overflow:hidden;position:absolute;right:0;top:0;z-index:2}@media screen and (prefers-color-scheme:dark){.SnAaEd{display:none}}.SnAaEd::after,.SnAaEd::before{content:"";display:block;height:100%;min-width:110px;position:absolute;right:-10%;-webkit-transform:rotate(-104deg);-ms-transform:rotate(-104deg);transform:rotate(-104deg);width:25vh;z-index:2}@media (min-width:600px){.SnAaEd::after,.SnAaEd::before{width:150px}}.SnAaEd::before{background-image:-webkit-gradient(linear,left top,left bottom,from(rgba(243,243,243,0)),to(rgba(243,243,243,.9)));background-image:-webkit-linear-gradient(top,rgba(243,243,243,0) 0,rgba(243,243,243,.9) 100%);background-image:linear-gradient(to bottom,rgba(243,243,243,0) 0,rgba(243,243,243,.9) 100%);bottom:-10%}.SnAaEd::after{background-image:-webkit-gradient(linear,left top,left bottom,from(rgba(255,255,255,0)),to(rgba(255,255,255,.9)));background-image:-webkit-linear-gradient(top,rgba(255,255,255,0) 0,rgba(255,255,255,.9) 100%);background-image:linear-gradient(to bottom,rgba(255,255,255,0) 0,rgba(255,255,255,.9) 100%);bottom:-80%}.wsArZ[data-ss-mode="1"] .SnAaEd~.St9mde{width:auto}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .SnAaEd~.St9mde{width:auto}}.RHNWk .St9mde{height:auto}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .RHNWk .St9mde{width:115px}}.cf660d .St9mde{-webkit-transform:translate(-9%,-3%);-ms-transform:translate(-9%,-3%);transform:translate(-9%,-3%)}.tUhwwc .St9mde{margin:auto;max-height:230px;right:0;top:-3%;-webkit-transform:none;-ms-transform:none;transform:none}.Jkvqxd .St9mde{-webkit-transform:translate(9%,-3%);-ms-transform:translate(9%,-3%);transform:translate(9%,-3%)}.onc8Ic .St9mde{-webkit-transform:translate(var( --c-ps-s,24px ),0);-ms-transform:translate(var( --c-ps-s,24px ),0);transform:translate(var( --c-ps-s,24px ),0)}.WA89Yb .St9mde{-webkit-transform:translate(0,0);-ms-transform:translate(0,0);transform:translate(0,0)}.wsArZ[data-ss-mode="1"] .XEN8Yb .St9mde{max-width:115px}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .XEN8Yb .St9mde{max-width:115px}}@media (min-width:1240px) and (orientation:landscape),all and (min-width:1600px){.KyPKed .NQ5OL .XEN8Yb .St9mde{max-width:115px}}.IsSr6b .St9mde{max-width:300px}.mmskdd .St9mde{-webkit-transform:none;-ms-transform:none;transform:none}@-webkit-keyframes quantumWizBoxInkSpread{0%{-webkit-transform:translate(-50%,-50%) scale(.2);transform:translate(-50%,-50%) scale(.2)}100%{-webkit-transform:translate(-50%,-50%) scale(2.2);transform:translate(-50%,-50%) scale(2.2)}}@keyframes quantumWizBoxInkSpread{0%{-webkit-transform:translate(-50%,-50%) scale(.2);transform:translate(-50%,-50%) scale(.2)}100%{-webkit-transform:translate(-50%,-50%) scale(2.2);transform:translate(-50%,-50%) scale(2.2)}}@-webkit-keyframes quantumWizIconFocusPulse{0%{-webkit-transform:translate(-50%,-50%) scale(1.5);transform:translate(-50%,-50%) scale(1.5);opacity:0}100%{-webkit-transform:translate(-50%,-50%) scale(2);transform:translate(-50%,-50%) scale(2);opacity:1}}@keyframes quantumWizIconFocusPulse{0%{-webkit-transform:translate(-50%,-50%) scale(1.5);transform:translate(-50%,-50%) scale(1.5);opacity:0}100%{-webkit-transform:translate(-50%,-50%) scale(2);transform:translate(-50%,-50%) scale(2);opacity:1}}@-webkit-keyframes quantumWizRadialInkSpread{0%{-webkit-transform:scale(1.5);transform:scale(1.5);opacity:0}100%{-webkit-transform:scale(2.5);transform:scale(2.5);opacity:1}}@keyframes quantumWizRadialInkSpread{0%{-webkit-transform:scale(1.5);transform:scale(1.5);opacity:0}100%{-webkit-transform:scale(2.5);transform:scale(2.5);opacity:1}}@-webkit-keyframes quantumWizRadialInkFocusPulse{0%{-webkit-transform:scale(2);transform:scale(2);opacity:0}100%{-webkit-transform:scale(2.5);transform:scale(2.5);opacity:1}}@keyframes quantumWizRadialInkFocusPulse{0%{-webkit-transform:scale(2);transform:scale(2);opacity:0}100%{-webkit-transform:scale(2.5);transform:scale(2.5);opacity:1}}:root{--wf-tfs:calc(var(--c-tfs,32)/16*1rem);--wf-tfs-bp2:calc(var(--c-tfs,36)/16*1rem);--wf-tfs-bp3:calc(var(--c-tfs,36)/16*1rem);--wf-tfs-bp5:calc(var(--c-tfs,44)/16*1rem);--wf-stfs:calc(var(--c-stfs,16)/16*1rem);--wf-stfs-bp5:calc(var(--c-stfs,16)/16*1rem)}:root{--wf-harmonize-filter-light:none;--wf-harmonize-filter-dark:none}.Dzz9Db,.GpMPBe{display:block;height:25vh;position:relative}@media (min-width:600px){.Dzz9Db,.GpMPBe{height:150px}}@media screen and (prefers-color-scheme:dark){.Dzz9Db:not(.GtvzYd){display:none}}.Dzz9Db.Irjbwb{height:auto}.GpMPBe{margin:0;overflow:hidden}.UFQPDd,.JNOvdd{display:block;height:100%;margin:0 auto;-o-object-fit:contain;object-fit:contain;width:100%}.f4ZpM{display:block;-webkit-filter:var(--wf-harmonize-filter-light);filter:var(--wf-harmonize-filter-light);height:100%;max-width:100%;min-height:110px;position:relative;-webkit-transform:translate(-43%,-3%);-ms-transform:translate(-43%,-3%);transform:translate(-43%,-3%);width:auto;z-index:3}@media screen and (prefers-color-scheme:dark){.f4ZpM{-webkit-filter:var(--wf-harmonize-filter-dark);filter:var(--wf-harmonize-filter-dark)}}.wsArZ[data-ss-mode="1"] .Dzz9Db,.wsArZ[data-ss-mode="1"] .f4ZpM{height:auto;width:100%}.wsArZ[data-ss-mode="1"] .f4ZpM{max-width:400px}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .Dzz9Db,.NQ5OL .f4ZpM{height:auto;width:100%}.NQ5OL .f4ZpM{max-width:400px}}.Dzz9Db.utFBGf,.Dzz9Db.utFBGf .f4ZpM{height:auto}.Dzz9Db.utFBGf .f4ZpM{height:auto;max-width:312px;width:100%}.Dzz9Db.utFBGf.zpCp3 .f4ZpM{max-width:unset}.Dzz9Db.IiQozc .f4ZpM{margin:0 auto;-webkit-transform:none;-ms-transform:none;transform:none}.Dzz9Db.Irjbwb .f4ZpM{height:auto;width:100%}.Dzz9Db.EEeaqf .f4ZpM{max-height:144px;max-width:144px}.nPt1pc{background-image:-webkit-gradient(linear,left top,left bottom,from(rgba(233,233,233,0)),color-stop(62.22%,rgba(233,233,233,0)),color-stop(40.22%,rgb(233,233,233)),to(rgba(233,233,233,0)));background-image:-webkit-linear-gradient(top,rgba(233,233,233,0) 0,rgba(233,233,233,0) 62.22%,rgb(233,233,233) 40.22%,rgba(233,233,233,0) 100%);background-image:linear-gradient(to bottom,rgba(233,233,233,0) 0,rgba(233,233,233,0) 62.22%,rgb(233,233,233) 40.22%,rgba(233,233,233,0) 100%);height:100%;left:0;overflow:hidden;position:absolute;right:0;top:0;z-index:2}@media screen and (prefers-color-scheme:dark){.nPt1pc{display:none}}.nPt1pc::after,.nPt1pc::before{content:"";display:block;height:100%;min-width:110px;position:absolute;right:-10%;-webkit-transform:rotate(-104deg);-ms-transform:rotate(-104deg);transform:rotate(-104deg);width:25vh;z-index:2}@media (min-width:600px){.nPt1pc::after,.nPt1pc::before{width:150px}}.nPt1pc::before{background-image:-webkit-gradient(linear,left top,left bottom,from(rgba(243,243,243,0)),to(rgba(243,243,243,.9)));background-image:-webkit-linear-gradient(top,rgba(243,243,243,0) 0,rgba(243,243,243,.9) 100%);background-image:linear-gradient(to bottom,rgba(243,243,243,0) 0,rgba(243,243,243,.9) 100%);bottom:-10%}.nPt1pc::after{background-image:-webkit-gradient(linear,left top,left bottom,from(rgba(255,255,255,0)),to(rgba(255,255,255,.9)));background-image:-webkit-linear-gradient(top,rgba(255,255,255,0) 0,rgba(255,255,255,.9) 100%);background-image:linear-gradient(to bottom,rgba(255,255,255,0) 0,rgba(255,255,255,.9) 100%);bottom:-80%}.wsArZ[data-ss-mode="1"] .nPt1pc~.f4ZpM{width:auto}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .nPt1pc~.f4ZpM{width:auto}}.ZS7CGc .f4ZpM{height:auto}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .ZS7CGc .f4ZpM{width:115px}}.qiRZ5e .f4ZpM{-webkit-transform:translate(-9%,-3%);-ms-transform:translate(-9%,-3%);transform:translate(-9%,-3%)}.vIv7Gf .f4ZpM{margin:auto;max-height:230px;right:0;top:-3%;-webkit-transform:none;-ms-transform:none;transform:none}.nvYXVd .f4ZpM{-webkit-transform:translate(9%,-3%);-ms-transform:translate(9%,-3%);transform:translate(9%,-3%)}.uOhnzd .f4ZpM{-webkit-transform:translate(24px,0);-ms-transform:translate(24px,0);transform:translate(24px,0)}.MsYMaf .f4ZpM{-webkit-transform:translate(0,0);-ms-transform:translate(0,0);transform:translate(0,0)}.wsArZ[data-ss-mode="1"] .YIi9qf .f4ZpM{max-width:115px}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .YIi9qf .f4ZpM{max-width:115px}}.QG3Xbe .f4ZpM{max-width:300px}.F6gtje .f4ZpM{-webkit-transform:none;-ms-transform:none;transform:none}@-webkit-keyframes mdc-ripple-fg-radius-in{from{-webkit-animation-timing-function:cubic-bezier(.4,0,.2,1);animation-timing-function:cubic-bezier(.4,0,.2,1);-webkit-transform:translate(var(--mdc-ripple-fg-translate-start,0)) scale(1);transform:translate(var(--mdc-ripple-fg-translate-start,0)) scale(1)}to{-webkit-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1))}}@keyframes mdc-ripple-fg-radius-in{from{-webkit-animation-timing-function:cubic-bezier(.4,0,.2,1);animation-timing-function:cubic-bezier(.4,0,.2,1);-webkit-transform:translate(var(--mdc-ripple-fg-translate-start,0)) scale(1);transform:translate(var(--mdc-ripple-fg-translate-start,0)) scale(1)}to{-webkit-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1))}}@-webkit-keyframes mdc-ripple-fg-opacity-in{from{-webkit-animation-timing-function:linear;animation-timing-function:linear;opacity:0}to{opacity:var(--mdc-ripple-fg-opacity,0)}}@keyframes mdc-ripple-fg-opacity-in{from{-webkit-animation-timing-function:linear;animation-timing-function:linear;opacity:0}to{opacity:var(--mdc-ripple-fg-opacity,0)}}@-webkit-keyframes mdc-ripple-fg-opacity-out{from{-webkit-animation-timing-function:linear;animation-timing-function:linear;opacity:var(--mdc-ripple-fg-opacity,0)}to{opacity:0}}@keyframes mdc-ripple-fg-opacity-out{from{-webkit-animation-timing-function:linear;animation-timing-function:linear;opacity:var(--mdc-ripple-fg-opacity,0)}to{opacity:0}}.VfPpkd-ksKsZd-XxIAqe{--mdc-ripple-fg-size:0;--mdc-ripple-left:0;--mdc-ripple-top:0;--mdc-ripple-fg-scale:1;--mdc-ripple-fg-translate-end:0;--mdc-ripple-fg-translate-start:0;-webkit-tap-highlight-color:rgba(0,0,0,0);will-change:transform,opacity;position:relative;outline:none;overflow:hidden}.VfPpkd-ksKsZd-XxIAqe::before,.VfPpkd-ksKsZd-XxIAqe::after{position:absolute;border-radius:50%;opacity:0;pointer-events:none;content:""}.VfPpkd-ksKsZd-XxIAqe::before{-webkit-transition:opacity 15ms linear,background-color 15ms linear;transition:opacity 15ms linear,background-color 15ms linear;z-index:1;z-index:var(--mdc-ripple-z-index,1)}.VfPpkd-ksKsZd-XxIAqe::after{z-index:0;z-index:var(--mdc-ripple-z-index,0)}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d::before{-webkit-transform:scale(var(--mdc-ripple-fg-scale,1));-ms-transform:scale(var(--mdc-ripple-fg-scale,1));transform:scale(var(--mdc-ripple-fg-scale,1))}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d::after{top:0;left:0;-webkit-transform:scale(0);-ms-transform:scale(0);transform:scale(0);-webkit-transform-origin:center center;-ms-transform-origin:center center;transform-origin:center center}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd::after{top:var(--mdc-ripple-top,0);left:var(--mdc-ripple-left,0)}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-Tv8l5d-lJfZMc::after{-webkit-animation:mdc-ripple-fg-radius-in 225ms forwards,mdc-ripple-fg-opacity-in 75ms forwards;animation:mdc-ripple-fg-radius-in 225ms forwards,mdc-ripple-fg-opacity-in 75ms forwards}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-Tv8l5d-OmS1vf::after{-webkit-animation:mdc-ripple-fg-opacity-out .15s;animation:mdc-ripple-fg-opacity-out .15s;-webkit-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));-ms-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1))}.VfPpkd-ksKsZd-XxIAqe::before,.VfPpkd-ksKsZd-XxIAqe::after{top:-50%;left:-50%;width:200%;height:200%}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d::after{width:var(--mdc-ripple-fg-size,100%);height:var(--mdc-ripple-fg-size,100%)}.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded],.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd{overflow:visible}.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded]::before,.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded]::after,.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd::before,.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd::after{top:0;left:0;width:100%;height:100%}.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded].VfPpkd-ksKsZd-mWPk3d::before,.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded].VfPpkd-ksKsZd-mWPk3d::after,.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd.VfPpkd-ksKsZd-mWPk3d::before,.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd.VfPpkd-ksKsZd-mWPk3d::after{top:var(--mdc-ripple-top,0);left:var(--mdc-ripple-left,0);width:var(--mdc-ripple-fg-size,100%);height:var(--mdc-ripple-fg-size,100%)}.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded].VfPpkd-ksKsZd-mWPk3d::after,.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd.VfPpkd-ksKsZd-mWPk3d::after{width:var(--mdc-ripple-fg-size,100%);height:var(--mdc-ripple-fg-size,100%)}.VfPpkd-ksKsZd-XxIAqe::before,.VfPpkd-ksKsZd-XxIAqe::after{background-color:#000;background-color:var(--mdc-ripple-color,#000)}.VfPpkd-ksKsZd-XxIAqe:hover::before,.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE::before{opacity:.04;opacity:var(--mdc-ripple-hover-opacity,.04)}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe::before,.VfPpkd-ksKsZd-XxIAqe:not(.VfPpkd-ksKsZd-mWPk3d):focus::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12;opacity:var(--mdc-ripple-focus-opacity,.12)}.VfPpkd-ksKsZd-XxIAqe:not(.VfPpkd-ksKsZd-mWPk3d)::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.VfPpkd-ksKsZd-XxIAqe:not(.VfPpkd-ksKsZd-mWPk3d):active::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12;opacity:var(--mdc-ripple-press-opacity,.12)}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0.12)}.VfPpkd-Bz112c-LgbsSe{font-size:24px;width:48px;height:48px;padding:12px}.VfPpkd-Bz112c-LgbsSe.VfPpkd-Bz112c-LgbsSe-OWXEXe-e5LLRc-SxQuSe .VfPpkd-Bz112c-Jh9lGc{width:40px;height:40px;margin-top:4px;margin-bottom:4px;margin-right:4px;margin-left:4px}.VfPpkd-Bz112c-LgbsSe.VfPpkd-Bz112c-LgbsSe-OWXEXe-e5LLRc-SxQuSe .VfPpkd-Bz112c-J1Ukfc-LhBDec{max-height:40px;max-width:40px}.VfPpkd-Bz112c-LgbsSe:disabled{color:rgba(0,0,0,.38);color:var(--mdc-theme-text-disabled-on-light,rgba(0,0,0,.38))}.VfPpkd-Bz112c-LgbsSe svg,.VfPpkd-Bz112c-LgbsSe img{width:24px;height:24px}.VfPpkd-Bz112c-LgbsSe{display:inline-block;position:relative;-webkit-box-sizing:border-box;box-sizing:border-box;border:none;outline:none;background-color:transparent;fill:currentColor;color:inherit;text-decoration:none;cursor:pointer;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none;z-index:0;overflow:visible}.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-RLmnJb{position:absolute;top:50%;height:48px;left:50%;width:48px;-webkit-transform:translate(-50%,-50%);-ms-transform:translate(-50%,-50%);transform:translate(-50%,-50%)}@media screen and (forced-colors:active){.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Bz112c-J1Ukfc-LhBDec,.VfPpkd-Bz112c-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Bz112c-J1Ukfc-LhBDec{display:block}}.VfPpkd-Bz112c-LgbsSe:disabled{cursor:default;pointer-events:none}.VfPpkd-Bz112c-LgbsSe[hidden]{display:none}.VfPpkd-Bz112c-LgbsSe-OWXEXe-KVuj8d-Q3DXx{-webkit-box-align:center;-webkit-align-items:center;align-items:center;display:-webkit-inline-box;display:-webkit-inline-flex;display:inline-flex;-webkit-box-pack:center;-webkit-justify-content:center;justify-content:center}.VfPpkd-Bz112c-J1Ukfc-LhBDec{pointer-events:none;border:2px solid transparent;border-radius:6px;-webkit-box-sizing:content-box;box-sizing:content-box;position:absolute;top:50%;left:50%;-webkit-transform:translate(-50%,-50%);-ms-transform:translate(-50%,-50%);transform:translate(-50%,-50%);height:100%;width:100%;display:none}@media screen and (forced-colors:active){.VfPpkd-Bz112c-J1Ukfc-LhBDec{border-color:CanvasText}}.VfPpkd-Bz112c-J1Ukfc-LhBDec::after{content:"";border:2px solid transparent;border-radius:8px;display:block;position:absolute;top:50%;left:50%;-webkit-transform:translate(-50%,-50%);-ms-transform:translate(-50%,-50%);transform:translate(-50%,-50%);height:calc(100% + 4px);width:calc(100% + 4px)}@media screen and (forced-colors:active){.VfPpkd-Bz112c-J1Ukfc-LhBDec::after{border-color:CanvasText}}.VfPpkd-Bz112c-kBDsod{display:inline-block}.VfPpkd-Bz112c-kBDsod.VfPpkd-Bz112c-kBDsod-OWXEXe-IT5dJd,.VfPpkd-Bz112c-LgbsSe-OWXEXe-IT5dJd .VfPpkd-Bz112c-kBDsod{display:none}.VfPpkd-Bz112c-LgbsSe-OWXEXe-IT5dJd .VfPpkd-Bz112c-kBDsod.VfPpkd-Bz112c-kBDsod-OWXEXe-IT5dJd{display:inline-block}.VfPpkd-Bz112c-mRLv6{height:100%;left:0;outline:none;position:absolute;top:0;width:100%}.VfPpkd-Bz112c-LgbsSe{--mdc-ripple-fg-size:0;--mdc-ripple-left:0;--mdc-ripple-top:0;--mdc-ripple-fg-scale:1;--mdc-ripple-fg-translate-end:0;--mdc-ripple-fg-translate-start:0;-webkit-tap-highlight-color:rgba(0,0,0,0);will-change:transform,opacity}.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::after{position:absolute;border-radius:50%;opacity:0;pointer-events:none;content:""}.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::before{-webkit-transition:opacity 15ms linear,background-color 15ms linear;transition:opacity 15ms linear,background-color 15ms linear;z-index:1;z-index:var(--mdc-ripple-z-index,1)}.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::after{z-index:0;z-index:var(--mdc-ripple-z-index,0)}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Bz112c-Jh9lGc::before{-webkit-transform:scale(var(--mdc-ripple-fg-scale,1));-ms-transform:scale(var(--mdc-ripple-fg-scale,1));transform:scale(var(--mdc-ripple-fg-scale,1))}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Bz112c-Jh9lGc::after{top:0;left:0;-webkit-transform:scale(0);-ms-transform:scale(0);transform:scale(0);-webkit-transform-origin:center center;-ms-transform-origin:center center;transform-origin:center center}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd .VfPpkd-Bz112c-Jh9lGc::after{top:var(--mdc-ripple-top,0);left:var(--mdc-ripple-left,0)}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-Tv8l5d-lJfZMc .VfPpkd-Bz112c-Jh9lGc::after{-webkit-animation:mdc-ripple-fg-radius-in 225ms forwards,mdc-ripple-fg-opacity-in 75ms forwards;animation:mdc-ripple-fg-radius-in 225ms forwards,mdc-ripple-fg-opacity-in 75ms forwards}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-Tv8l5d-OmS1vf .VfPpkd-Bz112c-Jh9lGc::after{-webkit-animation:mdc-ripple-fg-opacity-out .15s;animation:mdc-ripple-fg-opacity-out .15s;-webkit-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));-ms-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1))}.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::after{top:0;left:0;width:100%;height:100%}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Bz112c-Jh9lGc::after{top:var(--mdc-ripple-top,0);left:var(--mdc-ripple-left,0);width:var(--mdc-ripple-fg-size,100%);height:var(--mdc-ripple-fg-size,100%)}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Bz112c-Jh9lGc::after{width:var(--mdc-ripple-fg-size,100%);height:var(--mdc-ripple-fg-size,100%)}.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::after{background-color:#000;background-color:var(--mdc-ripple-color,#000)}.VfPpkd-Bz112c-LgbsSe:hover .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Bz112c-Jh9lGc::before{opacity:.04;opacity:var(--mdc-ripple-hover-opacity,.04)}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Bz112c-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12;opacity:var(--mdc-ripple-focus-opacity,.12)}.VfPpkd-Bz112c-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Bz112c-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.VfPpkd-Bz112c-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Bz112c-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12;opacity:var(--mdc-ripple-press-opacity,.12)}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0.12)}.VfPpkd-Bz112c-LgbsSe:disabled:hover .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe:disabled.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Bz112c-Jh9lGc::before{opacity:0;opacity:var(--mdc-ripple-hover-opacity,0)}.VfPpkd-Bz112c-LgbsSe:disabled.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe:disabled:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Bz112c-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:0;opacity:var(--mdc-ripple-focus-opacity,0)}.VfPpkd-Bz112c-LgbsSe:disabled:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Bz112c-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.VfPpkd-Bz112c-LgbsSe:disabled:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Bz112c-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:0;opacity:var(--mdc-ripple-press-opacity,0)}.VfPpkd-Bz112c-LgbsSe:disabled.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0)}.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc{height:100%;left:0;pointer-events:none;position:absolute;top:0;width:100%;z-index:-1}.VfPpkd-dgl2Hf-ppHlrf-sM5MNb{display:inline}.VfPpkd-LgbsSe{position:relative;display:-webkit-inline-box;display:-webkit-inline-flex;display:inline-flex;-webkit-box-align:center;-webkit-align-items:center;align-items:center;-webkit-box-pack:center;-webkit-justify-content:center;justify-content:center;-webkit-box-sizing:border-box;box-sizing:border-box;min-width:64px;border:none;outline:none;line-height:inherit;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none;-webkit-appearance:none;overflow:visible;vertical-align:middle;background:transparent}.VfPpkd-LgbsSe .VfPpkd-BFbNVe-bF1uUb{width:100%;height:100%;top:0;left:0}.VfPpkd-LgbsSe::-moz-focus-inner{padding:0;border:0}.VfPpkd-LgbsSe:active{outline:none}.VfPpkd-LgbsSe:hover{cursor:pointer}.VfPpkd-LgbsSe:disabled{cursor:default;pointer-events:none}.VfPpkd-LgbsSe[hidden]{display:none}.VfPpkd-LgbsSe .VfPpkd-kBDsod{margin-left:0;margin-right:8px;display:inline-block;position:relative;vertical-align:top}[dir=rtl] .VfPpkd-LgbsSe .VfPpkd-kBDsod,.VfPpkd-LgbsSe .VfPpkd-kBDsod[dir=rtl]{margin-left:8px;margin-right:0}.VfPpkd-LgbsSe .VfPpkd-UdE5de-uDEFge{font-size:0;position:absolute;-webkit-transform:translate(-50%,-50%);-ms-transform:translate(-50%,-50%);transform:translate(-50%,-50%);top:50%;left:50%;line-height:normal}.VfPpkd-LgbsSe .VfPpkd-vQzf8d{position:relative}.VfPpkd-LgbsSe .VfPpkd-J1Ukfc-LhBDec{pointer-events:none;border:2px solid transparent;border-radius:6px;-webkit-box-sizing:content-box;box-sizing:content-box;position:absolute;top:50%;left:50%;-webkit-transform:translate(-50%,-50%);-ms-transform:translate(-50%,-50%);transform:translate(-50%,-50%);height:calc(100% + 4px);width:calc(100% + 4px);display:none}@media screen and (forced-colors:active){.VfPpkd-LgbsSe .VfPpkd-J1Ukfc-LhBDec{border-color:CanvasText}}.VfPpkd-LgbsSe .VfPpkd-J1Ukfc-LhBDec::after{content:"";border:2px solid transparent;border-radius:8px;display:block;position:absolute;top:50%;left:50%;-webkit-transform:translate(-50%,-50%);-ms-transform:translate(-50%,-50%);transform:translate(-50%,-50%);height:calc(100% + 4px);width:calc(100% + 4px)}@media screen and (forced-colors:active){.VfPpkd-LgbsSe .VfPpkd-J1Ukfc-LhBDec::after{border-color:CanvasText}}@media screen and (forced-colors:active){.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-J1Ukfc-LhBDec,.VfPpkd-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-J1Ukfc-LhBDec{display:block}}.VfPpkd-LgbsSe .VfPpkd-RLmnJb{position:absolute;top:50%;height:48px;left:0;right:0;-webkit-transform:translateY(-50%);-ms-transform:translateY(-50%);transform:translateY(-50%)}.VfPpkd-vQzf8d+.VfPpkd-kBDsod{margin-left:8px;margin-right:0}[dir=rtl] .VfPpkd-vQzf8d+.VfPpkd-kBDsod,.VfPpkd-vQzf8d+.VfPpkd-kBDsod[dir=rtl]{margin-left:0;margin-right:8px}svg.VfPpkd-kBDsod{fill:currentColor}.VfPpkd-LgbsSe-OWXEXe-dgl2Hf{margin-top:6px;margin-bottom:6px}.VfPpkd-LgbsSe{-moz-osx-font-smoothing:grayscale;-webkit-font-smoothing:antialiased;text-decoration:none}.VfPpkd-LgbsSe{padding:0 8px 0 8px}.VfPpkd-LgbsSe-OWXEXe-k8QpJ{-webkit-transition:-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:box-shadow .28s cubic-bezier(.4,0,.2,1);transition:box-shadow .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);padding:0 16px 0 16px}.VfPpkd-LgbsSe-OWXEXe-k8QpJ.VfPpkd-LgbsSe-OWXEXe-Bz112c-UbuQg{padding:0 12px 0 16px}.VfPpkd-LgbsSe-OWXEXe-k8QpJ.VfPpkd-LgbsSe-OWXEXe-Bz112c-M1Soyc{padding:0 16px 0 12px}.VfPpkd-LgbsSe-OWXEXe-MV7yeb{-webkit-transition:-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:box-shadow .28s cubic-bezier(.4,0,.2,1);transition:box-shadow .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);padding:0 16px 0 16px}.VfPpkd-LgbsSe-OWXEXe-MV7yeb.VfPpkd-LgbsSe-OWXEXe-Bz112c-UbuQg{padding:0 12px 0 16px}.VfPpkd-LgbsSe-OWXEXe-MV7yeb.VfPpkd-LgbsSe-OWXEXe-Bz112c-M1Soyc{padding:0 16px 0 12px}.VfPpkd-LgbsSe-OWXEXe-INsAgc{border-style:solid;-webkit-transition:border .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1)}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-Jh9lGc{border-style:solid;border-color:transparent}.VfPpkd-LgbsSe{--mdc-ripple-fg-size:0;--mdc-ripple-left:0;--mdc-ripple-top:0;--mdc-ripple-fg-scale:1;--mdc-ripple-fg-translate-end:0;--mdc-ripple-fg-translate-start:0;-webkit-tap-highlight-color:rgba(0,0,0,0);will-change:transform,opacity}.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::after{position:absolute;border-radius:50%;opacity:0;pointer-events:none;content:""}.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::before{-webkit-transition:opacity 15ms linear,background-color 15ms linear;transition:opacity 15ms linear,background-color 15ms linear;z-index:1}.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::after{z-index:0}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Jh9lGc::before{-webkit-transform:scale(var(--mdc-ripple-fg-scale,1));-ms-transform:scale(var(--mdc-ripple-fg-scale,1));transform:scale(var(--mdc-ripple-fg-scale,1))}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Jh9lGc::after{top:0;left:0;-webkit-transform:scale(0);-ms-transform:scale(0);transform:scale(0);-webkit-transform-origin:center center;-ms-transform-origin:center center;transform-origin:center center}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd .VfPpkd-Jh9lGc::after{top:var(--mdc-ripple-top,0);left:var(--mdc-ripple-left,0)}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-Tv8l5d-lJfZMc .VfPpkd-Jh9lGc::after{-webkit-animation:mdc-ripple-fg-radius-in 225ms forwards,mdc-ripple-fg-opacity-in 75ms forwards;animation:mdc-ripple-fg-radius-in 225ms forwards,mdc-ripple-fg-opacity-in 75ms forwards}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-Tv8l5d-OmS1vf .VfPpkd-Jh9lGc::after{-webkit-animation:mdc-ripple-fg-opacity-out .15s;animation:mdc-ripple-fg-opacity-out .15s;-webkit-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));-ms-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1))}.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::after{top:-50%;left:-50%;width:200%;height:200%}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Jh9lGc::after{width:var(--mdc-ripple-fg-size,100%);height:var(--mdc-ripple-fg-size,100%)}.VfPpkd-Jh9lGc{position:absolute;-webkit-box-sizing:content-box;box-sizing:content-box;overflow:hidden;z-index:0;top:0;left:0;bottom:0;right:0}.VfPpkd-LgbsSe{font-family:Roboto,sans-serif;font-size:.875rem;letter-spacing:.0892857143em;font-weight:500;text-transform:uppercase;height:36px;border-radius:4px}.VfPpkd-LgbsSe:not(:disabled){color:#6200ee}.VfPpkd-LgbsSe:disabled{color:rgba(0,0,0,.38)}.VfPpkd-LgbsSe .VfPpkd-kBDsod{font-size:1.125rem;width:1.125rem;height:1.125rem}.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::before{background-color:#6200ee}.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::after{background-color:#6200ee}.VfPpkd-LgbsSe:hover .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:.04}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12}.VfPpkd-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.VfPpkd-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-text-button-pressed-state-layer-opacity,0.12)}.VfPpkd-LgbsSe .VfPpkd-Jh9lGc{border-radius:4px}.VfPpkd-LgbsSe .VfPpkd-J1Ukfc-LhBDec{border-radius:2px}.VfPpkd-LgbsSe .VfPpkd-J1Ukfc-LhBDec::after{border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-k8QpJ{font-family:Roboto,sans-serif;font-size:.875rem;letter-spacing:.0892857143em;font-weight:500;text-transform:uppercase;height:36px;border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-k8QpJ:not(:disabled){background-color:#6200ee}.VfPpkd-LgbsSe-OWXEXe-k8QpJ:disabled{background-color:rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-k8QpJ:not(:disabled){color:#fff}.VfPpkd-LgbsSe-OWXEXe-k8QpJ:disabled{color:rgba(0,0,0,.38)}.VfPpkd-LgbsSe-OWXEXe-k8QpJ .VfPpkd-kBDsod{font-size:1.125rem;width:1.125rem;height:1.125rem}.VfPpkd-LgbsSe-OWXEXe-k8QpJ .VfPpkd-Jh9lGc::before{background-color:#fff}.VfPpkd-LgbsSe-OWXEXe-k8QpJ .VfPpkd-Jh9lGc::after{background-color:#fff}.VfPpkd-LgbsSe-OWXEXe-k8QpJ:hover .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe-OWXEXe-k8QpJ.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:.08}.VfPpkd-LgbsSe-OWXEXe-k8QpJ.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe-OWXEXe-k8QpJ:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.24}.VfPpkd-LgbsSe-OWXEXe-k8QpJ:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.VfPpkd-LgbsSe-OWXEXe-k8QpJ:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.24}.VfPpkd-LgbsSe-OWXEXe-k8QpJ.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-filled-button-pressed-state-layer-opacity,0.24)}.VfPpkd-LgbsSe-OWXEXe-k8QpJ .VfPpkd-Jh9lGc{border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-k8QpJ .VfPpkd-J1Ukfc-LhBDec{border-radius:2px}.VfPpkd-LgbsSe-OWXEXe-k8QpJ .VfPpkd-J1Ukfc-LhBDec::after{border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-MV7yeb{font-family:Roboto,sans-serif;font-size:.875rem;letter-spacing:.0892857143em;font-weight:500;text-transform:uppercase;height:36px;border-radius:4px;-webkit-box-shadow:0 3px 1px -2px rgba(0,0,0,.2),0 2px 2px 0 rgba(0,0,0,.14),0 1px 5px 0 rgba(0,0,0,.12);box-shadow:0 3px 1px -2px rgba(0,0,0,.2),0 2px 2px 0 rgba(0,0,0,.14),0 1px 5px 0 rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:not(:disabled){background-color:#6200ee}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:disabled{background-color:rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:not(:disabled){color:#fff}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:disabled{color:rgba(0,0,0,.38)}.VfPpkd-LgbsSe-OWXEXe-MV7yeb .VfPpkd-kBDsod{font-size:1.125rem;width:1.125rem;height:1.125rem}.VfPpkd-LgbsSe-OWXEXe-MV7yeb .VfPpkd-Jh9lGc::before{background-color:#fff}.VfPpkd-LgbsSe-OWXEXe-MV7yeb .VfPpkd-Jh9lGc::after{background-color:#fff}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:hover .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe-OWXEXe-MV7yeb.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:.08}.VfPpkd-LgbsSe-OWXEXe-MV7yeb.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe-OWXEXe-MV7yeb:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.24}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.24}.VfPpkd-LgbsSe-OWXEXe-MV7yeb.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-protected-button-pressed-state-layer-opacity,0.24)}.VfPpkd-LgbsSe-OWXEXe-MV7yeb .VfPpkd-Jh9lGc{border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-MV7yeb .VfPpkd-J1Ukfc-LhBDec{border-radius:2px}.VfPpkd-LgbsSe-OWXEXe-MV7yeb .VfPpkd-J1Ukfc-LhBDec::after{border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-MV7yeb.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe,.VfPpkd-LgbsSe-OWXEXe-MV7yeb:not(.VfPpkd-ksKsZd-mWPk3d):focus{-webkit-box-shadow:0 2px 4px -1px rgba(0,0,0,.2),0 4px 5px 0 rgba(0,0,0,.14),0 1px 10px 0 rgba(0,0,0,.12);box-shadow:0 2px 4px -1px rgba(0,0,0,.2),0 4px 5px 0 rgba(0,0,0,.14),0 1px 10px 0 rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:hover{-webkit-box-shadow:0 2px 4px -1px rgba(0,0,0,.2),0 4px 5px 0 rgba(0,0,0,.14),0 1px 10px 0 rgba(0,0,0,.12);box-shadow:0 2px 4px -1px rgba(0,0,0,.2),0 4px 5px 0 rgba(0,0,0,.14),0 1px 10px 0 rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:not(:disabled):active{-webkit-box-shadow:0 5px 5px -3px rgba(0,0,0,.2),0 8px 10px 1px rgba(0,0,0,.14),0 3px 14px 2px rgba(0,0,0,.12);box-shadow:0 5px 5px -3px rgba(0,0,0,.2),0 8px 10px 1px rgba(0,0,0,.14),0 3px 14px 2px rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:disabled{-webkit-box-shadow:0 0 0 0 rgba(0,0,0,.2),0 0 0 0 rgba(0,0,0,.14),0 0 0 0 rgba(0,0,0,.12);box-shadow:0 0 0 0 rgba(0,0,0,.2),0 0 0 0 rgba(0,0,0,.14),0 0 0 0 rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-INsAgc{font-family:Roboto,sans-serif;font-size:.875rem;letter-spacing:.0892857143em;font-weight:500;text-transform:uppercase;height:36px;border-radius:4px;padding:0 15px 0 15px;border-width:1px}.VfPpkd-LgbsSe-OWXEXe-INsAgc:not(:disabled){color:#6200ee}.VfPpkd-LgbsSe-OWXEXe-INsAgc:disabled{color:rgba(0,0,0,.38)}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-kBDsod{font-size:1.125rem;width:1.125rem;height:1.125rem}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-Jh9lGc::before{background-color:#6200ee}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-Jh9lGc::after{background-color:#6200ee}.VfPpkd-LgbsSe-OWXEXe-INsAgc:hover .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe-OWXEXe-INsAgc.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:.04}.VfPpkd-LgbsSe-OWXEXe-INsAgc.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe-OWXEXe-INsAgc:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12}.VfPpkd-LgbsSe-OWXEXe-INsAgc:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.VfPpkd-LgbsSe-OWXEXe-INsAgc:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12}.VfPpkd-LgbsSe-OWXEXe-INsAgc.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-outlined-button-pressed-state-layer-opacity,0.12)}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-Jh9lGc{border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-J1Ukfc-LhBDec{border-radius:2px}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-J1Ukfc-LhBDec::after{border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-INsAgc:not(:disabled){border-color:rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-INsAgc:disabled{border-color:rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-INsAgc.VfPpkd-LgbsSe-OWXEXe-Bz112c-UbuQg{padding:0 11px 0 15px}.VfPpkd-LgbsSe-OWXEXe-INsAgc.VfPpkd-LgbsSe-OWXEXe-Bz112c-M1Soyc{padding:0 15px 0 11px}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-Jh9lGc{top:-1px;left:-1px;bottom:-1px;right:-1px;border-width:1px}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-RLmnJb{left:-1px;width:calc(100% + 2px)}.nCP5yc{font-family:"Google Sans",Roboto,Arial,sans-serif;font-size:.875rem;letter-spacing:.0107142857em;font-weight:500;text-transform:none;-webkit-transition:border .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),box-shadow .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);-webkit-box-shadow:none;box-shadow:none}.nCP5yc .VfPpkd-Jh9lGc{height:100%;position:absolute;overflow:hidden;width:100%;z-index:0}.nCP5yc:not(:disabled){background-color:rgb(26,115,232);background-color:var(--gm-fillbutton-container-color,rgb(26,115,232))}.nCP5yc:not(:disabled){color:#fff;color:var(--gm-fillbutton-ink-color,#fff)}.nCP5yc:disabled{background-color:rgba(60,64,67,.12);background-color:var(--gm-fillbutton-disabled-container-color,rgba(60,64,67,.12))}.nCP5yc:disabled{color:rgba(60,64,67,.38);color:var(--gm-fillbutton-disabled-ink-color,rgba(60,64,67,.38))}.nCP5yc .VfPpkd-Jh9lGc::before,.nCP5yc .VfPpkd-Jh9lGc::after{background-color:rgb(32,33,36);background-color:var(--gm-fillbutton-state-color,rgb(32,33,36))}.nCP5yc:hover .VfPpkd-Jh9lGc::before,.nCP5yc.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:.16;opacity:var(--mdc-ripple-hover-opacity,.16)}.nCP5yc.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.nCP5yc:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.24;opacity:var(--mdc-ripple-focus-opacity,.24)}.nCP5yc:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.nCP5yc:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.2;opacity:var(--mdc-ripple-press-opacity,.2)}.nCP5yc.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0.2)}.nCP5yc .VfPpkd-BFbNVe-bF1uUb{opacity:0}.nCP5yc .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-uI4vCe-LkdAo,.nCP5yc .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-IdXvz-LkdAo-Bd00G{stroke:#fff}@media (-ms-high-contrast:active),screen and (forced-colors:active){.nCP5yc .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-uI4vCe-LkdAo,.nCP5yc .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-IdXvz-LkdAo-Bd00G{stroke:CanvasText}}.nCP5yc:hover{-webkit-box-shadow:0 1px 2px 0 rgba(60,64,67,.3),0 1px 3px 1px rgba(60,64,67,.15);box-shadow:0 1px 2px 0 rgba(60,64,67,.3),0 1px 3px 1px rgba(60,64,67,.15);-webkit-box-shadow:0 1px 2px 0 var(--gm-fillbutton-keyshadow-color,rgba(60,64,67,.3)),0 1px 3px 1px var(--gm-fillbutton-ambientshadow-color,rgba(60,64,67,.15));box-shadow:0 1px 2px 0 var(--gm-fillbutton-keyshadow-color,rgba(60,64,67,.3)),0 1px 3px 1px var(--gm-fillbutton-ambientshadow-color,rgba(60,64,67,.15))}.nCP5yc:hover .VfPpkd-BFbNVe-bF1uUb{opacity:0}.nCP5yc:active{-webkit-box-shadow:0 1px 2px 0 rgba(60,64,67,.3),0 2px 6px 2px rgba(60,64,67,.15);box-shadow:0 1px 2px 0 rgba(60,64,67,.3),0 2px 6px 2px rgba(60,64,67,.15);-webkit-box-shadow:0 1px 2px 0 var(--gm-fillbutton-keyshadow-color,rgba(60,64,67,.3)),0 2px 6px 2px var(--gm-fillbutton-ambientshadow-color,rgba(60,64,67,.15));box-shadow:0 1px 2px 0 var(--gm-fillbutton-keyshadow-color,rgba(60,64,67,.3)),0 2px 6px 2px var(--gm-fillbutton-ambientshadow-color,rgba(60,64,67,.15))}.nCP5yc:active .VfPpkd-BFbNVe-bF1uUb{opacity:0}.nCP5yc:disabled{-webkit-box-shadow:none;box-shadow:none}.nCP5yc:disabled:hover .VfPpkd-Jh9lGc::before,.nCP5yc:disabled.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:0;opacity:var(--mdc-ripple-hover-opacity,0)}.nCP5yc:disabled.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.nCP5yc:disabled:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:0;opacity:var(--mdc-ripple-focus-opacity,0)}.nCP5yc:disabled:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.nCP5yc:disabled:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:0;opacity:var(--mdc-ripple-press-opacity,0)}.nCP5yc:disabled.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0)}.nCP5yc:disabled .VfPpkd-BFbNVe-bF1uUb{opacity:0}.Rj2Mlf{font-family:"Google Sans",Roboto,Arial,sans-serif;font-size:.875rem;letter-spacing:.0107142857em;font-weight:500;text-transform:none;-webkit-transition:border .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),box-shadow .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);-webkit-box-shadow:none;box-shadow:none}.Rj2Mlf .VfPpkd-Jh9lGc{height:100%;position:absolute;overflow:hidden;width:100%;z-index:0}.Rj2Mlf:not(:disabled){color:rgb(26,115,232);color:var(--gm-hairlinebutton-ink-color,rgb(26,115,232))}.Rj2Mlf:not(:disabled){border-color:rgb(218,220,224);border-color:var(--gm-hairlinebutton-outline-color,rgb(218,220,224))}.Rj2Mlf:not(:disabled):hover{border-color:rgb(218,220,224);border-color:var(--gm-hairlinebutton-outline-color,rgb(218,220,224))}.Rj2Mlf:not(:disabled).VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe,.Rj2Mlf:not(:disabled):not(.VfPpkd-ksKsZd-mWPk3d):focus{border-color:rgb(23,78,166);border-color:var(--gm-hairlinebutton-outline-color--stateful,rgb(23,78,166))}.Rj2Mlf:not(:disabled):active,.Rj2Mlf:not(:disabled):focus:active{border-color:rgb(218,220,224);border-color:var(--gm-hairlinebutton-outline-color,rgb(218,220,224))}.Rj2Mlf:disabled{color:rgba(60,64,67,.38);color:var(--gm-hairlinebutton-disabled-ink-color,rgba(60,64,67,.38))}.Rj2Mlf:disabled{border-color:rgba(60,64,67,.12);border-color:var(--gm-hairlinebutton-disabled-outline-color,rgba(60,64,67,.12))}.Rj2Mlf:hover:not(:disabled),.Rj2Mlf.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe:not(:disabled),.Rj2Mlf:not(.VfPpkd-ksKsZd-mWPk3d):focus:not(:disabled),.Rj2Mlf:active:not(:disabled){color:rgb(23,78,166);color:var(--gm-hairlinebutton-ink-color--stateful,rgb(23,78,166))}.Rj2Mlf .VfPpkd-BFbNVe-bF1uUb{opacity:0}.Rj2Mlf .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-uI4vCe-LkdAo,.Rj2Mlf .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-IdXvz-LkdAo-Bd00G{stroke:rgb(26,115,232)}@media (-ms-high-contrast:active),screen and (forced-colors:active){.Rj2Mlf .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-uI4vCe-LkdAo,.Rj2Mlf .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-IdXvz-LkdAo-Bd00G{stroke:CanvasText}}.Rj2Mlf .VfPpkd-Jh9lGc::before,.Rj2Mlf .VfPpkd-Jh9lGc::after{background-color:rgb(26,115,232);background-color:var(--gm-hairlinebutton-state-color,rgb(26,115,232))}.Rj2Mlf:hover .VfPpkd-Jh9lGc::before,.Rj2Mlf.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:.04;opacity:var(--mdc-ripple-hover-opacity,.04)}.Rj2Mlf.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.Rj2Mlf:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12;opacity:var(--mdc-ripple-focus-opacity,.12)}.Rj2Mlf:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.Rj2Mlf:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12;opacity:var(--mdc-ripple-press-opacity,.12)}.Rj2Mlf.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0.12)}.Rj2Mlf:disabled:hover .VfPpkd-Jh9lGc::before,.Rj2Mlf:disabled.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:0;opacity:var(--mdc-ripple-hover-opacity,0)}.Rj2Mlf:disabled.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.Rj2Mlf:disabled:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:0;opacity:var(--mdc-ripple-focus-opacity,0)}.Rj2Mlf:disabled:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.Rj2Mlf:disabled:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:0;opacity:var(--mdc-ripple-press-opacity,0)}.Rj2Mlf:disabled.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0)}.b9hyVd{font-family:"Google Sans",Roboto,Arial,sans-serif;font-size:.875rem;letter-spacing:.0107142857em;font-weight:500;text-transform:none;-webkit-transition:border .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),box-shadow .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);border-width:0;-webkit-box-shadow:0 1px 2px 0 rgba(60,64,67,.3),0 1px 3px 1px rgba(60,64,67,.15);box-shadow:0 1px 2px 0 rgba(60,64,67,.3),0 1px 3px 1px rgba(60,64,67,.15);-webkit-box-shadow:0 1px 2px 0 var(--gm-protectedbutton-keyshadow-color,rgba(60,64,67,.3)),0 1px 3px 1px var(--gm-protectedbutton-ambientshadow-color,rgba(60,64,67,.15));box-shadow:0 1px 2px 0 var(--gm-protectedbutton-keyshadow-color,rgba(60,64,67,.3)),0 1px 3px 1px var(--gm-protectedbutton-ambientshadow-color,rgba(60,64,67,.15))}.b9hyVd .VfPpkd-Jh9lGc{height:100%;position:absolute;overflow:hidden;width:100%;z-index:0}.b9hyVd:not(:disabled){background-color:#fff;background-color:var(--gm-protectedbutton-container-color,#fff)}.b9hyVd:not(:disabled){color:rgb(26,115,232);color:var(--gm-protectedbutton-ink-color,rgb(26,115,232))}.b9hyVd:disabled{background-color:rgba(60,64,67,.12);background-color:var(--gm-protectedbutton-disabled-container-color,rgba(60,64,67,.12))}.b9hyVd:disabled{color:rgba(60,64,67,.38);color:var(--gm-protectedbutton-disabled-ink-color,rgba(60,64,67,.38))}.b9hyVd:hover:not(:disabled),.b9hyVd.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe:not(:disabled),.b9hyVd:not(.VfPpkd-ksKsZd-mWPk3d):focus:not(:disabled),.b9hyVd:active:not(:disabled){color:rgb(23,78,166);color:var(--gm-protectedbutton-ink-color--stateful,rgb(23,78,166))}.b9hyVd .VfPpkd-BFbNVe-bF1uUb{opacity:0}.b9hyVd .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-uI4vCe-LkdAo,.b9hyVd .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-IdXvz-LkdAo-Bd00G{stroke:rgb(26,115,232)}@media (-ms-high-contrast:active),screen and (forced-colors:active){.b9hyVd .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-uI4vCe-LkdAo,.b9hyVd .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-IdXvz-LkdAo-B | 2026-01-13T09:30:12 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.