...
Expand | ||
---|---|---|
| ||
Avoid hardcoding configurations and parameters. Centralize configuration data in Custom Fields to make the interface adaptable and more secure. Information such as the base URL, authentication data (clientID, client secrets, username, password, tokens, etc.), and retry logic are good candidates for custom fields! This way, you can update configurations without modifying the core logic of your API calls. screenshot Here we are passing |
Expand | ||
---|---|---|
| ||
Using tables to store parameters allows you to dynamically build the data you need to send with the request. It also keeps your functions simple and support multiple optional parameters. In this example, we are passing the endpoint, body and live parameter in a single table for We are also passing the method, to |
Expand | ||
---|---|---|
| ||
In this example, we are working with JSON data. Notice in Depending on the API you’re working with and the type of request, there are a few functions that you may want to use to prepare the body or query string parameters:
|
Expand | ||
---|---|---|
| ||
Make your integration more robust by handling errors and retrying calls when necessary. This is particularly useful for handling intermittent network or server issues. For exampleNow, looking at , you can see pcall() , Retry Library | ||
Expand | ||
| ||
Prevent requests from hanging indefinitely by specifying a timeout parameter in and the Retry Library are used when making the See Handling HTTP Response for the fundamentals and recommendations on how to handle responses in IguanaX. |
Expand | ||
---|---|---|
| ||
Create Help Files (*.help) to document how your functions work and how to use them will make it easier for the rest of the team to understand and reuse your functions. |
If you are a more advanced user or are building a complex integration, refer to our Shell Adapter for a great template framework to structure your web client adapters to any API system.
...