Stay AI

connect your stay ai subscription data to chord stay ai (formerly retextion) is the subscription management platform powering recurring billing, customer portals, and lifecycle automations for shopify subscription brands chord ingests subscription, order, and selling plan data from stay ai so you can model retention, churn, and lifetime value alongside the rest of your stack what chord ingests from stay ai chord pulls 3 datasets from your stay ai account subscriptions active and historical subscription records status, line items, cadence, next billing date, customer link orders subscription driven orders linked back to the originating subscription contract selling plan groups selling plan group definitions cadences, bundle configuration, product mappings generate a stay ai api key you'll need a stay ai api key from the merchant portal there are no scopes or permissions to configure, it's a single token that grants read access to the stay ai rest api heads up only users with admin access to the stay ai merchant portal can generate api keys if your role doesn't include it, ask an admin on the account to either generate the key for you or grant your user the permission first log in to the stay ai merchant portal in the left sidebar, go to settings → api keys click new api key name the key something recognizable, e g chord data sync in the api keys table, find the new row and click show in the private key column to reveal the key copy the key value heads up unlike most platforms, stay ai keeps the private key viewable after creation, you can return to settings → api keys and click show any time to see it again there's no "you only get one chance to copy it" moment connect the key in chord open chord hub and go to data sources → add source pick stay ai from the data source list paste the api key you just copied into the api key field click save chord makes a test call against the stay ai subscriptions 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 //api retextion com/api/v2/subscriptions 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? stay ai api keys don't have scopes, so a 401 means the key value itself is wrong, was revoked, or was copied with extra whitespace go back to settings → api keys in the stay ai portal, confirm the key is still listed and active, and either copy it again carefully or generate a new one paste the value into the same chord credential entry and test again do stay ai api keys expire? no keys stay valid until someone with portal admin access manually revokes them in settings → api keys if a previously working key suddenly fails, check that page first to confirm it's still listed and active how do i rotate the key? generate a new api key in stay ai, paste it into the same chord credential entry, and save chord uses the new key on the next scheduled sync once you've confirmed the new key validates and the next sync runs cleanly, delete the old key from stay ai who can see the key after it's saved in chord? the key value is encrypted at rest in chord hub and is never displayed back in the ui you can rotate or delete it any time, but you can't view the original value once it's saved why does the api host say retextion com ? stay ai was previously called retextion the product was rebranded but the underlying api host and authentication header ( x retextion access token ) still use the legacy name this is expected chord's connector handles the naming difference internally; you only ever interact with "stay ai" in the chord hub ui 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