Updates only the top-level fields supplied for an existing entity; omitted top-level fields remain unchanged.

• PUT does not create a missing row. Acceptance is asynchronous, so a PUT for an unknown key still receives 202 — ensure the entity was created first.
• Nested objects replace rather than merge: a supplied object field (for example categoryNameTranslated or extra) replaces the stored object entirely. Retain your authoritative object before sending an update meant to preserve existing nested keys.
• Safe odds updates: automatic decimal-price derivation is not guaranteed on PUT. When fractional odds change, send numPrice, denPrice, and decPrice together with consistent values; to mark a Selection unpriced, set all three to null. Never update only one of the fractional pair.
• Record expiry — the optional X-Expires-After header applies a relative expiry (integer seconds, minimum 60) to every record in the request. PUT without the header preserves any existing expiry; to remove an expiry, send a complete authoritative POST for the row without the header.