Wikit Semantics JSON API Connector
Connector Configuration
Thanks to the integration between Wikit Semantics and your webhook, your Wikit Semantics app allows your users to leverage content from knowledge bases, document spaces, etc. The connector synchronizes content returned by webhooks and REST endpoints in Wikit Semantics JSON format to a Wikit Semantics data source.
| Field name | Format / Type | Required | Comment |
|---|---|---|---|
| Webhook URL | URL | ✅ | URL of the REST endpoint returning content in Wikit Semantics JSON format |
Authorization HTTP header | Free text / Token | ➖ | Authorization header sent when calling the webhook (for example: Basic <encoded-secret> or Bearer <jwt-token>) |
💡 Fields marked ✅ are required for the connector to work.
How the Connector Works
This format describes documents along with their fragmented content (chunks) according to a de facto standard for the Wikit Semantics solution.
Example JSON payload:
json
[
{
"@context": "https://wikit.ai",
"@type": "Document",
"identifier": "document-1",
"title": "My Document",
"url": "https://example.com/document-1",
"dateModified": "2025-05-13T00:00:00.000Z",
"hasPart": [
{
"@type": "DocumentChunk",
"text": "# Introduction This is the first paragraph."
},
{
"@type": "DocumentChunk",
"text": "# Chapter 1 Content of chapter 1."
},
{ "@type": "DocumentChunk", "text": "# Conclusion Final summary." }
]
},
{
"@context": "https://wikit.ai",
"@type": "Document",
"identifier": "document-2",
"title": "My second Document",
"url": "https://example.com/document-2",
"dateModified": "2025-05-13T00:00:00.000Z",
"hasPart": [
{ "@type": "DocumentChunk", "text": "This is a short document." }
]
}
]To note for the synchronization to work properly:
- The
identifier,dateModified, andhasPartfields are essential for synchronization. The last modification date is used to replace documents updated since the previous synchronization performed by the connector. - The
titleandurlfields are recommended for better use of the content within Wikit Semantics Chat.