v1Ressources/Reviews/deleteSupprimer un mot-clé d’avis
Supprimer un mot-clé d’avis
Nécessite un utilisateur actif avec accès Avis et au client. Fournir exactement locationId ou clientId. Les mots-clés sont nettoyés et mis en minuscules. POST ajoute un mot-clé de 3–128 caractères, jusqu’à 10 par périmètre, et demande un marquage sémantique en arrière-plan pouvant utiliser la capacité de génération. Vérifier queued et warning:tagging_not_queued ; le mot-clé reste enregistré si la mise en file échoue. DELETE supprime le mot-clé personnalisé et ses marquages. PATCH exige hide:true ou false et change la visibilité sans supprimer les avis. DELETE/PATCH acceptent les mots-clés existants de 1–128 caractères.
delete
reviews:write/api/v1/reviews/topic-trends/keywordsParamètres de requête
locationIdstringfacultatif
clientIdstringfacultatif
keywordstringobligatoire
Réponse
dataobjectfacultatif
Erreurs
400Il manque un paramètre requis à la requête, ou elle est invalide.
401Clé API manquante, invalide, expirée ou révoquée.
403La clé n'a pas la permission requise, ou n'est pas autorisée pour ce client/établissement.
404La ressource est introuvable, ou n'appartient pas à votre agence.
409La configuration historique du lieu entre en conflit avec un autre périmètre et ne peut pas être modifiée.
429Trop de requêtes. Réessayez après le nombre de secondes indiqué dans l'en-tête Retry-After.
503L’opération sur les avis n’a pas pu être effectuée.
delete/api/v1/reviews/topic-trends/keywords
Votre clé API
locationId
clientId
keyword *
{
"data": {
"custom": []
}
}Guides qui utilisent cette ressource
- Google Business Profile API vs a Listings Management APIHow Google's Business Profile API compares with a listings management API on scope, access, sync status, duplicates and reviews, and when to use each.
- How to Build a Reputation Management PlatformArchitecture and API calls for a multi-client reputation management platform on Synup: review ingestion, reply workflows, invites, widgets and reporting.
- How to Add Local Marketing Features to Your SaaSAdd listings management, reviews, Google posts, profile analytics, rank tracking and AI visibility to a SaaS product with the Synup API, tenant by tenant.
- How to Build an AI Agent for Local SEOBuild an AI agent that audits and fixes listings, tracks local rankings, checks AI visibility and drafts review replies with Synup's MCP server or REST tools.
- How to Build an AI Agent That Responds to ReviewsBuild an AI agent that drafts and posts review replies, with rating-based guardrails, human approval for negatives, and protection against injection.
- How to Build a Multi-Location Marketing DashboardBuild a multi-location marketing dashboard from the API's rollup endpoints, one call per panel, covering listings, reviews, rank, AI visibility and duplicates.
- How to Add Local Marketing Functionality to Vertical SaaSAdd local marketing to a vertical SaaS by mapping existing customers to clients and locations, and shipping only the features your niche needs.
- How to Fetch and Respond to Reviews via APIFetch reviews from Google, Facebook and custom review sites, filter them, post owner replies, add internal notes and read review analytics with the Synup API.
- How to Build Automated Review-Response WorkflowsBuild a review-response workflow that routes reviews by rating and sentiment, drafts replies, approves them, and pushes them back to the platform.
- Fetch Recent Reviews via APIPull a location's reviews from every connected platform with the Synup API, filter to what needs attention, and page through with a cursor.
- Local SEO APIs: What Developers Actually NeedA practical checklist of what a local SEO API must cover, from listings and sync status to reviews, rank tracking and AI visibility, mapped to endpoints.
- How to Retrieve Google Business Profile Analytics via APIPull Google Business Profile analytics through an API, portfolio-wide and per location, with views, calls, direction requests and a maps-versus-search split.
- Respond to a Review via APIPost an owner reply to a review with the Synup API, read the push status back, and know which failures are worth a retry.