NextGen Share Registry API Docs
NextGen Share Registry publishes a public, read-only JSON API and a set of machine-readable files so that software and AI agents can use our content directly. No authentication is required. There is no write API and no MCP server.
Machine-readable resources
- OpenAPI 3.1 specificationFull machine-readable API surface
https://www.nextgenregistry.com/openapi.json - llms.txt agent instructionsWhat this site is for and when an agent should use it
https://www.nextgenregistry.com/llms.txt - SitemapEvery indexable URL
https://www.nextgenregistry.com/sitemap.xml - robots.txtCrawl rules
https://www.nextgenregistry.com/robots.txt
Public endpoints
| Operation ID | Endpoint | Returns |
|---|---|---|
| listFaqs | GET /api/faqs | FAQs on RTA, ISIN, demat and corporate actions |
| listBlogPosts | GET /api/blogs | Published articles including the full body |
| listIpos | GET /api/ipo | IPO listings tracked on the site |
| getIpoBySlug | GET /api/ipo/{slug} | A single IPO listing by URL slug |
| listForms | GET /api/forms | RTA forms with direct download URLs |
| listFormCategories | GET /api/form-categories | Categories that group the RTA forms |
| listClientLogos | GET /api/client-logos | Client company logos |
Error format
Every failure returns JSON with a stable machine-readable code, a message and a recovery hint, alongside the matching HTTP status.
{
"error": {
"code": "not_found",
"message": "No API endpoint matches /api/unknown.",
"hint": "Fetch https://www.nextgenregistry.com/openapi.json for the full API surface.",
"documentation": "https://www.nextgenregistry.com/openapi.json"
}
}Codes: not_found, bad_request, method_not_allowed, internal_error.
Markdown content negotiation
Send Accept: text/markdown to any stable page URL to receive a markdown representation instead of HTML. Responses carry Vary: Accept, Accept-Encoding so a cache cannot serve the wrong variant.
curl -H "Accept: text/markdown" https://www.nextgenregistry.com/stamp-duty-calculatorRate limits
None published. Content changes at most daily, so please cache responses rather than polling. If you need higher volume or a dedicated integration, contact info@nextgenregistry.com.