How to Journal Delta Exchange India Futures Trades

What the integration supports

The repository includes Delta credentials, fill sync, product metadata, wallet or funding enrichment, CSV import, trade matching and a process-local sync lock. TradeLore imports data for journaling and analytics; it does not place trades or withdraw funds.

Check Delta's current documentation for account terminology, permissions and connection workflow before setup.

What a complete review should distinguish

• Orders versus fills: a journal should review executed fills, not only submitted orders.
• Long and short positions, including partial exits.
• Fees and funding as separate cost or cash-flow concepts.
• Settlement currency, leverage and perpetual-futures terminology.
• The difference between an API sync and a CSV import.

What to verify in your account

Confirm the supported contract set, source fields, historical range, fee and funding treatment, settlement currency and duplicate behaviour against the current account workflow. Product, API and exchange terminology can change, so verify current details before following operational instructions.

What you need before connecting Delta

The current Delta settings flow expects an API key and API secret. Its help panel instructs you to create a key with read or data permissions, avoid trading and withdrawal permissions, save both values in TradeLore, and then use either API sync or CSV import. If you use IP restrictions at Delta, the current TradeLore server IP requirements must be verified before relying on an allowlist.

Use a read or data-only key and avoid trading and withdrawal permissions. Check Delta's current documentation for account terminology, IP allowlisting and permission rules before setup.

Step by step: API sync

1. Create a read-only/data API key in Delta. 2. Save the key and secret in TradeLore. 3. Click Sync Delta. TradeLore signs each request with an HMAC-SHA256 signature over the uppercase method, current timestamp, request path, query string and body. 4. It requests fills in pages of 100, follows the returned cursor, loads or fetches product metadata, converts valid fills into trade orders, fetches wallet transactions for funding enrichment, and sends the result through the shared matching pipeline.

The sync stores a cursor so later runs can continue from the last page. It also has a process-local lock to reject a second sync for the same account while one is active. That lock is not a substitute for a distributed lock across multiple server instances; the implementation comment identifies that limit.

Endpoint names, signature requirements and pagination behaviour can change. Confirm Delta's current API documentation before reproducing this workflow outside TradeLore.

API fields and CSV fallback

A valid API fill needs a fill ID, symbol, positive size, positive price and BUY or SELL side. Product metadata supplies contract type, notional type, contract value, quote asset, settlement asset, expiry and settlement information. The normalised order retains order ID, fill ID, commission, commission asset and liquidity role where present.

TradeLore's Delta settings also exposes Import Delta CSV. The upload is routed through the shared import endpoint, so validate the imported count and matched trade count against the source export. Confirm the current Delta CSV format and export instructions before preparing a file.

Review positions, fees, funding and settlement

Review fills rather than assuming an order equals a position. Multiple fills can open, reduce, reverse or partially close a long or short position. Use product metadata to distinguish perpetual, futures and option contract types where the source supplies them. Do not describe a product as a perpetual or an option solely from a symbol without checking metadata.

Commission is stored as a fee amount with a fee asset. Wallet transactions are filtered for funding transactions, normalised by transaction ID, date, product and asset, and assigned once to the latest same-day/product trade bucket to avoid double counting. That bucket assignment is a deliberate simplification: inspect the raw funding transaction when exact attribution matters.

Settlement currency, leverage, contract value and funding treatment can materially change interpretation. Verify current Delta terminology and contract specifications before publishing or using a report for a financial decision.

Delta troubleshooting