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

# Fairing

Connect your Fairing survey data to Chord. Fairing is the post-purchase survey platform that captures attribution, demographic, and intent signals from customers right after checkout. Chord ingests the full question catalog and every response so you can model attribution channels, NPS, and post-purchase intent alongside the rest of your stack.

## What Chord ingests from Fairing

Chord pulls 2 datasets from your Fairing account. Each dataset becomes its own table in your Chord Snowflake schema.

* **Questions:** every question in your active question stream: id, type, prompt, response options, randomization settings, customer type, frequency, publish timestamps.
* **Responses:** every customer response captured by Fairing: order id, question id, response text, customer id and email, coupon code if applied, UTM source/medium/campaign, and order creation timestamp.

## Generate a Fairing API key

You'll need your Fairing Secret Key from the dashboard. There are no scopes or permissions to configure, it's a single key that grants read access to the Fairing REST API.

{% hint style="warning" %}
**Heads up:** only users with access to the Fairing **Account** page can view or generate API keys. If your role doesn't include it, ask an admin on the account to either retrieve the key for you or grant your user access.
{% endhint %}

1. Log in to your Fairing dashboard (either directly at app.fairing.co or via your Shopify store's Apps section).
2. Click **Account** in the navigation.
3. Scroll to the **API Keys** section (also labeled "API Credentials" in some accounts).
4. Find the **Secret Key** row and click to unhide / reveal it.
5. Copy the key value.

## Connect the key in Chord

1. Open Chord Hub and go to **Data Sources → Add Source**.
2. Pick **Fairing** from the data source list.
3. Paste the Secret Key you just copied into the **API Key** field.
4. Click **Save.** Chord makes a test call against the Fairing questions endpoint to confirm the key works.
5. The first sync kicks off automatically; subsequent syncs run on your tenant's standard ingestion schedule.

## Troubleshooting

**What does the validate step actually check?** Chord makes a small read against `https://app.fairing.co/api/questions` and confirms the key returns a 200 response with no authorization error. It does not pull or store any records — that happens on the first scheduled sync after you save the credential.

**The validate step failed. What now?** Fairing keys don't have scopes, so a 401 means the key value itself is wrong, was rotated, or was copied with extra whitespace (a common issue when copying from a hidden field). Go back to **Account → API Keys** in Fairing, reveal the Secret Key, copy it again carefully, paste it into the same Chord credential entry, and test again.

**Do Fairing API keys expire?** No. Keys stay valid until someone with Account access manually rotates them in **Account → API Keys**. If a previously working key suddenly fails, check that page first.

**How do I rotate the key?** Generate a new Secret Key in Fairing's Account page (or ask Fairing support to rotate yours if your dashboard doesn't expose the regenerate option), paste it into the same Chord credential entry, and save. Chord uses the new key on the next scheduled sync.

***

**Need help?** If you hit a credential or connectivity issue you can't resolve, reach out to <help@chord.co> with the exact error message. We'll trace the request and tell you what's failing.


---

# 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.chord.co/connect-sources/data-sources/connect-data-sources/fairing.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.