Family workflow

Family static IP

Family sharing is broker-policy-specific. Some brokers allow a documented family route, some require manual review, and some still expect separate IP ownership per customer.

Family sharing requires the broker’s documented approval. Servloci can prepare the setup or request, but cannot approve it on the broker’s behalf.

Broker policy snapshot

FYERSSupport + KYC review

Allowed only for spouse, dependent parents, and dependent children, with signed declaration and proof.

  • Whitelist the IP in one family member account first.
  • Get signatures from all family members listed in the declaration.
  • Email the declaration and proof documents for KYC validation.
Open official source
ZerodhaSupported in console

Immediate family can share one static IP through a single developer account with separate apps.

  • Create separate apps under one Kite Connect developer account.
  • Add all relevant client IDs to each app.
  • Confirm the immediate-family declaration while updating the whitelist.
Open official source

How to do it

  1. Confirm the broker route first. Start from the broker page in this docs section and check whether family mode is supported, support-reviewed, or blocked.
  2. Allocate the IP owner. Decide which account is the primary owner of the Servloci allocation before you touch broker settings or email support.
  3. Run the proxy egress check. Verify that your app exits from the assigned static IP before any whitelist request is submitted.
  4. Prepare relationship proof. Keep client IDs, relationship details, signed declaration forms, and KYC documents ready where the broker requires them.
  5. Submit only through the official path. Use the broker dashboard if self-service is supported, otherwise use the published support email or review flow.
  6. Record the approval. Save the request date, ticket ID, approved IP, approved client IDs, and who approved it before you mark the setup trading-ready.
  7. Verify with a non-order API call first. Only move to live order APIs after the broker accepts the IP and your own verification succeeds from the family-linked account.

Broker-specific notes

FYERS

FYERS allows a common static IP only for spouse, dependent parents, and dependent children. Their published flow is: whitelist the IP in one family member’s dashboard, download and sign the declaration form, attach relationship proof, and email the request for KYC validation. Treat the setup as blocked until FYERS confirms approval.

Zerodha

Zerodha’s published Kite Connect article allows immediate family sharing through one developer account. The documented pattern is to create separate apps under that account, add all relevant client IDs to each app, and confirm the family-use declaration during IP whitelist update.

Dhan

Dhan supports IPv6 whitelisting through the DhanHQ v2 static-IP request path. Keep the request record and approved address in Servloci before running live-order APIs.

Groww

Groww Trade API accepts IPv6 whitelisting on the current published route. Verify the exact API product route before treating the setup as trading-ready.

What to record

  • Relationship or eligible-family route.
  • Primary or secondary IP role when relevant.
  • Request date, ticket number and approved address.
  • API verification success before calling it trading-ready.