Custom Search JSON API returns 403 PERMISSION_DENIED on new org - new account restriction?

Google Cloud Cloud Foundations & Onboarding
1

I created a new Google Cloud org in March 2026. The Custom Search JSON API returns 403 PERMISSION_DENIED on every API call from every project in the org.

Error: “This project does not have the access to Custom Search JSON API.”
Status: PERMISSION_DENIED, reason: forbidden

Verified:

  • API is enabled on the GCP project, billing is active
  • No restrictServiceUsage org policies blocking it
  • Tested 3 API keys across 2 GCP projects — identical 403 on all
  • PSE engine ID is valid and accessible
  • Disabled and re-enabled the API via both gcloud CLI and Console UI

This appears to be a new-account restriction. Is there a process to get this lifted? Is there a minimum account age or verification step required for the Custom Search JSON API?

2

Hello @spine,

As noted in the documentation of Custom Search JSON API:

Note: The Custom Search JSON API is closed to new customers. Vertex AI Search is a favorable alternative for searching up to 50 domains. Alternatively, if your use case necessitates full web search, contact us to express your interest in and get more information about our full web search solution.

Existing Custom Search JSON API customers have until January 1, 2027 to transition to an alternative solution.

I would say that since it’s a new account / org, it won’t have access to this API anymore. You have to use Vertex AI Search.

3

Hi @LeoK
I have a similar issue. My setup is a personal Gmail account (no organization). I had the Custom Search JSON API working on a project created in mid-2025, so my account should be an existing customer. Recently I switched billing accounts and now get 403 “This project does not have the access to Custom Search JSON API” on all projects under my Gmail. My questions:

  1. Does “existing customer” status apply at the Gmail account level or at the individual project level?

  2. Can switching billing accounts cause loss of Custom Search API access on a previously working project?

  3. Is there any way to restore access on an existing project under a personal Gmail account?

4

Hello @Ojas_Patil,

That’s weird, but you’re not the only one apparently.

You’re not a new customer, you should still have access until January 1st, 2027.

Seems like the GCP team cut the access a little too harshly :thinking: