v1Resources/AEO/postUpdate AEO prompt fields
Update AEO prompt fields
Creates, renames or archives a custom field on a website's tracked AEO prompts, or sets values on its active or paused prompts. Send locationId, a mutationId and one command. Fields are annotations only: they don't change what prompt checks measure or spend. While prompt management is turned off for the agency, fields stay readable but can't be changed.
post
aeo:write/api/v1/aeo/prompts/fieldsRequest body
locationIdstringrequired
ID of the location whose field set you're changing. For AEO prompts, the website.
mutationIdstringrequired
A UUID you choose for this change. Resending it with the same command returns the first result without applying the change again; reusing it with a different command returns 409.
commandobjectrequired
One change. field_create adds a field with label, type and options. field_update renames a field, changes its options, or archives or restores it, and needs the field's current version as expectedVersion. values_update sets 1 to 1000 values, each with recordId, fieldId, value and expectedVersion, and applies all or none. An option that records still hold can't be removed; archive it instead. A field set holds at most 40 fields, archived ones included.
Response
dataobjectoptional
resultobjectoptional
What the change did: the field's id for field_create and field_update, or the number of values written for values_update.
Errors
400The request is missing a required parameter or is otherwise malformed.
401Missing, invalid, expired, or revoked API key.
403The key lacks the required scope, or isn't authorized for this client/location.
404The resource wasn't found, or doesn't belong to your agency.
409The request conflicts with the current state of the resource — for example, changing the email or phone of a recipient who has already been messaged, or a team invite that was already accepted (or hasn't been accepted yet).
413The request body is larger than 1 MB.
429Too many requests. Retry after the number of seconds in the Retry-After header.
503The service is temporarily unavailable. Follow the retry guidance for this operation.
post/api/v1/aeo/prompts/fields
Your API key
Request body*
{}Guides that use this resource
- What Is a Local SEO API?A local SEO API measures how a business ranks in local search, with geo-grid rank tracking, profile analytics and AI visibility, not just backlinks.
- 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.
- 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 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 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.
- 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 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.
- How to Track AI and AEO Visibility ProgrammaticallyMeasure how ChatGPT, Gemini and Perplexity describe and recommend a business through an API, enqueue reports, poll for results and roll up a portfolio.