Holds
A hold stops something from going live without taking down what is already live. There are three kinds.
A push held for your confirmation
Section titled “A push held for your confirmation”A push from your own system that would, on a catalogue of 20 or more listings, change more than a fifth of its prices, change any price by more than half, or remove more than a fifth of its listings, is stored but not published. The push answers held: true, and the portal shows it to your owners and admins.
An owner or admin — someone allowed to manage mandates — reviews it and confirms it, and its records go live. A version overtaken while it waited (because a newer one went live) is not published over the newer one: it answers rejected with conflict. This is the check a stolen integration key cannot pass.
A record held for review
Section titled “A record held for review”A record whose geocoded coordinate falls outside its country, or more than 500 m from the place captured with its address, is stored and not served, and opened for review by MasterDB. See Geocoding. A record whose URL is flagged as unsafe (malware or phishing) is taken out of serving and reviewed in the same way.
A business on hold
Section titled “A business on hold”MasterDB may put a business on hold while a case is open — a verification question, a report, a payment dispute. On hold:
- your published records stay live, and AI companies see no difference;
- new publishing pauses: a save or a push is refused with
party_held(403); - you can still edit drafts, run imports, and withdraw or delete records;
- ad delivery pauses.
A hold is a record with a reason and a date it was lifted, never a silent flag. It is different from a suspension that withdraws published data, a MasterDB decision that takes every record out of serving in every region at once — and is lifted the same way.