POST /subscription_seat/user_subscriptions

Assigns subscriptions to users, site-wide and for every user named in one call. The success path was not exercised; see Edge cases.

Params

Sample requests

A hash that names no user, which assigns nothing:

r = c.post("/subscription_seat/user_subscriptions", json={})

{}

A user id that is not on the site:

r = c.post("/subscription_seat/user_subscriptions",
           json={"999999999": "definitely_not_a_subscription"})

[{"id": "031d95c876d98d715e3fa9e5f4ccfaa4", "status": 400, "code": 103,
  "title": "Invalid humanUserId 999999999", "source": {}, "detail": null, "meta": null}]

A list where a hash is wanted:

r = c.post("/subscription_seat/user_subscriptions",
           json=[{"999999999": "definitely_not_a_subscription"}])

[{"id": "ddbb3576c29de17d5ea49e8531629931", "status": 400, "code": 103,
  "title": "Invalid JSON body. Expected Hash but received Array.", "source": {}, "detail": null,
  "meta": null}]

A key that is not a number:

r = c.post("/subscription_seat/user_subscriptions",
           json={"definitely_not_a_user": "definitely_not_a_subscription"})

[{"id": "22d78aa52f7e00aadc363704c26aad32", "status": 400, "code": 103,
  "title": "Invalid humanUserId definitely_not_a_user", "source": {}, "detail": null, "meta": null}]

Response codes

Edge cases

• The success path is deliberately unexercised. Every call that could succeed changes the subscription of a real user of a real site, and there is no dry-run parameter and no undo. The rejections above are what pins the body shape; the 200 and 207 rows come from the site's own /spec.json.
• {} answers 200 with {}. A caller that treats a 200 as "the assignment happened" cannot tell an applied change from a body that named nobody.
• The whole request fails on the first unknown id: the 400 replaces the per-user hash, so nothing is reported about the ids that were valid. Validate ids against /entity/human_users first.
• A per-user failure is a 207, not a 400, and its message is a string inside the hash rather than in an errors array. A client checking r.ok passes straight over it.
• The error message is in title. detail is null, source is {}.