Yetzederixx-custom-fields | Stripe Developers | Page 1

open snow Apr 21, 2022, 9:26 PM

#

Can you link the docs you're looking at?

vagrant shell Apr 21, 2022, 9:29 PM

#

sure one sec

#

https://stripe.com/docs/api/invoices/create

Stripe API reference – Create an invoice – curl

Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.

#

If I had to guess it's the last one I posted, but I haven't gotten that far in my own code yet

open snow Apr 21, 2022, 9:32 PM

#

So it should be an array of hashes. Not sure what that looks like syntactically in Python (it has been a while).

vagrant shell Apr 21, 2022, 9:32 PM

#

kk, basically an array of json then

open snow Apr 21, 2022, 9:34 PM

#

Syntactially it would probably look like
custom_field : {
key1: 'value',
key2: 'value2'
}

But I could be wrong. Let me know when you try a couple of things and I can help debug if needed 🙂

vagrant shell Apr 21, 2022, 9:37 PM

#

Welp it's not this heh

cfs=[
    {'Gophr ID', '1234'},
    {'Store ID', 'ABCD'},
    {'Pickup Business Name', 'pickup_business_name'},
    {'Drop Off Business Name', 'drop_off_business_name'}
]

#

So this doc really needs work though, well all your examples really.

The syntax is this
custom_fields=[{"name": "key1", "value": "value1"}]

open snow Apr 21, 2022, 9:45 PM

#

The syntax is this
custom_fields=[{"name": "key1", "value": "value1"}]
That makes sense. So you were able to get it to work?

vagrant shell Apr 21, 2022, 9:47 PM

#

yeah

#

while that's technically inferrable from the docs it does leave some room for confusion

open snow Apr 21, 2022, 9:53 PM

#

You're not wrong. I feel like it would be better if it worked like metadata where you just supply a single hash of key-value pairs, rather than the multiple hashes with a name value and a value value

#Yetzederixx-custom-fields