Overview

The V4MOS.AI Google Search Console API gives you the raw search performance records (clicks, impressions, CTR and average position) of the Search Console properties connected to your organization, by day, country, device, page and query. Rows come as they were synced, with the warehouse column names (snake_case), so you can load them straight into your BI. All endpoints use the /v1/google-search-console prefix and the same authentication, pagination and response format.

Getting startedCopy Anchor Link

Base URL: https://data.v4mos.ai. Every call requires your API credentials and the organizationId — see Authentication.

1. Connect Google Search Console in app.v4mos.ai (Connected accounts) and wait for the first sync.
2. Call any endpoint below with your organizationId, for example GET /v1/google-search-console/daily?organizationId=….
3. Every row carries integration_id and integration_name: the connected property it came from. To read a single property, pass that value as integrationId.

Available endpointsCopy Anchor Link

• getDaily report/v1/google-search-console/dailyOne row per property and day: clicks, impressions, CTR and average position.
• getReport by country/v1/google-search-console/countriesOne row per property, day and country: clicks, impressions, CTR and average position.
• getReport by device/v1/google-search-console/devicesOne row per property, day and device type: clicks, impressions, CTR and average position.
• getReport by page/v1/google-search-console/pagesOne row per property, day and page URL: clicks, impressions, CTR and average position.
• getReport by query/v1/google-search-console/queriesOne row per property, day and search query: clicks, impressions, CTR and average position.

ResourcesCopy Anchor Link

Search Console data arrives about 3 days late. When aggregating rows, recompute CTR as clicks ÷ impressions instead of averaging CTR.

Pagination and filtersCopy Anchor Link

• page (default 1) and limit (default 500, max 5000). meta.hasNextPage says whether another page exists; rows come in a stable order, so walk the pages until it is false.
• dateFrom / dateTo (YYYY-MM-DD, inclusive) filter by the date column shown in the table above.
• integrationId keeps the rows of one connected property.
• Answers are cached for 30 minutes and the data is synced once a day — see Data sync.

Response formatCopy Anchor Link

{
  "data": [{ "...": "one object per row, with the columns listed on each endpoint" }],
  "meta": {
    "page": 1,
    "limit": 500,
    "hasNextPage": true,
    "hasPreviousPage": false
  }
}

Decimal values and large counters (format: decimal and format: int64 fields in each endpoint's schema) arrive as text, for example "125.50", so no precision is lost. Convert them to a numeric type on your side.