---
title: "Update DLA Holdings"
method: PUT
path: "/backend/{gatewayname}/v1/holdings"
---

# Update DLA Holdings

`PUT /backend/{gatewayname}/v1/holdings`

When holdings data changes (e.g. you've fetched the user's latest MF or stock positions), call this API so eligibility and credit limit stay in sync.

## Path parameters

- `gatewayname` string, required

## Headers

- `x-gateway-secret` string, required
- `x-gateway-authtoken` string, required

## Request body

- object
  - `userId` string, required
  - `assetType` 'MUTUALFUND' | 'STOCKS', required — MUTUALFUND for LAMF, STOCKS for LAS. Allowed: MUTUALFUND, STOCKS.
  - `holdings` object[] — Required for MUTUALFUND. Non-empty array of MF holdings. When non-empty, holdingsLastFetchedAt is required.
  - `holdingsLastFetchedAt` string, date — Required when holdings is non-empty. ISO 8601 / RFC 3339.
  - `stockHoldings` object[] — Required for STOCKS. Non-empty array of stock holdings.
  - `name` string — Optional user attribute update.
  - `age` number — Optional user attribute update.
  - `isNri` boolean — Optional user attribute update.

## Response `200`

- object
  - `data` object
  - `message` string
  - `code` integer

## Other responses

- `400` — Bad Request

---

[API](https://skmtc.net/smallcase/apis/graph-performance-api.md) · [All operations](https://skmtc.net/smallcase/apis/graph-performance-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/smallcase/graph-performance-api/versions/6d2439eafede/schema)