What it does: Replaces your scoring profile. The body is validated against the ranges GET reports before anything is stored; an out-of-range weight, an unknown knob, a fail that cannot be softened or an autoThreshold below 0.90 is refused with 400 and the message names the field. Unknown fields are 400 too.

Takes effect on new jobs only. Mappings already stored keep the score they were stored with. To re-score a hotel, purge its matches (DELETE /rooms/match/async/matches/{hotelId}) and submit it again. Preview a candidate first with POST /rooms/match/async/scoring-profile/preview.

Each change gets a new version that is never reused; score.profile on results (for example c368927/v3) names the exact policy that produced the number.

Available to accounts with their own isolated room-mapping cache; others receive 409. Details: Implementation Workflow (doc page: implementation-workflow).