Register API Features
In this Final Step, you define the actual API operations (features) that the integration will expose.
To import Features:
-
Click
+ Add New Feature
to open the configuration page for a single API operation. -
Provide basic metadata:
- Feature Code: A unique internal identifier (e.g.,
getOrders
) - Feature Name: Display name for UI references
- Feature Description: Notes about the operation's function
- Feature Code: A unique internal identifier (e.g.,
- Configure the Inputs JSON Schema Settings required for this API call. These will be passed as variables (e.g.
${orderId}
,${date}
) in the request path, headers, or body.
- Import CURL and configure the request method and path, along with optional headers, parameters, and body structure.
-
Set assert expressions to validate the API response.
- Example:
status == 200 && $.data.length > 0
- Example:
-
Choose how Item DI should handle the API response:
- Path: Extract specific fields (e.g.
$.orders[0].id
) - Fixed: Map static values to variables (e.g.
token_type: Bearer
) - Full Response: Store the entire response payload (for debugging or full-sync operations)
- Path: Extract specific fields (e.g.
-
Click
Test
to preview the result.
- Click Save Feature to complete.
- Repeat this process for each API operation you want to register under this integration.
All features you configure will be accessible from Merchant Connectors, Workflow Connector Nodes and MCP-compatible server interfaces. For more information, see Integration Use Cases.