Contentstack Developers
What this is
This site is the developer homebase for Contentstack, an API-first headless CMS. Use it when you are building a website or app on Contentstack and need kickstarts, guides, live streams, a public JSON API, or an MCP server — not when you need the main product marketing site.
When to use it
- You are implementing a Contentstack-powered frontend (Next.js, Nuxt, Astro, Angular, or similar).
- An AI agent needs to search, read, or cite this site's public developer content.
- You want OpenAPI, markdown, or MCP access instead of scraping HTML.
Getting started
- Read this page and Platform API & AI.
- Create a free Contentstack account if you need a stack. Browsing this site does not require an account.
- Pick a kickstart or follow a guide.
- Point an agent at
/llms.txt,/agents.md,/api/openapi.json, or the MCP endpoint.
Prerequisites
- A public HTTP client (
curl, an MCP client, or a browser). - Optional: a Contentstack stack and delivery tokens if you are building an app, not if you are only reading this site.
- Node.js is not required to consume the public JSON API or markdown.
Authentication
No authentication is required for this website, the public JSON API, markdown URLs, or the MCP server. Do not send API keys to developers.contentstack.com. Do not call unpublished or preview APIs.
Minimal example
Search public content:
curl "https://developers.contentstack.com/api/content?q=kickstart&limit=5"Read a page as markdown:
curl "https://developers.contentstack.com/index.md"OpenAPI contract:
curl "https://developers.contentstack.com/api/openapi.json"MCP Streamable HTTP (no auth): https://developers.contentstack.com/api/mcp
Failure behavior
JSON endpoints return:
{
"error": {
"code": "bad_request",
"message": "Invalid 'limit' parameter"
}
}| Status | Meaning |
|---|---|
400 | Invalid query or path input (code: bad_request) |
404 | Unknown resource (code: not_found) |
500 | Unexpected server error (code: internal_error) |
Unknown HTML paths return HTTP 404 with recovery links to /, /search, /llms.txt, /agents.md, /sitemap.xml, /sitemap.md, and /api/content. Markdown .md fallbacks use the same 404 body as text/markdown. Do not invent a replacement URL. There is no authentication challenge on public routes.
Where the API lives
| Resource | URL |
|---|---|
| OpenAPI | /api/openapi.json |
| Content search | /api/content |
| MCP discovery | /.well-known/mcp |
| MCP endpoint | /api/mcp |
| Agent policy | /agents.md |
| LLM guidance | /llms.txt |
| Full platform reference | Platform API & AI |
Component documentation
This directory also documents the React components used to build this website.
Structure
Components are organized using Atomic Design principles, a methodology for creating design systems:
- atoms/ - Basic, indivisible UI elements (buttons, icons, typography, etc.)
- molecules/ - Simple combinations of atoms (search bars, tags, cards, etc.)
- organisms/ - Complex components composed of molecules and atoms (headers, footers, sections, etc.)
- layout/ - Layout-specific components (navigation components, theme-aware logos, etc.)
- pages/ - Page-level components that compose organisms
- system/ - System-level components (error boundaries, renderers)
- cards/ - Specialized card components (search result cards)
Platform Docs
- Platform API & AI - Public JSON API, MCP server, LLM discovery, and all AI-native endpoints
- Architecture - High-level architecture and data flow
Atomic Design Explained
Atoms
The most basic building blocks. These are fundamental UI elements that cannot be broken down further:
Button- Basic button element with variantsIcons- Icon componentMediaItem- Image/media elementTitle- Typography componentRichTextRenderer- Text renderingYouTubeVideo- YouTube video embed componentCodeBlock- Syntax-highlighted code blockCodeBlockWithCopy- Code block with copy-to-clipboardCopyButton- Copy-to-clipboard buttonDateDisplay- Date displayReadingTime- Reading time estimationJsonLd- MetadataSidebar- Layout wrapper
Molecules
Combinations of atoms that form simple, reusable functional units:
SearchBar- Input + Icon atomSearchSidebar- Filter sidebar (content type, subjects, technology, person)HeaderSearch- Search with typeahead suggestionsTaxonomyTags- Subject tags with button stylingTechnologyTags- Technology terms with iconsAuthorCard- MediaItem + Link atomsAuthorLinks- List of author external linksBreadcrumb- Multiple Link atomsChapterNavigation- Guide chapter sidebar navigationChapterPagination- Previous/next chapter cardsContentTaxonomies- Technology + subject termsKickstarterLinks- Kickstart resource linksNoticesSection- Notices from additional_itemsTableOfContents- H2 table of contentsCta- Button atom wrapped in LinkFAQ- Title atom + accordion structureNotice- Alert/notice componentCanonical- Canonical link attribution
Organisms
Larger, more complex components composed of molecules and/or atoms:
AdditionalItemsSection- FAQ and Related Items from additional_itemsPersons- Multiple AuthorCard moleculesContentActions- Copy for LLM and markdown viewDefaultCard- MediaItem + Title + TaxonomyTagsIconCard- MediaItem + Title atomsHeader- AnnouncementBar + MainNavigation organismsMainNavigation- DesktopNavigation + MobileNavigationFooter- Server component that renders FooterClientFooterClient- Client-side footer with accordions and Live PreviewAnnouncementBar- Links + utility navigationHero- Title + RichTextRenderer + SearchBar + CtaList- Title + RichTextRenderer + Cards (DefaultCard/IconCard)Media- MediaItem atomRichText- Title + RichTextRenderer atomTwoColumn- Two-column layout with nested ComponentsRenderer
Dependency Rules
- Atoms should never depend on molecules or organisms
- Molecules should only depend on atoms
- Organisms can depend on molecules, atoms, and other organisms
- Pages compose organisms to create complete page layouts
Quick Links
Atoms
- Button
- Icons
- MediaItem
- Title
- RichTextRenderer
- YouTubeVideo
- CodeBlock
- CodeBlockWithCopy
- CopyButton
- DateDisplay
- ReadingTime
- JsonLd
- Sidebar
Molecules
- AuthorCard
- AuthorLinks
- Breadcrumb
- Canonical
- ChapterNavigation
- ChapterPagination
- ContentTaxonomies
- Cta
- DocsNavSidebar
- FAQ
- FilterCheckbox
- HeaderSearch
- KickstarterLinks
- ListFilters
- Notice
- NoticesSection
- Pagination
- SearchBar
- SearchSidebar
- TableOfContents
- TaxonomyTags
- TechnologyTags
Organisms
- AdditionalItemsSection
- ContentActions
- DefaultCard
- IconCard
- Persons
- Header
- MainNavigation
- Footer
- FooterClient
- AnnouncementBar
- Hero
- List
- Media
- RichText
- TwoColumn
Layout
Pages
System
- AgentMetadata - Metadata endpoints for crawlers and agents
- CachePriming - Build-time cache priming for launch.json
- ClientErrorBoundary
- ComponentsRenderer
- ErrorBoundary
- HeaderProvider - React context for header data
- MarkdownRenderer - Markdown renderer for docs pages
- MarkdownRoutes - Markdown output routes and content negotiation
- OgImageFallback - Automatic OG fallback image generator
- ScrollToTop - Scroll to top on route changes
Cards
- SearchResultCard - Compact card for search typeahead