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 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 log in to your fairing dashboard (either directly at app fairing co or via your shopify store's apps section) click account in the navigation scroll to the api keys section (also labeled "api credentials" in some accounts) find the secret key row and click to unhide / reveal it copy the key value heads up the secret key stays viewable in the account page, you can return any time and click to reveal it again connect the key in chord open chord hub and go to data sources → add source pick fairing from the data source list paste the secret key you just copied into the api key field click save chord makes a test call against the fairing questions endpoint to confirm the key works 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 mailto\ help\@chord co with the exact error message we'll trace the request and tell you what's failing