> ## Documentation Index
> Fetch the complete documentation index at: https://docs.unstructured.io/llms.txt
> Use this file to discover all available pages before exploring further.
# MongoDB
First time creating a connector? [Read this first](/api-reference/workflow/connector-first-time-reqs).
Send processed data from Unstructured to MongoDB.
## Requirements
You will need:
The MongoDB requirements for a MongoDB Atlas deployment include:
For MongoDB Atlas, SCRAM-SHA-1 is not supported for authentication. This means that cluster types that only
include SCRAM-SHA-1, such as **Free**, **M0**, **Flex**, and **Serverless**, are **not** supported.
Unstructured only supports SCRAM-SHA-256 for MongoDB Atlas, which is cryptographically stronger than SCRAM-SHA-1.
If you try to test or use a connector that refers to a cluster type that only includes SCRAM-SHA-1, the
operation will fail, and you will get an error message similar to the following:
`[digital envelope routines] unsupported`.
* A MongoDB Atlas account. [Create an account](https://www.mongodb.com/cloud/atlas/register).
* A MongoDB Atlas cluster. [Create a cluster](https://www.mongodb.com/docs/atlas/tutorial/create-new-cluster/). Be sure to **not**
select a cluster type that only includes SCRAM-SHA-1, such as **Free**, **M0**, **Flex**, or **Serverless**.
* The cluster must be reachable from your application environment, for example by adding IP addresses to your IP access list. [Learn more](https://www.mongodb.com/docs/atlas/setup-cluster-security/#network-and-firewall-requirements).
* The cluster must be configured to allow IP address. [Learn how](https://www.mongodb.com/docs/atlas/security/ip-access-list/#add-ip-access-list-entries).
To get Unstructured's IP address ranges, go to
[https://assets.p6m.u10d.net/publicitems/ip-prefixes.json](https://assets.p6m.u10d.net/publicitems/ip-prefixes.json)
and allow all of the `ip_prefix` fields' values that are listed.
These IP address ranges are subject to change. You can always find the latest ones in the preceding file.
* The cluster must have at least one database. [Create a database](https://www.mongodb.com/docs/compass/current/databases/#create-a-database).
* The database must have at least one user, and that user must have sufficient access to the database. [Create a database user](https://www.mongodb.com/docs/atlas/security-add-mongodb-users/#add-database-users). [Give the user database access](https://www.mongodb.com/docs/manual/core/authorization/).
* The database must have at least one collection. [Create a collection](https://www.mongodb.com/docs/compass/current/collections/#create-a-collection).
For the destination connector, Unstructured recommends that all documents in the target collection have a field
named `record_id` with a `String` data type.
Unstructured can use this field to do intelligent document overwrites. Without this field, duplicate documents
might be written to the collection or, in some cases, the operation could fail altogether.
* The connection string for the cluster. For MongoDB Atlas, this connection string must include the protocol, username, password, host, and cluster name. For example:
```text theme={null}
mongodb+srv://:@/?retryWrites=true&w=majority&appName=
```
To get the connection string in MongoDB Atlas, do the following:
1. Log in to your MongoDB Atlas console.
2. In the sidebar, under **Databases**, click **Clusters**.
3. Click on the cluster you want to connect to.
4. Click **Connect**.
5. Click **Drivers**.
6. Under **Add your connection string into your application code**, copy the connection string.
You can then close the **Connect** dialog in MongoDB Atlas.
Before you use this connection string, be sure to fill in any placeholders in the string, such as your MongoDB Atlas database user's password value.
[Learn more](https://www.mongodb.com/resources/products/fundamentals/mongodb-connection-string).
## Examples
To create a MongoDB destination connector, see the following examples.
For more information on working with destination connectors using the Unstructured API, see [Destination endpoints](/api-reference/api/destination/destination-apis).
```python Python SDK theme={null}
import os
from unstructured_client import UnstructuredClient
from unstructured_client.models.operations import CreateDestinationRequest
from unstructured_client.models.shared import CreateDestinationConnector
with UnstructuredClient(api_key_auth=os.getenv("UNSTRUCTURED_API_KEY")) as client:
response = client.destinations.create_destination(
request=CreateDestinationRequest(
create_destination_connector=CreateDestinationConnector(
name="",
type="mongodb",
config={
"database": "",
"collection": "",
"uri": ""
}
)
)
)
print(response.destination_connector_information)
```
```bash curl theme={null}
curl --request 'POST' --location \
"$UNSTRUCTURED_API_URL/destinations" \
--header 'accept: application/json' \
--header "unstructured-api-key: $UNSTRUCTURED_API_KEY" \
--header 'content-type: application/json' \
--data \
'{
"name": "",
"type": "mongodb",
"config": {
"database": "",
"collection": "",
"uri": ""
}
}'
```
## Configuration settings
Replace the preceding placeholders as follows:
A unique name for this connector.
The name of the database on the target MongoDB instance.
The name of the collection within the database.
The instance connection string.
## Learn more
* [How to go from S3 to MongoDB with no code using Unstructured](https://unstructured.io/blog/how-to-go-from-s3-to-mongodb-with-no-code-using-unstructured)