#tymm

1 messages · Page 1 of 1 (latest)

cedar juncoBOT
craggy breach
lucid ferry
craggy breach
#

hmmm, it says Received unknown parameter: items[0][proration_date]; code: parameter_unknown; request-id: req_cBlys0p4eNOGlr

iron bone
craggy breach
#

proration_date was placed inside SubscriptionCreateParams which is in the item list of the subscription im creating

iron bone
#

No I don't think proration_date is within Subscription Create API. It's a parameter on Subscription Item Create API.

#

I think you might need to break down to 2 APIs

craggy breach
#

is there a reason for the absence of proration_date properties in the subscription create api when the subscription update api has it?

iron bone
#

I am not super sure about that but it could just be a limitation on our API, sorry

craggy breach
#

alright, got it. lemme try calling them separately. thanks

iron bone
#

good luck!

craggy breach
#

hmmmm now im getting
Cannot specify proration date outside of current subscription period or current phase. The value should be between 1706755800 and 1709251200.; request-id: req_XLiI9vHoR3KxGX

#

need your suggestions on this 😅

#

prior to calling subscription create api i made a call to invoice upcoming to make a preview to show the prorated price to customer. so by the time my code creates the subscription it will use the same timestamp used when creating the preview to make the price consistent

iron bone
#

Hmm not sure about your flow, but the request specified proration_date = 1706752800 which < 1706755800 (start date)

craggy breach
#

i did not set the "start date" so i reckon this is the time i made the call to the api am i right?

#

im using test clock so the start date is the testclock frozen time my customer is in