Request encoding multimethods for Stripe API v1 and v2.
Dispatches encoding based on API version:
Request encoding multimethods for Stripe API v1 and v2. Dispatches encoding based on API version: - v1: application/x-www-form-urlencoded with nested bracket notation - v2: application/json with native JSON encoding
Returns the appropriate Content-Type header for the API version.
Returns the appropriate Content-Type header for the API version.
Encodes request parameters based on API version.
v1: Flattens params with bracket notation for form-urlencoded v2: Converts to JSON string with snake_case keys
Encodes request parameters based on API version. v1: Flattens params with bracket notation for form-urlencoded v2: Converts to JSON string with snake_case keys
Formats field expansion parameters based on API version.
v1: Uses 'expand' parameter with indexed bracket notation v2: Uses 'include' parameter with indexed bracket notation
Formats field expansion parameters based on API version. v1: Uses 'expand' parameter with indexed bracket notation v2: Uses 'include' parameter with indexed bracket notation
(get-expansion-fields version opts)Gets the appropriate expansion fields based on API version.
For user convenience, accepts both :expand and :include for any version and maps to the correct parameter:
This allows users to use either option without needing to remember which version uses which parameter name.
Gets the appropriate expansion fields based on API version. For user convenience, accepts both :expand and :include for any version and maps to the correct parameter: - v1: Uses 'expand' parameter (prefers :expand, falls back to :include) - v2: Uses 'include' parameter (prefers :include, falls back to :expand) This allows users to use either option without needing to remember which version uses which parameter name.
cljdoc builds & hosts documentation for Clojure/Script libraries
| Ctrl+k | Jump to recent docs |
| ← | Move to previous article |
| → | Move to next article |
| Ctrl+/ | Jump to the search field |