#Luca

1 messages · Page 1 of 1 (latest)

signal hareBOT
#

Hello Luca, we'll be with you shortly! Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
Luca, 3 days ago, 31 messages

marsh bolt
woven dock
#

request-id: req_bA6R88EZOpEYGR'

marsh bolt
#

According to the requestId, you are passing feature: ""

#

You are not passing the correct object

woven dock
#

yes, i know. i just needed the error for discrod. give me a second i can pass the "correct" one.

marsh bolt
#

Between, why you want to use feature ?

now i want to set the email as well, so the user can not modify it.
You simply need to set the Customer Id

woven dock
#

I set customerId, he can modify it.
here is a better features: request-id: req_vDQyW81chOMwKL'

marsh bolt
#

I set customerId, he can modify it.
How he can modify it ?

marsh bolt
#

I invite you to double check your request body and the error message, it's quiet explicit I think

woven dock
marsh bolt
#

Ah Iss, because youa re not creating the customer portal link via the dashboard

#

then yes you need to use feature

#

But make sure to send the correct object

woven dock
# marsh bolt Ah Iss, because youa re not creating the customer portal link via the dashboard

yes i provided my code at the top. even though i use features:

Map<String, Object> features = new HashMap<>();

   
    Map<String, Object> customerUpdate = new HashMap<>();
    customerUpdate.put("allowed_updates", Collections.singletonList("address"));

    features.put("customer_update", customerUpdate);

    params.put("features", features);

request-id: req_QYHIwh5lX1YE4C'

I read the docs but its not working for me. i do something wrong. i dont know for a long time now not what.

marsh bolt
#

You are passing the feature on the wrong API call

#

You are setting the feature on this endpoint /v1/billing_portal/sessions