Real-time ingestion
Real-time ingestion.
Documentation Index
Fetch the complete documentation index at: https://docs.gloo.com/llms.txt
Use this file to discover all available pages before exploring further.
Authentication
The API requires a JWT token with specific claims to authorize access. The token must be associated with a Client ID that has access to the specified publisher. The system validates that the organization associated with your Client ID has permission to access the publisher specified in your request.JWT Token Requirements
Your JWT must include the following claims:- A
subclaim containing your API Client ID. - A
scopeclaim that includesapi/access.
publisher_id field in the request body for accuracy.Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
The request body should be a JSON object with the following structure:
UUID of the publisher associated with the content. This must be associated with your organization.
The actual text content to be ingested and chunked.
Custom filename for this content.
Content type (e.g., article, blog, tutorial).
Title of the content item.
Subtitle of the content item.
Brief summary of the content.
URL to image associated with the content.
URL to the original content.
URL to a file associated with the content.
Identifying number for the content item.
Additional information about the content item.
Tags associated with the content (can be array or comma-separated string).
Author(s) of the content (can be array or comma-separated string).
ISBN if content is from a book.
Date when the content was published (recommended format: YYYY-MM-DD).
ID of the content producer.
Religious tradition (if applicable).
Publication type.
URL where the content is hosted.
Number of pages (for documents).
Duration (for audio/video content).
Title for level 2 heading/section.
Subtitle for level 2 heading/section.
Image URL for level 2 heading/section.
URL for level 2 heading/section.
File URL for level 2 heading/section.
Summary for level 2 heading/section.
Number for level 2 heading/section.
Additional info for level 2 heading/section.
Title for level 3 heading/section.
Subtitle for level 3 heading/section.
Image URL for level 3 heading/section.
URL for level 3 heading/section.
File URL for level 3 heading/section.
Summary for level 3 heading/section.
Response
Content successfully uploaded and processed.

