# Destination

#### CCA

Name of the config key store key containing the url for the CCA API.

```
${DBKS:CCA_URL}
```

#### CCA repository (leave empty for default)

Name of the repository to fetch data from, leave empty if editorial is to be used.

#### LCC

Enter the provider information from [Content-Agent](https://docs.navigaglobal.com/content-agent/)

| Key        | Type   | Description                                                          |
| ---------- | ------ | -------------------------------------------------------------------- |
| ocProvider | string | Enter the named open content provider from Content Agent to customer |

```
{
    "ocProvider": "${DBKS:CA_PROVIDER}"
}
```

#### OC Property mappings

An object containing properties to match against the customer OC

| Key             | Type   | Description                         |
| --------------- | ------ | ----------------------------------- |
| uuid            | string | UUID of the article                 |
| externalUUID    | string | The imported UUID of the article    |
| externalVersion | string | The imported version of the article |
| creator         | string | The creator of the article          |
| channels        | string | The article's meta channels         |
| created         | string | The created field                   |

Example:

```
{
    "uuid": "uuid",
    "externalUUID": "ExternalUUID",
    "externalVersion": "ExternalVersion",
    "creator": "ObjectCreator",
    "channels": "ArticleMetaChannels",
    "created": "created"
}
```

[**Here you will find examples**](https://docs.navigaglobal.com/naviga-wire/2.1.0-7/admin-guide/configuration/providers/icp-configuration-examples) of how to write the functions for Wire ICP Configuration for IMEngine.

#### QS properties

This is an array with string with properties to match the properties to search in for the query streamer.\
They should match the properties that are set as the free text search in Wire open content.

Example:

```
[
    "ArticleBody",
    "ArticleMetaChannels",
    "ArticleMetaNewsValue",
    "ArticleMetaSections",
    "Name",
    "Text",
    "WriterAuthors",
    "WriterHeadlines"
]
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.navigaglobal.com/naviga-wire/2.1.0-7/admin-guide/configuration/providers/destination.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.