Skip to main content
The subscription settings endpoints manage the global configuration singleton used by the Reorder plugin at runtime. You can read the effective settings — which fall back to hardcoded defaults if no record has been persisted yet — and write a new or updated singleton through the dedicated workflow. All routes require an authenticated Medusa Admin user. The POST route uses optimistic locking via expected_version.
All routes require an authenticated Medusa Admin user. Unauthenticated requests return 401.

Field reference


GET /admin/subscription-settings

Returns the effective settings payload. When no record has been saved yet the response uses hardcoded fallback defaults and is_persisted is false. This route never returns 404.

Response

object
required
Fallback response example
Persisted response example

POST /admin/subscription-settings

Persists a new or updated settings singleton through the dedicated workflow. The first successful POST creates the record. Omitted fields retain their current effective value.

Body parameters

number
Default trial length in days. Must be >= 0.
number[]
Retry intervals in minutes. Must be strictly increasing positive integers. Length must equal max_dunning_attempts.
number
Maximum retry attempts. Must be a positive integer equal to the number of intervals.
string
Global renewal policy. One of process_immediately or require_review_for_pending_changes.
string
Global cancellation policy. One of recommend_retention_first or allow_direct_cancellation.
number
Current version for optimistic locking. Use 0 on the first write.
string
Optional reason for the update, recorded in the audit log.
Request example

Response

Returns the updated subscription_settings object. The metadata.audit_log and metadata.last_update fields record the change summary.
Response example

Errors