This article showcases a use case where legacy SOAP APIs power secure, structured transactions, while modern GraphQL APIs enable flexible, real-time data access. eZintegrations simplifies the integration of both API types, allowing businesses to modernize operations by connecting these APIs to their existing systems. The article highlights eZintegrations ability to handle diverse API protocols effectively, with a focus on applications in the banking industry.
SOAP API Integration (Banking)
API: Account Balance Retrieval (SOAP)
Endpoint: http://bankapi.com/soap/accountService
Operation: GetAccountBalance
Description: Retrieves account details for customer management in a banking CRM.
Response (XML):
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<Account>
<AccountNumber>987654321</AccountNumber>
<AccountHolder>Jane Smith</AccountHolder>
<Balance>15000.75</Balance>
<LastTransaction>2025-10-20</LastTransaction>
</Account>
</GetAccountBalanceResponse>
</soap:Envelope>
AI Operation Prompt for SOAP:
Extract account number, account holder name, balance, and last transaction date from the {%bizdata_dataset_response%}. Add a field 'account_status' with value 'Active' if the balance exceeds 1000, otherwise 'Inactive'. Format the data as a JSON object for the banking CRM and give the value in the 'Data'.
Output (JSON):
"account_holder": "Jane Smith",
"balance": 15000.75,
"last_transaction_date": "2025-10-20",
"account_status": "Active"
}
APPEND Operation:
{
"status": "success"
}
FILTER Operation: Send only active accounts to the CRM:
data["account_status"] == "Active"
Target: The data is sent to a legacy banking CRM (e.g., Microsoft Dynamics 365) via a REST API to update customer account profiles.
Use Case: A bank uses the SOAP API to sync account details to Microsoft Dynamics 365, enabling relationship managers to track active accounts. Biweekly syncs (0 6 * * WED) in the IST timezone (Asia/Kolkata) ensure timely updates.
GraphQL API Integration (Banking)
API: Transaction Analytics (GraphQL)
Endpoint: http://bankapi.com/graphql
Description: Fetches transaction details for real-time fraud monitoring in a modern CRM.
Query:
query {
transactionAnalytics(accountNumber: "987654321") {
transactionId
amount
date
merchant
}
}
Response (JSON):
"transactionAnalytics": {
"transactionId": "TXN456",
"amount": 250.50,
"date": "2025-10-20",
}
}
}
AI Operation Prompt for GraphQL:
Extract transaction ID, amount, date, and merchant from the {%bizdata_dataset_response%}. Add a field 'risk_level' with value 'Low' if the transaction amount is below 1000, otherwise 'Medium'. Format the data as a JSON object for the fraud monitoring CRM and put the value in the key 'Data'.
Output (JSON):
{
"transaction_id": "TXN456",
"transaction_amount": 250.50,
"transaction_date": "2025-10-20",
"merchant": "Retail Store",
"risk_level": "Low"
}
APPEND Operation:
{
"status": "success"
FILTER Operation: Send only low-risk transactions to the CRM:
data["risk_level"] == "Low"
Target: The data is sent to a modern fraud monitoring CRM (e.g., Salesforce Financial Services Cloud) via a REST API to enhance real-time fraud detection.
Use Case: The bank uses the GraphQL API to feed transaction data into Salesforce for fraud analysis. Biweekly syncs (0 6 * * WED) in the IST timezone (Asia/Kolkata) ensure consistent monitoring.
Why eZintegrations?
The platform’s AI operations use natural language prompts, eliminating coding complexity. Businesses can test APIs in a sandbox, schedule syncs, and share integrations across teams, fostering efficiency and innovation.
Broader Impact: By supporting both legacy SOAP and modern GraphQL APIs, eZintegrations helps businesses modernize without replacing existing systems. This dual compatibility drives operational agility, enhances customer service, and strengthens security.
