SONDTRE Connect
Open ConnectGetting started
- Register a public HTTPS website in your business's Connect workspace.
- Add the unique verification code as a TXT record at
_sondtre.YOUR_WEBSITE_HOST, then verify ownership. - Install the generated script for a domain-bound heartbeat and optional existing receptionist/booking widget.
- For data sync, generate a scoped key and send events from your website server.
Domain verification uses DNS only; SONDTRE does not fetch user-supplied website addresses. A public site ID is not a secret and does not authorize private data. Browser-origin checks protect installation routing, not user identity. Private imports require server authentication. No analytics cookies or automatic visitor tracking are installed.
JavaScript installation
<script src="https://sondtre.com/api/public/connect/script.js" data-sondtre-site="YOUR_PUBLIC_SITE_ID" async></script>
Shopify
Online Store → Themes → Edit code → theme.liquid. Paste before </head>. Checkout requires Shopify's supported extensions; this script does not import orders.
WordPress
Use your site's header-code plugin or theme header. Paste the script before </head>.
WooCommerce
Install in the WordPress header. For sales, send signed server-side events from a reviewed WooCommerce integration.
Wix
Settings → Custom Code → Add Custom Code → Head → All pages. A plan supporting custom code is required.
Squarespace
Settings → Advanced → Code Injection → Header. Your plan must support code injection.
Webflow
Site settings → Custom code → Head code. Save and publish your site.
BigCommerce
Storefront → Script Manager → Create script. Choose Head and All pages.
Universal
Paste the script into your website header or supported custom-code section, then publish.
Custom website
Add the script to your HTML document or framework's supported script loader. It works independently of the framework.
Authentication & key management
Use Authorization: Bearer YOUR_SERVER_KEY. Keys are shown once, stored as hashes and bound to one website, its business and the issuing active owner. Revoke in Connect. Rotate by creating a replacement, deploying it on your server, then revoking the old key.
Requests carrying an Origin header are rejected: do not call these APIs from a browser. Revocation, disconnected websites, unverified domains, inactive owners and expired subscriptions block imports. Financial scopes should only be granted to trusted payment systems; these are website-reported payments, not independently provider-verified transactions.
REST events API
POST https://sondtre.com/api/public/connect/events
curl https://sondtre.com/api/public/connect/events \
-H 'Authorization: Bearer YOUR_SERVER_KEY' \
-H 'Content-Type: application/json' \
--data '{"type":"customers","externalId":"customer-123",
"requestId":"YOUR_UNIQUE_UUID",
"record":{"name":"Customer name","email":"customer@yourbusiness.com"}}'Every event requires type, externalId, a UUID requestId, and record. Extra fields are rejected. Request retries return the original record; reusing a request ID with changed content fails. Update a nonfinancial record with the same external ID and a new request ID.
| Scope / type | Record fields |
|---|---|
| customers | name; optional phone, email, address, notes |
| leads | name; optional phone, email, service, message |
| products | name, sku, priceCents, currency (USD). New stock starts at 0. |
| orders | number, recipient (name, street1, city, state, zip, country), items (name, quantity, price_cents); optional customerExternalId. No fulfillment changes or implied payments. |
| appointments | customerName, phone, service, startsAt, endsAt (ISO with timezone), status (booked/completed/cancelled); optional email, customerExternalId. Existing capacity rules apply. |
| inventory | productExternalId, quantity (absolute nonnegative snapshot). Product must exist. Changes enter the stock ledger. |
| revenue | kind (revenue/refund), amountCents (including tax), salesTaxCents, currency (USD), paymentStatus (completed), unique paymentReference, occurredAt; optional description. Financial events are immutable; refunds are separate events. |
| events | name, path. Saves event receipt metadata, not arbitrary visitor/customer data. |
Sync customer/product references first. Maximum body 64 KB, 100 order items, 120 requests/minute per request source. Monetary amounts use integer cents. Collected sales tax is separate from income; unpaid orders never inflate totals. Existing platform imports must not send the same payment again under a different source.
Signed inbound webhooks
POST https://sondtre.com/api/public/connect/webhook, same event format and bearer key. Send X-SONDTRE-Timestamp (Unix seconds) and X-SONDTRE-Signature (lowercase hex HMAC-SHA256 using the server key over timestamp.rawBody). Sign the exact transmitted body; timestamps expire after five minutes. Durable request IDs protect replay.
// Website server only
const timestamp = String(Math.floor(Date.now() / 1000));
const body = JSON.stringify(event);
const signature = createHmac('sha256', process.env.SONDTRE_KEY)
.update(timestamp + '.' + body).digest('hex');This is SONDTRE's custom event protocol, not a substitute for verifying Stripe, Shopify or other provider signatures in a native adapter. Outbound webhooks are not implemented.
Errors & recovery
- 400 invalid_event: validate required fields and formats.
- 401 invalid_credential / invalid_signature / expired_signature: replace revoked keys or regenerate the signature.
- 403 scope_denied / authorization_inactive: check owner, domain, key scopes and subscription.
- 409 sync_rejected: fix missing references, booking conflicts or duplicate payment IDs. Retry with the original request ID and unchanged content.
- 413 payload_too_large: split requests.
- 429 rate_limited: back off at least one minute.
Disconnect revokes all keys without deleting imported records. Reconnect requires renewed domain verification and new credentials. Test connection checks actual DNS verification and shows saved script/sync evidence separately; it never certifies untested data imports.
Supported integrations
Universal script and server-event methods are platform-independent. Shopify, WordPress, WooCommerce, Wix, Squarespace, Webflow and BigCommerce installation instructions are provided. Native OAuth adapters and automatic platform pulls are not verified or activated by this feature; each needs official credentials, provider permissions and a successful business-specific synchronization test.