If you’re new to Unstructured, read this note first.Before you can create a destination connector, you must first sign in to your Unstructured account:
- If you do not already have an Unstructured account, sign up for free. After you sign up, you are automatically signed in to your new Unstructured Let’s Go account, at https://platform.unstructured.io. To sign up for a Business account instead, contact Unstructured Sales, or learn more.
- If you already have an Unstructured Let’s Go, Pay-As-You-Go, or Business SaaS account and are not already signed in, sign in to your account at https://platform.unstructured.io. For other types of Business accounts, see your Unstructured account administrator for sign-in instructions, or email Unstructured Support at support@unstructured.io.
-
After you sign in to your Unstructured Let’s Go, Pay-As-You-Go, or Business account, click API Keys on the sidebar.
For a Business account, before you click API Keys, make sure you have selected the organizational workspace you want to create an API key for. Each API key works with one and only one organizational workspace. Learn more. -
Click Generate API Key.
-
Follow the on-screen instructions to finish generating the key.
-
Click the Copy icon next to your new key to add the key to your system’s clipboard. If you lose this key, simply return and click the Copy icon again.
Here are some more details about these requirements:
- The endpoint and API key for Azure AI Search. Create an endpoint and API key.
-
The name of the index in Azure AI Search. Create an index.
The Azure AI Search index that you use must have an index schema that is compatible with the schema of the documents that Unstructured produces for you. Unstructured cannot provide a schema that is guaranteed to work in all circumstances. This is because these schemas will vary based on your source files’ types; how you want Unstructured to partition, chunk, and generate embeddings; any custom post-processing code that you run; and other factors. You can adapt the following index schema example for your own needs. Be sure to replace
<number-of-dimensions>(in three locations in the following example) with the number of dimensions of the embedding model you are using:Therecord_id,element_id, andidfields are closely related, but each has a distinct purpose. Therecord_ididentifies the source document.- For S3 and Azure Blob connectors, the record ID is a Version 5 UUID generated from the namespace and file path of the document. This ensures that the ID is deterministic and unique at the file level.
- For all other blob connectors, the record ID is a Version 4 UUID representing a random 32-character hexadecimal string.
- For SQL connectors, the record ID is generated from the table name and record ID of the database table.
element_ididentifies the specific element. Source connectors generate element ID in one of the following ways, depending on the source connector:- A SHA-256 hash of the element’s text, its position on the page, the page number it’s on, and the name of the related file. This is to ensure that the ID is deterministic and unique at the file level.
- A Version 4 UUID generated using random numbers.
Each element from the same document contains that document’s record ID; this enables Unstructured to identify all the elements generated from a given document. If a source connector has been set to not reprocess all documents each time a workflow runs, Unstructured uses the record ID (along with the record version) to determine which documents are unchanged and should not be processed again. TheOlder connectors generate SHA-256 hashes for element IDs, while more modern connectors generate UUIDs. Going forward, older connectors will be converted to using UUIDs as well.idrepresents the actual row that Unstructured writes into the destination location. The ID is a Version 5 UUID generated from the namespace, element ID and record ID of the source document. The ID is deterministic and unique at the row level. Destination connectors process document updates in one of the following ways, depending on the connector:- Use the record ID to identify and delete all elements from a given document, prior to writing new elements from that document into the destination.
- Use the ID to perform upsert operations without generating duplicate rows, ensuring that reprocessing documents is idempotent.
<name>(required) - A unique name for this connector.<endpoint>(required) - The endpoint URL for Azure AI Search.<index>(required) - The name of the index for Azure AI Search.<key>(required) - The API key for Azure AI Search.

