A user can specify whatever API version they need (e.g. 2022-11-15
). There is a field in the component’s metadata where an API version can be set. If the field is blank, version 2020-08-27
is used by default.
Name | Mandatory | Description | Values |
---|---|---|---|
API_RETRIES_COUNT |
false | Set how many time system try to make request to API on errors (3 by default) | any integer above 0 |
API_RETRY_DELAY |
false | Delay between retry attempts in milliseconds (10000 by default) | any integer above 0 |
API_REQUEST_TIMEOUT |
false | HTTP requests timeout in milliseconds (15000 by default) | any integer above 0 |
Component credentials configuration fields:
To verify credentials request GET https://api.stripe.com/v1/charges
with your Secret Key is used. So if you are restricted to make this API call - simply skip credentials verification.
This component has no trigger functions. This means it will not be accessible to select as a first component during the integration flow design.
Executes custom request.
false
.https://api.stripe.com
.GET
, POST
, PUT
, PATCH
, DELETE
.As of the component version 1.1.0 an input body can be set as a plain JSON object. While version 1.0.0 expected an input body to be built as a application/x-www-form-urlencoded
data only. Version 1.1.0 allows both options.
As an example we’ll be using the Payment Links endpoint.
Body:
{
"method": "POST",
"url": "v1/payment_links",
"data": {
"line_items[][quantity]": 3,
"line_items[][price]": "price_1MJXtjGB4S5N5BY8ymGY6TWC"
}
}
In version 1.1.0 both options will work. Either as we showed for 1.0.0 or a plain JSON:
Body:
{
"method": "POST",
"url": "v1/payment_links",
"data": {
"line_items": [
{
"quantity": 3,
"price": "price_1MJXtjGB4S5N5BY8ymGY6TWC"
},
{
"quantity": 10,
"price": "price_1MJh6eGB4S5N5BY8kJ1Q6exh"
}
]
}
}
Click here to learn more about the elastic.io iPaaS