✳flâneur — a map of the web's best reading

Stripe API reference – Authentication – curl

stripe.com · 1,045 words · saved by 1 readers

The Stripe API is organized around REST. Our API has predictable resource-oriented URLs, accepts form-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs. You can use the Stripe API in test mode, which doesn't affect your live data or interact with the banking networks. The API key you use to authenticate the request determines whether the request is live mode or test mode. The Stripe API doesn't support bulk updates. You can work on only one object per request. To optimize performance and reliability, Stripe has established rate limits and allocations for API endpoints. The Stripe API differs for every account as we release new versions and tailor functionality. Log in to see docs customized to your version of the API, with your test key and data. Was this section helpful?YesNo Check out our development quickstart guide. Use Stripe’s no-code options or apps from our partners to get started with Stripe and to do more

Errors Ask about this section Copy for LLM View as Markdown Stripe uses conventional HTTP response codes to indicate the success or failure of an API request. In general: Codes in the 2xx range indicate success. Codes in the 4xx range indicate an error that failed given the information provided (e.g., a required parameter was omitted, a charge failed, etc.). Codes in the 5xx range indicate an error with Stripe’s servers (these are rare). Some 4xx errors that could be handled programmatically (e.g., a card is declined ) include an error code that briefly explains the error reported. Was this se

Explore this link on the map →

saved by

related reading