> For the complete documentation index, see [llms.txt](https://docs.secoda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.secoda.co/integrations/data-pipeline-tools/census.md).

# Census

An overview of the Census integration with Secoda

<details>

<summary>Getting Started with Census</summary>

There are two steps to get started using Census with Secoda:

1. Retrieve your Census API key and Host
2. Connect Census to Secoda

</details>

<details>

<summary>1. Retrieve your Census API key and Host</summary>

1. Open up [Census](https://getcensus.com) and login
2. Go to **Settings -> General -> API Access**
3. Copy the API Key
4. Copy the [Base URL](https://developers.getcensus.com/api-reference/introduction/overview#base-urls) of your Census workspace, i.e, <https://app.getcensus.com>

</details>

<details>

<summary>2. Connect Census to Secoda</summary>

After retrieving the API key and host, the next step is to connect Secoda:

1. In the Secoda App, select **Add Integration** page on the Integrations page
2. Search for and select "Census"
3. Enter your API key and host
4. Click **Connect**
5. After the extraction is complete your **Census** Syncs will be in Secoda

</details>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.secoda.co/integrations/data-pipeline-tools/census.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.