Submit Documents Directly to SitecoreAI Search Indexes with the Ingestion Service API
In This Article
SitecoreAI now provides the Ingestion Service API, enabling developers to programmatically send documents directly to search indexes through authenticated API requests. This new capability offers greater flexibility and control over how indexed content is created, updated, and removed.
Key Capabilities
With the Ingestion Service API, developers can:
- Create indexed documents directly within SitecoreAI search indexes.
- Update existing documents when source content changes.
- Delete indexed documents that are no longer required.
- Synchronize external content with SitecoreAI without depending on traditional crawling workflows.
- Perform targeted additions, updates, and deletions across push, site, and content sources.
- Keep search indexes synchronized with changes occurring in external applications and systems.
Find Sitecore Search Gaps Before They Impact Visibility
Why It Matters
The Ingestion Service API provides a consistent and programmatic approach to managing indexed content across different source types. It is especially useful for integrations where developers need direct control over indexing operations, faster content synchronization, and automated search-index maintenance.
This makes it easier to connect external content platforms and applications with SitecoreAI while keeping search experiences up to date with the latest content changes.
Read more: Sitecore AI
Frequently Asked Questions
What is the SitecoreAI Ingestion Service API?
The SitecoreAI Ingestion Service API allows developers to programmatically create, update, and delete documents directly within SitecoreAI search indexes using authenticated API requests.
What can developers do with the SitecoreAI Ingestion Service API?
Developers can create indexed documents, update existing documents, remove outdated documents, synchronize external content, and automate targeted indexing operations across supported source types.
How does direct ingestion differ from traditional crawling?
Traditional crawling discovers content by visiting pages or sources, while direct ingestion lets applications send document changes directly to the search index. This gives developers more control over timing, updates, and deletions.
Can SitecoreAI synchronize content from external systems?
Yes. The Ingestion Service API can be used to synchronize content from external applications, platforms, databases, or workflows directly with SitecoreAI search indexes.
Can the Ingestion Service API update existing indexed documents?
Yes. Developers can programmatically update indexed documents when source content changes, helping keep search results aligned with the latest information.
Can indexed documents be deleted through the API?
Yes. The API supports deletion of indexed documents that are no longer required, which helps prevent outdated content from remaining searchable.
What source types can use the SitecoreAI Ingestion Service API?
The API supports targeted additions, updates, and deletions across push, site, and content sources.
Why is the SitecoreAI Ingestion Service API important for enterprise search?
It gives enterprises direct control over search-index updates, reduces dependence on crawl schedules, enables faster synchronization, and supports automated integration with external systems.
Can the SitecoreAI Ingestion Service API support real-time or near-real-time search updates?
The API can support faster synchronization because external systems can push document changes directly instead of waiting for traditional crawling workflows. Actual update timing depends on the implementation and platform behavior.
What are common use cases for the SitecoreAI Ingestion Service API?
Common use cases include ecommerce catalogs, knowledge bases, customer portals, external CMS platforms, product data, frequently changing content, and event-driven enterprise search integrations.
