in reply to Re: HTTP::Tiny losing headers for Stripe
in thread HTTP::Tiny losing headers for Stripe

I imagine it needs to be encoded as JSON

No - Stripe takes key/value pairs.

To quote the documentation:
accepts form-encoded request bodies, returns JSON-encoded responses

For a form-encoded request, application/x-www-form-urlencoded is required hence the use of post_form().

The syntax of the call to Stripe works elsewhere in my code. Indeed, the call I am making works provided I don't make another call before it - it is this problem I want help resolving.

I'm unsure if it is an issue with HTTP::Tiny not being able to reuse the header information or an issue with Stripe or something else...

Out of interest, I have tried using the request() method as you suggested.
With the first call still in the code I continue to get a 401 error and the message that I have not supplied an API Key.
If I comment out the first call to Stripe, it accepts the API Key but returns the entire subscription object because it is not accepting the JSON encoded payload.

Replies are listed 'Best First'.
Re^3: HTTP::Tiny losing headers for Stripe
by tangent (Parson) on Jun 26, 2022 at 00:23 UTC
    No - Stripe takes key/value pairs.
    Ah, I see. Still might be an issue sending a perl hash which is not the same as key-value pairs coming from a form. You could try: 
    'content' => $http->www_form_urlencode( $subscription ),

# or just to try getting it to work

'content' => q|"items[0][id]"="x","items[0][price]"="some price"|,

    [download]

    Update: I think you can strike the above as looking at the source for the module post_form does call www_form_urlencode on the content. I'm stumped for the moment.

[reply]
[d/l]
[select]

      The reason I'm stumped is that it works providing I don't make a call to the Stripe API followed by another. One call works - two calls don't.

      I've eliminated rate limiting by trying a 5 second delay between calls.

[reply]

In Section Seekers of Perl Wisdom