#Home designer suite coupon 2018 upgrade

The API calls you make without a Stripe-Version header: the parameters you can send and the structure of objects returned.

#Home designer suite coupon 2018 upgrade

If you’re running an older version of the API, upgrade to the latest version to take advantage of new functionality or to streamline responses so the API is faster for you. Make sure that your webhook listener gracefully handles unfamiliar event types.For example, if you’re using MySQL, store the IDs in a VARCHAR(255) COLLATE utf8_bin column (the COLLATE configuration provides case-sensitivity during lookups). Make sure that your integration can handle Stripe-generated object IDs, which can contain up to 255 characters.This includes adding or removing fixed prefixes (such as ch_ on charge IDs).Changing the length or format of opaque strings, such as object IDs, error messages, and other human-readable strings.Changing the order of properties in existing API responses.Adding new properties to existing API responses.Adding new optional request parameters to existing API methods.Stripe considers the following changes to be backwards-compatible: If you make requests on behalf of other users using Connect, we’ll use your application’s API version, making it easy for you to write code that works for all your users no matter what API versions they’re individually running. To avoid breaking your code, we don’t change your version until you’re ready to upgrade. When a breaking change is introduced to the Stripe API, a new dated version is released. Your version gets set the first time you make an API request.

Your API version controls the API and webhook behavior you see (for example, what properties you see in responses, what parameters you’re permitted to send in requests, and so on).