Connecting a business
Nothing reaches a business’s books until someone who manages that business approves your platform in SYNC. You start the request; they finish it.
1. Ask SYNC to connect
From your server, for one of your accounts (your own id for it is external_tenant_id):
POST /v1/connections
{
"external_tenant_id": "acct_42",
"display_name": "Aloha Salon",
"owner_email": "owner@alohasalon.com",
"redirect_url": "https://yourapp.example/sync/back?state=..."
}SYNC answers with the connection, pending, and its authorize_url. Send the person there. redirect_url must be https; put anything you need to recognize them when they come back (a signed state, say) in its query, and SYNC keeps it.
2. They approve it in SYNC
Only someone signed in to SYNC with owner_email can approve, and only into a business they own or manage. They choose which business it is, then SYNC sends them to your redirect_url with connection_id and status=active added.
3. Check it and start posting
Read GET /v1/connections/{connection_id}: it should be active, for your external_tenant_id, and its entity_id is the business. Send that id as Vortex-Entity on every call for this business. The connection.activated webhook tells you the same thing.
One accounting system at a time
While a business is connected to SYNC, post its activity only to SYNC. SYNC allows one pending or active connection per account of yours (409 connection_existsotherwise): to start over, disconnect the old one with POST /v1/connections/{id}/disconnect.
Disconnecting and reconnecting
- Either side can disconnect. After that SYNC refuses calls for the business with
409 connection_inactive, and you getconnection.disconnected. What’s already in the books stays there. - If the same account of yours reconnects to the same business, it carries on where it left off: what you sent before is still found by its
external_idand invoice number, so you never send it again.
Next: post events.

