sub claim containing your API Client ID.scope claim that includes api/access.publisher_id field in the request body for accuracy.Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
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.
Content successfully uploaded and processed.