> For the complete documentation index, see [llms.txt](https://docs.geoprismregistry.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geoprismregistry.com/readme/current/external-system-integration/4.2-register-and-synchronize-an-external-system/4.2.2-reveal.md).

# 4.2.2. Reveal

## 4.2.2.1. Registration

The following steps describe how to register a Reveal external system. A Reveal external system enables the ability to import Geo-Object data with identifiers from a Reveal system and to read data using the REST API that includes the Reveal external identifiers:

1. Navigate to the Settings page.
2. Find the External Systems section and click the **+** button to open the Registration modal.\\

   <figure><img src="https://lh5.googleusercontent.com/jmVBmNgM7kHdWwIYdhWRtaPTNQ0Cy-A6O3aNci116Nqz0T24LmxYB3-GeESnWQ2f9owjIzpOglFnBF5dEAxnvOIok_iAmRC7x4aRoy-P9HebnjfULI7kgFWPZB-5aMjdt2jrJ3iFVxMPi2wNOGQCGHdJkOPieJElOtlYQ6GRTNC9gDjVnbAfFrgUzA" alt=""><figcaption></figcaption></figure>
3. Select 'Reveal' from the *Type* dropdown and fill out the modal fields.\\

   <figure><img src="https://lh6.googleusercontent.com/ugUDp81o4BpD75gbVwD0Nt5UX_XmO84vCwfVW7P-SiGI-KBTC3N_4ZC_LE_pK6cudjCnIQyUP_QxwZ_cUEhD8dZyZWDqj4phsmDJLR_T-bSw3-9Qlil_Rpl-CoZtnLWZY0kQFaAB6UzuluDkpfiLQTfFXA0_xlRWoRLfgQy4c5ogkCGr1Jyfup6NyA" alt=""><figcaption></figcaption></figure>

| GPR data type | Appropriate Reveal value types                                                                                        | Required |
| ------------- | --------------------------------------------------------------------------------------------------------------------- | -------- |
| Type          | The type of external system.                                                                                          | Yes      |
| Organization  | The organization you belong to. An external system will only be available to data and users within this organization. | Yes      |
| ID            | The identifier for this external system.                                                                              | Yes      |
| Label         | The label of the external system.                                                                                     | Yes      |
| Description   | The description of the external system.                                                                               | No       |

## 4.2.2.2. Import

If Geo-Object data is already present in a Reveal instance, it must first be imported to GeoPrism Registry using the ‘Import from an external system’ option in the Import module after the Reveal external system has been registered (see [section 6.5.1.1](/readme/current/geoprism-registry-tutorial/6.5-content-management/6.5.1-lists-and-spatial-data/6.5.1.1-import.md)). Uploading data from a Reveal system in this way stores the identifiers from the Reveal system data on the Geo-Objects that are imported/created in GeoPrism Registry. These Reveal identifiers will be used during synchronization to match GeoPrism Registry Geo-Objects with data in Reveal.

## 4.2.2.3. Synchronization

The Reveal external system registration enables the GeoPrism Registry REST API to be used to query Geo-Objects with Reveal identifiers in a Reveal format. Reveal external systems do not have a configurable interface for pushing data like DHIS2 systems, but automated synchronizations could be made with external programs that utilize the GeoPrism Registry REST API.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.geoprismregistry.com/readme/current/external-system-integration/4.2-register-and-synchronize-an-external-system/4.2.2-reveal.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.