Listing Thumbnail

    Ticker-Driven Shenzhen XSHE Stocks News API & MCP Server for AI Agents

     Info
    Quick Launch
    Empower investors, traders, and analysts with real-time multilingual news for every XSHE-listed company. The Ticker-Driven Shenzhen Stock Exchange Stocks News API delivers AI-curated headlines, concise briefs, and full-text articles across 100+ languages. Simply input a stock ticker like 2594 or 2936 to access market-moving coverage from verified global sources - optimized for integration into trading terminals, portfolio dashboards, and analytics platforms.

    Overview

    Track Shenzhen Stock Exchange Stock News with Precision

    The service news-xshe is built for teams that need focused news retrieval across the Shenzhen Stock Exchange investing universe. Instead of searching the open web in a broad and noisy way, you can query online news specifically through XSHE MIC codes and related company identifiers, making it easier to retrieve coverage around listed companies, sectors, holdings, and market themes tied to Shenzhen Stock Exchange.

    For portfolio products, investor tools, research workflows, and AI-driven finance applications, that matters because Shenzhen Stock Exchange is part of a live trading ecosystem with active daily turnover and participation from retail investors, institutions, issuers, analysts, market-makers, founders, employees, customers, suppliers, regulators, and other stakeholders whose decisions are often influenced by current news flow.


    Built for the Shenzhen Stock Exchange Investing Universe

    Shenzhen Stock Exchange is an important market for investors who care about company developments, sector moves, earnings narratives, market sentiment, and shifts in portfolio exposure. News tied to companies in this exchange can affect how investors think about positions, watchlists, risk, and opportunity. The service news-xshe helps you go deep into that universe by narrowing retrieval to Shenzhen Stock Exchange-linked entities instead of mixing them into a generic market-wide feed.

    That makes it easier to build products and workflows where relevance matters more than raw article volume. If your users care about holdings, peer groups, sector baskets, or market themes connected to Shenzhen Stock Exchange-listed companies, this service gives you a cleaner retrieval layer to build on.


    • MIC-code-based retrieval helps applications target Shenzhen Stock Exchange-linked companies more precisely than broad keyword-only search.
    • Coverage for a live market ecosystem supports workflows around companies that attract investor, analyst, media, and stakeholder attention.
    • Boolean search support using operators like plus, minus, AND, and OR helps refine queries and reduce noise.
    • Country and language filters improve relevance when users want news from a specific market context or language environment.
    • Multiple output depths let you choose headlines, briefs, or full text depending on the speed and depth your workflow needs.

    • App developers building portfolio trackers, investing dashboards, screening tools, or workflow automation around listed companies.
    • Equity researchers who need current news tied to Shenzhen Stock Exchange companies, sectors, earnings narratives, and market-moving events.
    • Content writers and newsletter operators covering public markets, company developments, earnings, and investment themes.
    • Social media creators in finance who need faster discovery of relevant stock-specific stories to support posts, threads, videos, and commentary.
    • AI product teams that want to combine market news retrieval with summarization, ranking, sentiment review, and portfolio analysis.

    • Headlines endpoints for rapid monitoring across watchlists, market scans, and alerting workflows.
    • Brief endpoints when you need more context than a headline without always ingesting full articles.
    • Fulltext endpoints for deeper company research, event analysis, and downstream AI processing.
    • Country and language filters to focus retrieval on the investor audience or geography that matters most.
    • Structured responses that can flow directly into financial apps, analytics layers, notification systems, or AI tools.

    • Automatic portfolio monitoring lets users configure their trading or investing app portfolio and receive news updates tied to the companies they already hold.
    • Watchlist-driven retrieval supports investors who want separate coverage for current positions, target entries, and sector themes.
    • Notification pipelines can turn fresh company news into app alerts, research queues, digest emails, or custom dashboards.
    • Holdings-level enrichment helps add current news context next to positions, performance charts, and company fundamentals.
    • Multi-company scanning makes it easier to monitor an entire portfolio instead of checking each stock manually.

    • MCP support makes news-xshe suitable for AI-agent environments that need live access to current company news.
    • Portfolio-aware agents can fetch news for portfolio companies, compare developments across holdings, and identify which stories deserve attention first.
    • Analyst-style workflows can combine retrieval with summaries, bullish or bearish signal extraction, event clustering, and narrative tracking.
    • Research copilots can use headlines, briefs, or full text to explain what is happening across a user's portfolio and why it may matter.
    • Decision-support pipelines can pair current news

    Highlights

    • Real-time data access
    • Multi-language support
    • Comprehensive coverage of news

    Details

    Delivery method

    Deployed on AWS
    New

    Introducing multi-product solutions

    You can now purchase comprehensive solutions tailored to use cases and industries.

    Multi-product solutions

    Features and programs

    Financing for AWS Marketplace purchases

    AWS Marketplace now accepts line of credit payments through the PNC Vendor Finance program. This program is available to select AWS customers in the US, excluding NV, NC, ND, TN, & VT.
    Financing for AWS Marketplace purchases

    Quick Launch

    Leverage AWS CloudFormation templates to reduce the time and resources required to configure, deploy, and launch your software.

    Pricing

    Ticker-Driven Shenzhen XSHE Stocks News API & MCP Server for AI Agents

     Info
    Pricing is based on the duration and terms of your contract with the vendor, and additional usage. You pay upfront or in installments according to your contract terms with the vendor. This entitles you to a specified quantity of use for the contract duration. Usage-based pricing is in effect for overages or additional usage not covered in the contract. These charges are applied on top of the contract price. If you choose not to renew or replace your contract before the contract end date, access to your entitlements will expire.
    Additional AWS infrastructure costs may apply. Use the AWS Pricing Calculator  to estimate your infrastructure costs.

    1-month contract (4)

     Info
    Dimension
    Description
    Cost/month
    Overage cost
    Micro Tier
    Designed for individual users, small teams, and early experiments. Ideal for testing, prototyping, and light monitoring needs. Limited daily searches and alerts. Access to core endpoints (headlines, briefs). Suitable for freelancers, researchers, and small projects.
    $25.00
    Starter Tier
    Built for growing startups and small organizations that need consistent, structured news intelligence. Expanded daily query and alert limits. Full-text articles with metadata and translations. Scheduled digests and basic MCP integration. Perfect for startups building media-driven apps or compliance workflows.
    $100.00
    Business Tier
    Optimized for SMBs, agencies, and mid-sized enterprises that require continuous, cross-market monitoring. High-volume queries and alerts across multiple regions/languages. Full API and MCP server integration with AI/LLM workflows. Access to enriched data: entities, Wikidata IDs, sentiment. Priority email support and advanced scheduling. Best for marketing, compliance, and research teams managing multiple clients/projects.
    $250.00
    Enterprise Tier
    Comprehensive package for large enterprises, institutions, and global organizations with advanced compliance or intelligence needs. Unlimited or custom query/alert volumes. Multi-tenant dashboards, role-based access, and advanced security. SLA-backed support, dedicated success manager, custom integrations. Real-time streaming feeds, regulatory monitoring, and AI-driven executive summaries. Designed for compliance teams, global corporations, financial institutions, and government agencies.
    $750.00

    Vendor refund policy

    All billed amounts are non-refundable. Charges are incurred once usage or subscription billing begins. No refunds or credits are issued for partial usage, cancellations, or unused time. Billing errors, if any, will be reviewed at Press Monitor's discretion.

    How can we make this page better?

    Tell us how we can improve this page, or report an issue with this product.
    Tell us how we can improve this page, or report an issue with this product.

    Legal

    Vendor terms and conditions

    Upon subscribing to this product, you must acknowledge and agree to the terms and conditions outlined in the vendor's End User License Agreement (EULA) .

    Content disclaimer

    Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.

    Usage information

     Info

    Delivery details

    Software as a Service (SaaS)

    SaaS delivers cloud-based software applications directly to customers over the internet. You can access these applications through a subscription model. You will pay recurring monthly usage fees through your AWS bill, while AWS handles deployment and infrastructure management, ensuring scalability, reliability, and seamless integration with other AWS services.

    Additional details

    Usage instructions

    Usage Instructions – Press Monitor API & MCP Server

    XSHE Ticker-Driven News API - Usage Guide

    API Documentation

    <https://www.pressmonitor.com/en/docs/news-xshe-api-mcp>

    Overview

    The Ticker-Driven Shenzhen Stock Exchange (XSHE) News API provides real-time, multilingual news access for all XSHE-listed companies. Access critical market-moving news across 100+ languages by simply providing a stock ticker symbol. This API is designed for traders, investors, wealth management platforms, and trading terminals.

    API Version: 1.0.1


    Base URL

    <https://api.pressmonitor.com/news-xshe/v1>

    Authentication

    All endpoints require Bearer Token authentication with the format:

    Authorization: Bearer secret_key:subscription_id

    Example:

    curl -H "Authorization: Bearer YOUR_SECRET_KEY:YOUR_SUBSCRIPTION_ID" \ "https://api.pressmonitor.com/news-xshe/v1/news-headlines?ticker=2594"

    Available Endpoints

    1. /names - Resolve Company Names to Tickers

    Method: GET Operation ID: resolveNames

    Convert partial or full company names into XSHE ticker symbols.

    Parameters:

    • name (required) - Partial or full company name (e.g., 'BYD' → 2594, BYD Company Limited)
    • count (optional) - Maximum number of results (default: 20, max: 100)

    Example:

    curl -H "Authorization: Bearer YOUR_TOKEN" \ "https://api.pressmonitor.com/news-xshe/v1/names?name=BYD&count=5"

    Response:

    [ { "ticker": "2594", "name": "BYD Company Limited" }, { "ticker": "2936", "name": "Ping An Bank Co., Ltd." } ]

    2. /news-headlines - News Headlines

    Method: GET Operation ID: newsHeadlines Credits: 1 per story

    Returns basic news headlines with titles and URLs.

    Parameters:

    • ticker (required) - XSHE stock ticker symbol (e.g., 2594, 2936)
    • country_code (optional) - Filter by ISO-3166-1 alpha-2 country codes
    • lang_code (optional) - Filter by ISO-639-1 language codes
    • count (optional) - Number of results (default: 20)
    • sort (optional) - latest (default) or relevance
    • search_after (optional) - Pagination cursor (only with sort=latest)

    Example:

    curl -H "Authorization: Bearer YOUR_TOKEN" \ "https://api.pressmonitor.com/news-xshe/v1/news-headlines?ticker=2594&lang_code=en&count=10&sort=latest"

    Response Fields:

    • id - Unique story identifier
    • title - Article headline
    • url - Link to original article
    • source - Publication name
    • lang_code - Language code
    • country_code - Source country
    • ts - Publish timestamp (epoch seconds)

    3. /news-briefs - News Briefs

    Method: GET Operation ID: newsBriefs Credits: 2 per story

    Returns headlines with short AI-generated summaries.

    Parameters: Same as /news-headlines

    Example:

    curl -H "Authorization: Bearer YOUR_TOKEN" \ "https://api.pressmonitor.com/news-xshe/v1/news-briefs?ticker=2936&country_code=CN&sort=relevance"

    Response Fields: All headline fields plus:

    • description - AI-generated brief summary
    • images - Array of image URLs
    • caption - Image caption

    4. /news-fulltext - Full Articles

    Method: GET Operation ID: newsFulltext Credits: 5 per story

    Returns complete articles with full body text.

    Parameters: Same as /news-headlines

    Example:

    curl -H "Authorization: Bearer YOUR_TOKEN" \ "https://api.pressmonitor.com/news-xshe/v1/news-fulltext?ticker=2415&lang_code=en&count=5"

    Response Fields: All brief fields plus:

    • body - Full article text

    5. /news-fulltext-metadata - Full Articles + Metadata

    Method: GET Operation ID: newsFulltextMetadata Credits: 7 per story

    Returns full articles with enriched metadata for knowledge graphs and compliance.

    Parameters: Same as /news-headlines

    Example:

    curl -H "Authorization: Bearer YOUR_TOKEN" \ "https://api.pressmonitor.com/news-xshe/v1/news-fulltext-metadata?ticker=300750&count=3"

    Response Fields: All fulltext fields plus:

    • wikidata - Wikidata IDs and metadata (object)
    • entities - Named entities (array of objects)
    • mediatopics - IPTC Media Topics subject codes (array)

    6. Translated Endpoints

    Add -translated suffix to any news endpoint for machine translation. Requires additional target_lang_code parameter.

    Available Translated Endpoints:

    • /news-headlines-translated (2 credits/story)
    • /news-briefs-translated (4 credits/story)
    • /news-fulltext-translated (10 credits/story)
    • /news-fulltext-metadata-translated (14 credits/story)

    Example:

    curl -H "Authorization: Bearer YOUR_TOKEN" \ "https://api.pressmonitor.com/news-xshe/v1/news-headlines-translated?ticker=2594&target_lang_code=zh&count=5"

    Translation Response Format: Each item includes a tr object with translated fields:

    { "id": "...", "title": "Original Title", "tr": { "title": "翻译标题", "description": "翻译描述", "source_lang_code": "en", "target_lang_code": "zh" } }

    Pagination

    When using sort=latest, responses include a next object with pagination info:

    { "items": [...], "credits": {...}, "next": { "search_after": "opaque_cursor_string", "count": 20, "sort": "latest" } }

    Use search_after value in your next request:

    curl -H "Authorization: Bearer YOUR_TOKEN" \ "https://api.pressmonitor.com/news-xshe/v1/news-headlines?ticker=2594&search_after=CURSOR&sort=latest"

    Response Headers

    All responses include:

    • X-Request-ID - Request identifier for debugging
    • X-RateLimit-Limit - Max requests in current window
    • X-RateLimit-Remaining - Remaining requests
    • X-RateLimit-Reset - Epoch seconds until quota resets

    Credits Tracking

    All responses include a credits object:

    { "credits": { "rate": 1, "quantity": 15, "total": 9850, "request_id": "req_abc123" } }
    • rate - Credits per story
    • quantity - Credits charged for this response
    • total - Total credits remaining
    • request_id - Request identifier

    Error Responses

    All errors follow RFC 7807 Problem Details format:

    { "type": "about:blank", "title": "Bad Request", "status": 400, "detail": "Missing required parameter: ticker", "instance": "/news-headlines" }

    HTTP Status Codes:

    • 400 - Bad request (invalid parameters)
    • 401 - Unauthorized (missing/invalid token)
    • 403 - Forbidden (subscription/plan restriction)
    • 429 - Too Many Requests (rate limit exceeded)
    • 500 - Server error

    Best Practices

    1. Use appropriate endpoints - Headlines for quick scans, fulltext for analysis
    2. Leverage pagination - Use search_after for large result sets with sort=latest
    3. Filter by language/country - Reduce noise and credits usage
    4. Monitor credits - Track credits.total in responses
    5. Handle rate limits - Respect X-RateLimit-* headers
    6. Cache results - Avoid redundant requests for the same data
    7. Use sort=relevance for topic research, sort=latest for real-time monitoring

    Example Workflow: Track BYD Company News

    # 1. Get latest headlines curl -H "Authorization: Bearer YOUR_TOKEN" \ "https://api.pressmonitor.com/news-xshe/v1/news-headlines?ticker=2594&lang_code=en&count=20&sort=latest" # 2. Get detailed briefs for important stories curl -H "Authorization: Bearer YOUR_TOKEN" \ "https://api.pressmonitor.com/news-xshe/v1/news-briefs?ticker=2594&lang_code=en&count=5&sort=relevance" # 3. Fetch full articles for deep analysis curl -H "Authorization: Bearer YOUR_TOKEN" \ "https://api.pressmonitor.com/news-xshe/v1/news-fulltext?ticker=2594&lang_code=en&count=3" # 4. Get enriched metadata for compliance curl -H "Authorization: Bearer YOUR_TOKEN" \ "https://api.pressmonitor.com/news-xshe/v1/news-fulltext-metadata?ticker=2594&count=1"

    Support

    Docs: https://www.pressmonitor.com/en/docs/news-xshe-api-mcp  

    Email: support@pressmonitor.com 

    XSHE Ticker-Driven News MCP Server - Usage Guide

    Overview

    The XSHE Ticker-Driven News MCP Server provides AI agents and automation workflows with tools for accessing real-time, multilingual news about XSHE-listed companies. Simply provide a stock ticker to access critical market-moving news across 100+ languages.

    MCP Version: 1.0.0


    Base URL

    <https://mcp.bespokeapps.com/news-xshe/v1>

    Authentication

    All MCP calls require:

    Authorization: Bearer YOUR_API_KEY

    MCP Configuration

    Add this to your mcp.json configuration file:

    { "mcpServers": { "xshe-ticker-news": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.bespokeapps.com/news-xshe/v1", "--header", "Authorization: Bearer ${XSHE_NEWS_API_TOKEN}" ], "env": { "XSHE_NEWS_API_TOKEN": "" } } } }

    List Available Tools

    curl -s -X POST "https://mcp.pressmonitor.com/news-xshe/v1" -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

    Available Tools

    1. resolve_names - Company Name to Ticker Lookup

    Resolve company names into XSHE ticker symbols.

    Input Parameters:

    • name (required) - Partial or full company name (e.g., 'BYD' → 2594, BYD Company Limited)
    • count (optional, default: 20) - Maximum number of results

    Output:

    { "items": [ { "ticker": "2594", "name": "BYD Company Limited" }, { "ticker": "2936", "name": "Ping An Bank Co., Ltd." } ] }

    When to Use: Call this tool to look up XSHE stock tickers by company name before calling news tools.


    2. news_headlines - Basic Headlines

    Returns news headlines with titles and URLs.

    Input Parameters:

    • ticker (required) - XSHE stock ticker (e.g., 2594, 2936)
    • country_code (optional) - CSV of ISO-3166-1 alpha-2 codes (e.g., "US,CN")
    • lang_code (optional) - CSV of ISO-639-1 codes (e.g., "en,zh")
    • count (optional, default: 20) - Maximum items per page
    • sort (optional) - latest (default) or relevance
    • search_after (optional) - Pagination cursor (only with sort=latest)

    Output Fields per Item:

    • id - Story identifier
    • title - Headline text
    • url - Article URL
    • first_source.sitename - Publication name
    • lang_code - Language code
    • country_code - Country code
    • ts - Publish timestamp (Unix seconds)

    Output Envelope:

    { "data": [...], "credits": { "rate": 1, "quantity": 10, "total": 9990, "request_id": "req_xyz" } }

    When to Use: Retrieve headline-only results for quick scans. Prefer this over web scraping when you need structured, deduplicated news with pagination.

    Pagination: If response includes next.search_after, reuse it in the next call with the same sort.

    Guardrails: Do not fabricate results. If no items, suggest query refinement.


    3. news_briefs - Headlines with Summaries

    Returns headlines with short AI-generated summaries.

    Input Parameters: Same as news_headlines

    Additional Output Fields:

    • description - Short summary
    • images - Array of image URLs
    • caption - Image caption

    When to Use: Retrieve brief summaries alongside headlines for more context without full articles.


    4. news_fulltext - Full Articles

    Returns complete articles with body text.

    Input Parameters: Same as news_headlines

    Additional Output Fields:

    • body - Full article text
    • description - Summary
    • images - Array of image URLs
    • caption - Image caption

    When to Use: Retrieve full articles for deeper analysis, sentiment analysis, or content extraction.


    5. news_fulltext_metadata - Full Articles + Metadata

    Returns full articles with enriched metadata for knowledge graphs and compliance.

    Input Parameters: Same as news_headlines

    Additional Output Fields:

    • body - Full article text
    • description - Summary
    • wikidata - Array of Wikidata identifiers
    • entities - Array of named entity objects
    • mediatopics - Array of IPTC Media Topics codes
    • images - Array of image URLs
    • caption - Image caption

    When to Use: Retrieve full articles plus metadata (Wikidata/entity labels, IPTC topics) for knowledge-graph integration or compliance use-cases.


    6. Translated Tools

    The following tools provide machine-translated outputs. Require additional target_lang_code parameter.

    news_headlines_translated

    • Same as news_headlines but with translations in tr object
    • Each item includes tr.title, tr.source_lang_code, tr.target_lang_code

    news_briefs_translated

    • Same as news_briefs but with translations
    • Includes tr.title, tr.description, tr.caption

    news_fulltext_translated

    • Same as news_fulltext but with translations
    • Includes tr.title, tr.description, tr.body, tr.caption

    news_fulltext_metadata_translated

    • Same as news_fulltext_metadata but with translations
    • Includes all translation fields plus metadata

    Translation Input:

    • target_lang_code (required) - ISO-639-1 code to translate into (e.g., "zh", "en")

    Translation Output: Each item includes a tr object:

    { "id": "...", "title": "Original Title", "tr": { "title": "Translated Title", "description": "Translated Description", "source_lang_code": "en", "target_lang_code": "zh" } }

    Common Patterns

    Pattern 1: Lookup Ticker, Then Get News

    1. Call resolve_names with name="BYD" 2. Extract ticker="2594" from results 3. Call news_headlines with ticker="2594"

    Pattern 2: Monitor Latest News

    1. Call news_headlines with ticker="2936", sort="latest", count=20 2. Process results 3. If next.search_after exists, call again with search_after cursor

    Pattern 3: Multi-language News

    1. Call news_headlines_translated with ticker="2415", target_lang_code="zh" 2. Use tr.title for Chinese headline, title for original

    Pattern 4: Deep Analysis with Metadata

    1. Call news_fulltext_metadata with ticker="300750", count=10 2. Extract entities, wikidata, mediatopics for knowledge graph 3. Analyze body text for sentiment or key topics

    Pagination Strategy

    When sort=latest:

    1. Initial request returns next.search_after in response
    2. Use search_after value in subsequent requests
    3. Keep sort and count consistent
    4. Stop when next object is absent

    Example:

    Request 1: ticker=2594, sort=latest, count=20 Response 1: {data: [...], next: {search_after: "cursor1"}} Request 2: ticker=2594, sort=latest, count=20, search_after="cursor1" Response 2: {data: [...], next: {search_after: "cursor2"}} ...continue until next is absent

    Sort Modes

    sort=latest (default)

    • Orders by publish time (newest first)
    • Supports pagination via search_after
    • Best for: Real-time monitoring, news feeds

    sort=relevance

    • Orders by relevance to ticker/query
    • Pagination via offset (if supported)
    • Best for: Topic research, finding most relevant stories

    Credits & Usage Tracking

    All tools return a credits object:

    { "credits": { "rate": 1, "quantity": 15, "total": 9850, "request_id": "req_abc123" } }

    Credits per Tool:

    • news_headlines: 1 per story
    • news_briefs: 2 per story
    • news_fulltext: 5 per story
    • news_fulltext_metadata: 7 per story
    • news_headlines_translated: 2 per story
    • news_briefs_translated: 4 per story
    • news_fulltext_translated: 10 per story
    • news_fulltext_metadata_translated: 14 per story

    Monitor Usage:

    • Track credits.total to monitor remaining credits
    • Use credits.request_id for debugging
    • Optimize count to balance coverage and cost

    Error Handling

    Tools may fail due to:

    • Invalid ticker - Verify ticker exists on XSHE
    • Missing authentication - Check Bearer token format
    • Rate limits - Reduce request frequency
    • No results - Try broader filters or different time range

    Recommended Strategy:

    1. Validate ticker with resolve_names first
    2. Start with small count (5-10) for testing
    3. Handle empty data arrays gracefully
    4. Log request_id for support requests

    Best Practices

    1. Start with resolve_names - Validate ticker before news queries
    2. Use appropriate depth - Headlines for scans, fulltext for analysis
    3. Filter by language - Use lang_code to reduce noise
    4. Filter by country - Use country_code for regional focus
    5. Paginate wisely - Use search_after with sort=latest for chronological feeds
    6. Monitor credits - Check credits.total regularly
    7. Cache results - Avoid redundant calls for same ticker/time
    8. Handle empty results - Suggest query refinement to user

    Example Workflow: Track BYD Company News

    Step 1: Verify ticker Tool: resolve_names Input: {name: "BYD"} Output: {items: [{ticker: "2594", name: "BYD Company Limited"}]} Step 2: Get latest headlines Tool: news_headlines Input: {ticker: "2594", lang_code: "en", count: 20, sort: "latest"} Output: {data: [...20 headlines...], credits: {...}, next: {search_after: "..."}} Step 3: Get detailed briefs for top stories Tool: news_briefs Input: {ticker: "2594", lang_code: "en", count: 5, sort: "relevance"} Output: {items: [...5 briefs with summaries...], credits: {...}} Step 4: Deep dive into one article Tool: news_fulltext_metadata Input: {ticker: "2594", count: 1} Output: {items: [{id, title, body, entities, wikidata, mediatopics, ...}], credits: {...}} Step 5: Translate for international audience Tool: news_headlines_translated Input: {ticker: "2594", target_lang_code: "zh", count: 10} Output: {items: [{title: "...", tr: {title: "...", target_lang_code: "zh"}}], credits: {...}}

    Integration Tips

    For Trading Platforms

    • Use news_headlines with sort=latest for real-time ticker feeds
    • Filter by lang_code=en for English-speaking users
    • Cache headlines for 1-5 minutes to reduce API calls

    For Investment Research

    • Use news_fulltext_metadata for entity extraction and topic analysis
    • Combine wikidata and entities for knowledge graphs
    • Use sort=relevance for topic-driven research

    For Multilingual Dashboards

    • Use translated tools with user's target_lang_code
    • Display both original and translated titles for verification
    • Cache translations to minimize credit usage

    For Alert Systems

    • Poll news_headlines every 5-15 minutes with sort=latest
    • Track search_after to avoid duplicate alerts
    • Filter by country_code for regional alerts

    Support

    Docs: https://www.pressmonitor.com/en/docs/news-xshe-api-mcp  

    Email: support@pressmonitor.com 

    Support

    Vendor support

    Email: support@pressmonitor.com 

    Customers receive complete developer and enterprise support, including:

    • 24 x 7 API uptime monitoring and incident alerts.
    • Comprehensive documentation and sample code.
    • Integration help for authentication, rate-optimization, and MCP server linking.
    • Assistance with advanced use cases (translation, compliance tagging, metadata enrichment).

    Press Monitor provides SLA-backed response times for enterprise clients and proactive guidance for AWS Marketplace subscribers.

    AWS infrastructure support

    AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.

    Similar products

    Customer reviews

    Ratings and reviews

     Info
    0 ratings
    5 star
    4 star
    3 star
    2 star
    1 star
    0%
    0%
    0%
    0%
    0%
    0 reviews
    No customer reviews yet
    Be the first to review this product . We've partnered with PeerSpot to gather customer feedback. You can share your experience by writing or recording a review, or scheduling a call with a PeerSpot analyst.