#stripeuser_96421
1 messages · Page 1 of 1 (latest)
The default limit is 10 records per request, but you can increase that to up to 100: https://stripe.com/docs/api/pagination#pagination-limit
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Yes, using I am using 100 as limit. But there will be still lot of calls
Our libraries have auto-pagination features which handle this: https://stripe.com/docs/api/pagination/auto
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
But if you're not using them then I'm afraid 100 is a hard limit
auto pagination is a good option but apigee has a limitation of 25 MB data
Yeah I'm not familiar with Apigee but if that's a limitation on libraries/modules then I guess you'll need to manually handle it
I understand, but do you know if we can use streaming on stripe data?
I've no idea what that means
okay, no issues. will research more on it. But one more question. suppose I call the api and somehow there is some record which fails to reach the target(via apigee), then what are the parameter to call that specific transaction in the balance_transaction api?
like can we get a specifc transaction from the api call?
You mean retrieve a single txn_xxx object?
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.