Opensolr Changelog

Recent updates and improvements to the Opensolr platform.

API × Mar 2026 ×

API Mar 8, 2026

  • Improved The Data Ingestion API now returns a doc_ids array in every successful response, showing the auto-generated document ID (md5 of uri) for each document in your batch. Use these IDs to track, query, or update specific documents in your index.
  • Improved URI is now mandatory for every document in the Data Ingestion API. The document ID is always generated as md5(uri), making the URI the single source of truth for document identity. Same URI = same document. Resubmitting a URI updates the existing document. Duplicate URIs in pending jobs are automatically rejected to prevent accidental double-indexing.
  • New JSON file upload for the Data Ingestion API. Instead of embedding your documents in the request body, save your full payload as a .json file and upload it via the payload_file field. The file can contain everything — email, api_key, core_name, and documents — or just the documents array with auth as separate form fields. Ideal for large batches generated by CMS exports or data pipelines.
  • New Document extraction in the Data Ingestion API — add rtf:true to any document and point uri at a PDF, Word, Excel, PowerPoint, or OpenDocument file. Text is extracted automatically and indexed with full enrichment. Mix regular and RTF documents in the same batch.
  • New Data Ingestion API — push documents directly into your Opensolr index via POST. Submit up to 50 docs per batch with automatic vector embeddings, sentiment analysis, language detection, and all derived search fields. Works alongside the Web Crawler to push content it cannot reach: gated pages, CMS exports, product feeds. Same doc ID updates existing records.
  • New Global API rate limits are now enforced: 30 requests per minute and 500 per hour across all authenticated API endpoints. This applies to every API call including search, AI summaries, embeddings, and batch operations. If you need higher throughput for your integration, contact us and we will set custom limits for your account.

API Mar 3, 2026

  • New API rate limiting is now active. Every authenticated API request is tracked per user and per IP, with configurable limits per minute and per hour. If you exceed the threshold you will receive a 429 response with a Retry-After header — just back off and retry. Admin accounts are exempt. Individual users or IP addresses can also be given custom limits or blocked entirely. Monthly request counters are stored persistently so you can review your API usage over time.