stripe-node
stripe-node copied to clipboard
stripe.issuing.fundingInstructions API missing
Describe the bug
As per API docs issuing should allow to manage FundingInstructions
https://stripe.com/docs/api/issuing/funding_instructions/object?lang=node
However neither v9.16.0 nor v10.0.0 have that API interface exposed
VSCode error: Property 'fundingInstructions' does not exist on type '{ authorizations: AuthorizationsResource; cards: CardsResource; cardholders: CardholdersResource; disputes: DisputesResource; transactions: TransactionsResource; }'.ts(2339)
To Reproduce
-
npm install stripe --save
-
import Stripe from "stripe"
-
const stripe = new Stripe(process.env.STRIPE_SECRET_KEY, { apiVersion: "2020-08-27" })
- Try to access
stripe.issuing.fundingInstructions
Expected behavior
The API functions are available as described in the docs
Code snippets
import Stripe from "stripe"
const stripe = new Stripe(process.env.STRIPE_SECRET_KEY, { apiVersion: "2020-08-27" })
class StripeService {
async test(){
// ERROR: Property 'fundingInstructions' does not exist on type '{ authorizations: AuthorizationsResource; cards: CardsResource; cardholders: CardholdersResource; disputes: DisputesResource; transactions: TransactionsResource; }'.ts(2339)
const fundingInstructions = await stripe.issuing.fundingInstructions.list({
limit: 3,
});
}
}
export const stripeService = new StripeService()
OS
windows, macos
Node version
12.22.6
Library version
10.0.0
API version
2020-08-27
Additional context
No response
index.d.ts confirms that the API methods are not exposed
Hi @steve1337 , thank you for the report!
You're right that these endpoints are indeed not in the SDKs today. I'll follow up with the team and get back to you.
Sorry for the trouble!
Following up here - these snippets were accidentally included in the docs, but these APIs are not yet supported in the SDKs.
I've removed the non-cURL snippets from https://stripe.com/docs/api/issuing/funding_instructions/object to clear up any confusion.
Sorry about the trouble here.
I'm actually going to re-open this issue, since we do eventually want to ship this API to the SDKs.