Univest's recommendation feed, portfolio ratings, and trade alerts

Three things move through Univest's servers worth wiring into another system: the daily Buy, Sell and Hold calls its analysts publish, the live profit-and-loss on each user's tracked holdings, and the exit alerts that fire the moment a position should be closed. The app describes a research team of SEBI-registered analysts with 75+ years of combined experience, and its listing cites over 30 lakh (roughly three million) users. For an integrator, the interesting part is not the marketing reach but the shape of the feed: short, structured calls with an entry, a target, a stop-loss and a linked report, arriving on a schedule the market sets.

The lead this page takes is the alert stream. Univest's whole value is timing, so the calls go out fast and over several channels at once. That makes a push-style integration the natural spine: receive each call as an event, normalize it, and let portfolio state catch up on a slower sync. Holdings that need to be broker-accurate rather than app-reported are a separate problem, and India has a clean consented route for those. Both are covered below.

What sits behind a Univest login

Mapped from the app's own description and its public Pro pages, these are the surfaces an integration would actually touch. Granularity is what the app exposes to the account holder, not an internal guess.

Three authorized routes to the data

Which route fits depends on whether you want Univest's own view of a position or the user's underlying market record.

1. Authorized interface integration

Protocol analysis of the app's own traffic, run against a consenting account, reaches the proprietary layer: the recommendation feed, the tracker ratings, entitlements, and the alert events as they publish. This carries most of the load because the calls and the Buy/Sell/Hold ratings exist only inside Univest, not in any shared standard. Effort is moderate; durability holds as long as we re-validate the parsed shapes when the app ships a notable update, which is part of how we maintain a build.

2. RBI Account Aggregator consent

Where a project needs broker-verified holdings rather than Univest's self-reported tracker, India's Account Aggregator network is the consented path to securities data (brokerage and mutual funds sit within its scope). The user authorizes a specific purpose and duration through a regulated AA, and the data flows to a registered financial information user. We design and stand up that consent flow; the user's own authorization is what makes it dependable, not any single app endpoint.

3. User-consented session access

For per-user pulls that the Account Aggregator does not cover — the advisory layer, plan status, the report archive — a consented session against the account fills the gap. Lightweight, scoped to one user, and useful when the integration is per-member rather than fleet-wide.

For most teams the interface route is what the integration runs on day to day, with the alert webhook as its front door. The Account Aggregator path is worth adding only when broker-accurate holdings matter; the consented-session route is the fallback for the narrow personal surfaces neither of the first two reach.

What lands in your repository

Everything is yours to run, not a hosted black box. The order below reflects what teams use first on a Univest build.

• Runnable clients in Python and Node.js for the recommendation feed and the portfolio endpoints, with the auth handshake wired in.
• A trade-alert webhook handler that ingests each call as it publishes and writes one normalized record across the push, WhatsApp and Telegram copies.
• An automated test suite built from captured response fixtures, covering the recommendation, portfolio and alert shapes.
• A sync design that splits the work: real-time push for alerts, a cursor-based pull for portfolio P&L on the cadence you choose.
• An OpenAPI / Swagger description of the surfaces in scope, for your own tooling.
• A protocol and auth-flow report covering the login, OTP and token-refresh chain as it behaves here.
• Interface documentation and data-retention guidance aligned to the SEBI record-keeping rules below.

Inside the alert-feed handler

The snippet below is illustrative; exact field names are confirmed against captured responses during the build. It shows the core job of the webhook: take a published call, parse it once, and key it so the same alert arriving on three channels does not become three records.

// Normalizing a Univest trade-alert event into one canonical record.
// The same call can arrive via push, WhatsApp and the Telegram channel.

app.post("/hooks/univest/alert", (req, res) => {
  const e = req.body;                       // raw alert payload
  const call = {
    id:         e.call_id,                  // key used to collapse channel duplicates
    instrument: e.symbol,                   // e.g. "TATAMOTORS" (NSE)
    segment:    e.segment,                  // EQ | FUT | OPT | COMM
    action:     e.action,                   // BUY | SELL | HOLD | EXIT
    entry:      e.entry_price,
    target:     e.target_price,
    stopLoss:   e.stop_loss,
    horizon:    e.timeframe,                // intraday | short | medium | long
    rationale:  e.note,                     // analyst comment / linked report id
    analystReg: e.ra_registration,          // SEBI RA registration of the issuing desk
    issuedAt:   e.published_at
  };
  store.upsert(call.id, call);              // a repeat call_id resolves to one row
  res.sendStatus(200);
});

// Portfolio pull (illustrative response):
// GET /portfolio/holdings
// [{ "symbol":"INFY", "qty":40, "avg":1450.0,
//    "ltp":1502.3, "pnl":2092.0,
//    "rating":"HOLD", "source":"broker_linked" }]

Builds teams ask us for

• Stream Univest's daily calls into an internal trading-desk board, each row showing the entry, target and stop-loss with the report one click away.
• Fold a user's Univest portfolio ratings into a multi-account wealth view, tagging which holdings are broker-linked and which were typed in by hand.
• Catch exit alerts the instant they fire and hand them to a downstream risk or notification service, so a closed call triggers action without a person watching three chat apps.

