Synchronize a provider subscription source

POST/v1/billing/admin/{userId}/provider-subscription

Records a test- or production-mode Lemon Squeezy subscription independently and recomputes the effective entitlement for the current deployment stage.

How to call this endpoint

Every ACP API request uses bearer authentication. The examples here show the actual request path, auth header, and body shape that the platform expects.

Path, query, and header parameters

These parameters control which ACP object the endpoint acts on and how the request is processed.

Path parameters
NameLocationTypeRequiredDescription
userIdpathstringYesUser ID
Query parameters
None.

Body schema

Content type: application/json · Required

FieldTypeRequiredDescription
providerlemonsqueezyNo
providerModetest | productionYes
providerSubscriptionIdstringYes
providerCustomerIdstringNo
tierbuilder | team | business | enterprise | pro | scale | maxYes
statustrialing | active | past_due | canceled | cancelled | expiredYesCurrent lifecycle status.
organizationIdstringNo
periodStartDatestringNo
periodEndDatestringNo
billingIntervalmonthly | annualNo
builderSeatsintegerNo
resetPeriodUsagebooleanNo
productionEligiblebooleanNoExplicitly approves a test-mode source as a production fallback. Reserved for grandfathered or internal subscriptions.
eventNamestringNo
variantIdstringNo

What the API returns

Each response code below includes the documented payload shape for the ACP API.

200Provider source stored and stage entitlement projectedapplication/json
FieldTypeRequiredDescription
successbooleanNoWhether the request succeeded.
userIdstringNoUser ID.
deploymentStagedev | cons | prodNo
recognizedSourceCountintegerNo
tierstringNo
subscriptionStatusstringNo
organizationIdstringNo
planIdstringNo
sourceobjectNo
effectiveSourceobjectNo
organizationSubscriptionobjectNo
400Response
None.
Synchronize a provider subscription source
Loading...
Response 200
Loading...
See the ACP quickstart and SDK flow