Overview, API References
Connect to an unlimited number of private content sources using the Enterprise Search APIs.
This overview will discuss:
Each API call requires an
access_token and a
access_token is your private API key. You'll need it to authenticate each request. Keep it secret!
content_source_key identifies which content source you'd like to reach with your request.
curl -X POST http://localhost:3002/api/v1/ent/sources/[CONTENT_SOURCE_KEY]/documents/bulk_create \ -H "Authorization: Bearer [ACCESS_TOKEN]" \ -H "Content-Type: application/json" \ -d ' ... '
Create a new Custom API Source or view the details of an existing Custom API Source to find these values.
access_token is shared amongst all connectors. But the
content_source_token is unique to each connector.
External IDs (external_id)
Each document within a content source must have a unique
Two documents in two separate content sources may have the same
You can update existing documents by issuing a POST request to an existing
external_id does not exist, a new document is created.
It is up to you to maintain the integrity of your
external_id for each document within each custom API content source.
We recommend that you avoid SHAs or any id derived from the content of a document.
Modification of original data will alter value, making it difficult to identify the document in the search index. This can lead to record duplication.