v1Recursos/Listados publicados/postActualizar campos de directorios
Actualizar campos de directorios
Crea, renombra o archiva un campo personalizado de la tabla de directorios de una ubicación, o establece valores en sus filas. Envíe locationId, un mutationId y un command. Los cambios permanecen en Synup y nunca se envían a un directorio.
post
listings:write/api/v1/listings/directory-fieldsCuerpo de la solicitud
locationIdstringobligatorio
ID de la ubicación cuyo conjunto de campos está modificando. Para prompts AEO, el sitio web.
mutationIdstringobligatorio
Un UUID que usted elige para este cambio. Reenviarlo con el mismo command devuelve el primer resultado sin volver a aplicar el cambio; reutilizarlo con un command distinto devuelve 409.
commandobjectobligatorio
Un cambio. field_create añade un campo con label, type y options. field_update renombra un campo, cambia sus opciones o lo archiva o restaura, y requiere la versión actual del campo como expectedVersion. values_update establece de 1 a 1000 valores, cada uno con recordId, fieldId, value y expectedVersion, y aplica todos o ninguno. Una opción que los registros todavía tienen no se puede eliminar; archívela en su lugar. Un conjunto de campos admite como máximo 40 campos, incluidos los archivados.
Respuesta
dataobjectopcional
resultobjectopcional
Lo que hizo el cambio: el id del campo para field_create y field_update, o el número de valores escritos para values_update.
Errores
400A la solicitud le falta un parámetro obligatorio o es inválida de otra forma.
401La clave de API falta, es inválida, expiró o fue revocada.
403A la clave le falta el permiso requerido, o no está autorizada para este cliente/ubicación.
404El recurso no se encontró, o no pertenece a su agencia.
409La solicitud entra en conflicto con el estado actual del recurso — por ejemplo, cambiar el correo electrónico o el teléfono de un destinatario al que ya se le ha enviado un mensaje, o una invitación de equipo que ya fue aceptada (o que aún no ha sido aceptada).
413El cuerpo de la solicitud supera 1 MB.
429Demasiadas solicitudes. Reintente tras el número de segundos indicado en el encabezado Retry-After.
503El servicio no está disponible temporalmente. Siga las indicaciones de reintento para esta operación.
post/api/v1/listings/directory-fields
Su clave de API
Cuerpo de la solicitud*
{}Guías que usan este recurso
- What Is a Business Listings API?A business listings API manages a business's name, address, hours and more across many publishers at once, with sync status and duplicate detection built in.
- Business Listings API: Complete Developer GuideHow a business listings API works and how to create, update, sync and monitor locations across Google, Apple, Bing and directories with the Synup API.
- 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 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 Manage Business Listings ProgrammaticallyKeep business listings accurate from your own system with the Synup API. Covers change detection, idempotent updates, hours, photos and sync reporting.
- What Is an AEO API?An AEO API measures how AI answer engines like ChatGPT, Gemini and Perplexity describe and recommend a business, and tracks that visibility over time.
- How to Update Business Information Across Google, Apple, Bing and DirectoriesPush one business-information change to Google, Apple, Bing and the directory network through a single API call, and verify it reached each publisher.
- How Listing Syndication WorksListing syndication takes one business record, translates it into each publisher's format, and pushes it out asynchronously, which is why sync status matters.
- 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 Manage Thousands of Business Locations via APIDesign a sync job for thousands of locations on the Synup API with cursor pagination, tags, rate-limit handling, an id map and rollup health checks.
- How to Find and Remove Duplicate Business ListingsDetect duplicate business listings across publishers, review them by confidence, and flag them for removal or dismiss them with the Synup API.
- How Duplicate Listing Suppression WorksDuplicate suppression detects listings that look like the same business, scores them by confidence, and requests removal from the publisher that controls them.
- 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 Connect and Manage Google Business Profiles via APIConnect a Google Business Profile to a location, match the account's listings, keep the profile in sync and handle reconnects with the Synup API.
- Building Publisher Integrations Directly vs Using SynupWhat it really costs to integrate Google, Apple, Bing and directories yourself, versus one API, and how to decide between them or combine both.
- 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 Track Local Rankings with an APITrack local search rankings on a geo grid through an API, add keywords, read the grid and trend, and compare against competitors and citation coverage.
- How to Monitor Local SEO Across Multiple LocationsMonitor local SEO across hundreds of locations through rollup endpoints, with rank and AI visibility per location and the weakest surfaced first.