Consent, SEBI oversight, and the Account Aggregator route

Univest's research arm, Uniresearch India Pvt Ltd, is described in the app's own listing as a SEBI-registered research analyst (registration INH000013776, as the app states it). That places the recommendation feed under the SEBI (Research Analysts) Regulations, 2014, which per SEBI's published text were last amended on 16 December 2024 and require analysts to keep client interaction and KYC records for at least five years and to disclose standardized terms before service begins. An integration that stores calls and member data should retain alongside the same evidence, which is how we set up logging and consent records on these builds.

For the holdings layer, the relevant mechanism is the RBI-regulated Account Aggregator network, live since 2021, under which securities data can be shared only with explicit, purpose-bound and revocable consent, and only to a regulated financial information user. We design the sync so a consent's purpose and validity window are honored and a revocation is respected. Personal data handling follows India's Digital Personal Data Protection Act, 2023, on a data-minimized basis, under NDA where the engagement calls for it.

What we plan around on Univest

Two or three details about this app shape the build, and we account for each rather than leave them to you.

Tier-dependent visibility

What a session can see tracks the user's Pro plan — Lite shows stock calls, while futures, options and commodity ideas live behind Plus, Alpha, Super and Black. We map entitlements per tier so the integration reads a missing F&O call as "not subscribed", not as a fault.

One call, three channels

The same recommendation goes out over push, WhatsApp and Telegram. We collapse those to a single canonical event keyed on the call id, so a downstream system acts on a Buy once even though it was notified three times.

Broker-linked versus manual holdings

The tracker mixes positions pulled from a linked broker with ones a user added by hand. We tag each row by source so any reconciliation knows which figures are authoritative and which are self-reported.

Timing and cost

A first working drop — the alert webhook handler plus a portfolio client with its tests — lands inside one to two weeks. Source code is delivered from $300, and you pay after delivery, once the build does what you needed it to do. The other option is a pay-per-call hosted API: you call our endpoints and pay only for the calls you make, with nothing upfront. You bring the app name and what you want from its data; access to a consenting account or a sandbox and any compliance paperwork are arranged together with you as the work begins.

Tell us what you need from Univest

Screens this brief draws on

Public store screenshots used while mapping the surfaces above. Select one to enlarge.

How this brief came together

Drafted on 15 June 2026 from the live Google Play and App Store listings, Univest's own Pro subscription pages, and primary regulatory text from SEBI and the Government of India on the Account Aggregator framework. Where a number or registration appears above it is attributed to the source that states it; nothing here is asserted beyond what those pages show. Compiled by OpenFinance Lab, 15 June 2026.

• Univest on Google Play (com.univest.capp)
• Univest Pro subscription tiers
• SEBI (Research Analysts) Regulations, 2014 (amended Dec 2024)
• Account Aggregator framework — Dept. of Financial Services, Govt. of India

Univest among India's research and broking apps

A unified integration usually has to read more than one of these, since users hold positions and watchlists across several. Each is named for context, not ranked.

• Groww — broker for mutual funds and direct equity; holdings, orders and NAV history sit behind a login.
• Zerodha Kite — discount-broker trading terminal exposing order book, positions and holdings per account.
• Tickertape — research and screening tool with per-user watchlists, scorecards and portfolio analytics.
• Trendlyne — analyst targets, screeners and alert subscriptions tied to a user account.
• StockEdge — scans and study tools with account-bound watchlists and saved research.
• Screener.in — fundamental data with saved screens and watchlists per login.
• StreetGains — SEBI-registered advisory that pushes trade calls, with alert delivery much like Univest's.
• Eqsis — options-focused advisory and training with member calls behind a subscription.

What integrators ask about Univest

Univest pushes its calls over WhatsApp, push notifications and Telegram. How do you receive them in real time?

We stand up a webhook handler that takes the alert event the moment it is published and collapses the three delivery channels into one canonical record keyed on the call id, so the same Buy or Exit call arriving on push and on Telegram is stored once. From there it flows into whatever you run downstream, with entry, target, stop-loss and the linked rationale already parsed.

Can you read a user's real holdings, or only Univest's own Buy/Sell/Hold ratings?

Both, by different routes. Univest's own tracker ratings and the live P&L it shows come through the authorized interface route against a consenting account. Broker-verified holdings sit a layer below, in the user's demat and brokerage records, and those are reached through the RBI Account Aggregator consent flow where the project needs figures the user has independently confirmed.

Does the data you can pull change with the Univest Pro tier a user holds?

Yes. Univest gates trade ideas by plan, so a Pro Lite session surfaces stock calls while futures, options and commodity calls sit behind Pro Plus, Alpha, Super and Black. We map entitlements per tier during the build so the integration expects exactly the segments a given subscription includes rather than treating a missing F&O call as an error.

What would you hand over first for a Univest integration?

Usually the alert webhook handler plus a portfolio client with a test suite, inside one to two weeks. To begin we only need the app name and what you want out of its data; access to a consenting account or a sandbox and any compliance paperwork are arranged together with you as the work starts.