Get suppressed duplicate locations
Retrieves the count of locations identified as duplicates, grouped by directory type, within a date range. Optionally limits the result to a single directory type. Date parameters are passed as strings and validated server-side. Defaults to all available data (from 1970-01-01 up to today) if startDate is not provided. endDate defaults to today.
Query parameters
Start date (inclusive) as an ISO-8601 date or date-time, with or without zone/offset (e.g. 2025-01-01, 2025-01-01T14:30:00, 2025-01-01T14:30:00Z, 2025-01-01T14:30:00%2B02:00). Zone-aware values are normalised to UTC. The formats yyyy.MM.dd, dd.MM.yyyy, dd-MM-yyyy HH:mm:ss and dd.MM.yyyy HH:mm:ss are also accepted. Optional for most endpoints — defaults to a period before end date if omitted.
End date (inclusive) as an ISO-8601 date or date-time, with or without zone/offset. Zone-aware values are normalised to UTC. The formats yyyy.MM.dd, dd.MM.yyyy, dd-MM-yyyy HH:mm:ss and dd.MM.yyyy HH:mm:ss are also accepted. Defaults to today.
Overrides the automatic granularity of the date range. Case-insensitive. When omitted, granularity is derived from the range length. Legacy values DAY, WEEK, MONTH and YEAR are also accepted. HOUR is deprecated (was only for ACTIONS-PHONE) and now maps to DAILY.
Filter strategy to use for scoping locations
Comma-separated location IDs (used when filterCategory=location)
Comma-separated business IDs (used when filterCategory=business)
Label names (used when filterCategory=labels)
Location group IDs (used when filterCategory=location-groups)
Comma-separated location IDs to exclude from results
Comma-separated business IDs to exclude from results
Label names to exclude from results
Location group IDs to exclude from results
Response
Duplicate counts per directory type