# POST /api/public/subscriptions: the spec says 201, and Location points at the subscription

- Date: 2026-10-30
- Type: Non-breaking change
- Surface: /api/public
- What you need to do: Nothing.
- Address: https://developers.rivr.io/changelog/2026-10-30-api-public-subscription-201

`POST /api/public/subscriptions` has always answered `201` with `subscriptionId` and `subscriptionNumber`, but the spec said `200` with the whole `Subscription`, and the `Location` header pointed at an address that does not exist. The spec now says `201` with the new schema `CreateSubscriptionResponse`, and `Location` is `/api/public/subscriptions/{subscriptionId}`, the address that reads the subscription. The answer is the same when the call creates the subscription and when it adds payments to an existing one. The status code and the body do not change. If you generate a client from the spec, regenerate it so the create call returns `CreateSubscriptionResponse`. The sandbox has the change since platform release 2026.10.30.2747; production gets it with the platform's next release, and this entry says when.