article Setting Up Your Account as a Reseller in Billing & Pricing

article Setting Up Your Account as a Reseller in Billing & Pricing https://community.sinch.com/t5/Billing-Pricing/Setting-Up-Your-Account-as-a-Reseller/ta-p/19829 <DIV class="lia-message-template-content-zone lia-indent-padding-left-30px"> <P><I><SPAN data-contrast="none">How to structure your Sinch account so you can easily and securely onboard, isolate, and bill your own end-customers.</SPAN></I><SPAN data-ccp-props="{"201341983":0,"335559739":160,"335559740":276}"> </SPAN></P> <H2 aria-level="2"> </H2> <H2 aria-level="2"><STRONG><SPAN data-contrast="none">Overview</SPAN></STRONG><SPAN data-ccp-props="{"335559738":320,"335559739":160}"> </SPAN></H2> <P><SPAN data-contrast="none">If you resell Sinch products to your own customers, you're what we call a reseller, or an ISV (Independent Software Vendor). This guide walks you through the recommended way to structure your Sinch account so that each of your end-customers is properly isolated, easy to bill, and simple to manage as you grow.</SPAN><SPAN data-ccp-props="{"201341983":0,"335559739":160,"335559740":276}"> </SPAN></P> <P> </P> <P><SPAN data-contrast="none">This guide assumes you already have a Sinch account. If you don't, you can sign up for free </SPAN><A href="https://dashboard.sinch.com/signup/" target="_blank" rel="noopener"><SPAN data-contrast="none">here</SPAN></A><SPAN data-contrast="none">. For additional help creating your account, </SPAN><A href="https://support.sinch.com/hc/en-us/articles/53501378504467-How-to-sign-up-for-your-free-Sinch-account" target="_blank" rel="noopener"><SPAN data-contrast="none">read our guide</SPAN></A><SPAN data-contrast="none"> or reach out to support.</SPAN><SPAN data-ccp-props="{"201341983":0,"335559739":160,"335559740":276}"> </SPAN></P> <H2 aria-level="2"> </H2> <H2 aria-level="2"><STRONG><SPAN data-contrast="none">Understanding Hierarchy: Accounts, Projects, and Subprojects</SPAN></STRONG><SPAN data-ccp-props="{"335559738":320,"335559739":160}"> </SPAN></H2> <STRONG><SPAN data-contrast="none">Sinch organizes resources in a three-level hierarchy: </SPAN></STRONG><SPAN data-contrast="none">Account → Project → Subproject.</SPAN><SPAN data-ccp-props="{"201341983":0,"335559739":160,"335559740":276}"> </SPAN> <UL> <LI><STRONG><SPAN data-contrast="none">Account:</SPAN></STRONG><SPAN data-contrast="none"> your overarching Sinch relationship. Billing and top-level access are managed here.</SPAN></LI> <LI data-aria-level="1" data-aria-posinset="1" data-list-defn-props="{"335552541":1,"335559685":460,"335559991":260,"469769242":[8226],"469777803":"left","469777804":"•","469777815":"hybridMultilevel"}" data-listid="2" data-font="" data-leveltext="•" aria-setsize="-1"><STRONG><SPAN data-contrast="none">Project:</SPAN></STRONG><SPAN data-contrast="none"> a workspace under your account used to separate resources, e.g. by team or environment. Every account has at least one.</SPAN><SPAN data-ccp-props="{"201341983":0,"335559739":80,"335559740":276}"> </SPAN></LI> <LI data-aria-level="1" data-aria-posinset="1" data-list-defn-props="{"335552541":1,"335559685":460,"335559991":260,"469769242":[8226],"469777803":"left","469777804":"•","469777815":"hybridMultilevel"}" data-listid="2" data-font="" data-leveltext="•" aria-setsize="-1"><STRONG><SPAN data-contrast="none">Subproject:</SPAN></STRONG><SPAN data-contrast="none"> a workspace inside a project. It behaves like a project (own apps, own contacts), but its usage rolls up to its parent project for billing.</SPAN><SPAN data-ccp-props="{"201341983":0,"335559739":80,"335559740":276}"> </SPAN></LI> </UL> <P><SPAN data-contrast="none">If you'd like the full picture of how this hierarchy works, see our article on the </SPAN><A href="https://community.sinch.com/t5/Billing-Pricing/Sinch-Account-Model/ta-p/9375" target="_blank" rel="noopener"><SPAN data-contrast="none">Sinch Account Model</SPAN></A><SPAN data-contrast="none">.</SPAN><SPAN data-ccp-props="{"201341983":0,"335559739":160,"335559740":276}"> </SPAN></P> <H2 aria-level="2"> </H2> <H2 aria-level="2"><STRONG><SPAN data-contrast="none">How to set up your account as a reseller</SPAN></STRONG><SPAN data-ccp-props="{"335559738":320,"335559739":160}"> </SPAN></H2> <P><STRONG><SPAN data-contrast="none">As a reseller, you should use one Subproject for each of your end-customers.</SPAN></STRONG><SPAN data-ccp-props="{"335559739":80}"> </SPAN></P> <P><SPAN data-contrast="none">This keeps every end-customer's numbers, apps, and traffic separate from every other end-customer's, while still rolling everything up into a single account you manage and get billed on.</SPAN><SPAN data-ccp-props="{"335559739":80}"> </SPAN></P> <P aria-level="3"> </P> <P aria-level="3"><STRONG><SPAN data-contrast="none">Setup:</SPAN></STRONG><SPAN data-ccp-props="{"335559738":240,"335559739":120}"> </SPAN></P> <OL> <LI data-aria-level="1" data-aria-posinset="1" data-list-defn-props="{"335552541":0,"335559685":460,"335559991":260,"469769242":[65533,0],"469777803":"left","469777804":"%1.","469777815":"hybridMultilevel"}" data-listid="1" data-font="" data-leveltext="%1." aria-setsize="-1"><SPAN data-contrast="none">Create a dedicated parent project within your account (named, for example, “End-Customer Accounts”).</SPAN></LI> <LI data-aria-level="1" data-aria-posinset="1" data-list-defn-props="{"335552541":0,"335559685":460,"335559991":260,"469769242":[65533,0],"469777803":"left","469777804":"%1.","469777815":"hybridMultilevel"}" data-listid="1" data-font="" data-leveltext="%1." aria-setsize="-1"><SPAN data-contrast="none">Under that parent project, create one subproject for every individual end-customer you bring on board.</SPAN><SPAN data-ccp-props="{"201341983":0,"335559739":80,"335559740":276}"> </SPAN></LI> </OL> <P><SPAN data-contrast="none">You can create your first few subprojects directly from the Build dashboard. If you plan to onboard end-customers at scale, see the section on API automation below.</SPAN><SPAN data-ccp-props="{"201341983":0,"335559739":160,"335559740":276}"> </SPAN></P> <P> </P> <P><SPAN data-contrast="none">Multiple projects should be used to group different customers as appropriate – for example by region/currency.</SPAN><SPAN data-ccp-props="{"201341983":0,"335559739":160,"335559740":276}"> </SPAN></P> <P> </P> <span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Jannic_Nielsen_0-1787124916568.png" style="width: 596px;"><img src="https://community.sinch.com/t5/image/serverpage/image-id/7473iEF209930B9478871/image-dimensions/596x225?v=v2" width="596" height="225" role="button" title="Jannic_Nielsen_0-1787124916568.png" alt="Jannic_Nielsen_0-1787124916568.png" /><span class="lia-inline-image-caption" onclick="event.preventDefault();">Jannic_Nielsen_0-1787124916568.png</span></span> <H3 aria-level="3"> </H3> <H3 aria-level="3"><STRONG><SPAN data-contrast="none">Why this structure is recommended for resellers</SPAN></STRONG><SPAN data-ccp-props="{"335559738":240,"335559739":120}"> </SPAN></H3> <UL> <LI aria-level="3"><STRONG><SPAN data-contrast="none">Automation.</SPAN></STRONG><SPAN data-contrast="none"> Subprojects can be created, configured, and managed via the Subproject API, so you can onboard new end-customers without manual work in the dashboard.</SPAN><SPAN data-ccp-props="{"201341983":0,"335559739":80,"335559740":276}"> </SPAN></LI> <LI aria-level="3"><STRONG><SPAN data-contrast="none">Security and isolation.</SPAN></STRONG><SPAN data-contrast="none"> This structure keeps your end-customers' resources separate from one another, and keeps them out of your main Build dashboard entirely.</SPAN><SPAN data-ccp-props="{"201341983":0,"335559739":80,"335559740":276}"> </SPAN></LI> <LI aria-level="3"><STRONG><SPAN data-contrast="none">Cost tracking.</SPAN></STRONG><SPAN data-contrast="none"> Because each end-customer sits in their own subproject, you can pull granular cost reports for each of your clients.</SPAN><SPAN data-ccp-props="{"201341983":0,"335559739":80,"335559740":276}"> </SPAN></LI> <LI aria-level="3"><STRONG><SPAN data-contrast="none">Per-end-customer invoice detail.</SPAN></STRONG><SPAN data-contrast="none"> Sinch supports usage slicing by subproject within a single invoice for supported messaging channels, so you get one consolidated invoice that itemizes traffic by end-customer, rather than a separate invoice per client.</SPAN><SPAN data-ccp-props="{"201341983":0,"335559739":80,"335559740":276}"> </SPAN></LI> </UL> <H3 aria-level="3"> </H3> <H3 aria-level="3"><STRONG><SPAN data-contrast="none">Setting up API automation</SPAN></STRONG><SPAN data-ccp-props="{"335559738":240,"335559739":120}"> </SPAN></H3> <P><SPAN data-contrast="none">To create and manage subprojects programmatically, your account needs to be enabled for the </SPAN><A href="https://developers.sinch.com/docs/subprojects/api-reference/subprojects" target="_blank" rel="noopener"><SPAN data-contrast="none">Subproject API</SPAN></A><SPAN data-contrast="none">. This isn't switched on by default.</SPAN><SPAN data-ccp-props="{"201341983":0,"335559739":160,"335559740":276}"> </SPAN></P> <UL> <LI><SPAN data-contrast="none">Contact your Sinch account manager and ask them to enable </SPAN><A href="https://developers.sinch.com/docs/subprojects/api-reference/subprojects" target="_blank" rel="noopener"><SPAN data-contrast="none">Subproject API</SPAN></A><SPAN data-contrast="none"> access for your account.</SPAN><SPAN data-ccp-props="{"201341983":0,"335559739":80,"335559740":276}"> </SPAN></LI> <LI><SPAN data-contrast="none">Once enabled, you can create, configure, and delete subprojects entirely through the API, without needing dashboard access for each end-customer.</SPAN><SPAN data-ccp-props="{"201341983":0,"335559739":80,"335559740":276}"> </SPAN></LI> </UL> <H3 aria-level="3"> </H3> <H3 aria-level="3"><STRONG><SPAN data-contrast="none">Giving your end-customers access</SPAN></STRONG><SPAN data-ccp-props="{"335559738":240,"335559739":120}"> </SPAN></H3> <P><SPAN data-contrast="none">Your end-customers should </SPAN><STRONG><SPAN data-contrast="none">not</SPAN></STRONG><SPAN data-contrast="none"> be invited into the Sinch Build dashboard. Instead, issue each end-customer's integration a scoped API key tied to their subproject. This keeps them isolated from your other clients and from your own account settings, while still giving them everything they need to integrate.</SPAN><SPAN data-ccp-props="{"201341983":0,"335559739":160,"335559740":276}"> </SPAN></P> <H2 aria-level="2"> </H2> <H2 aria-level="2"><STRONG><SPAN data-contrast="none">Things to know before you start</SPAN></STRONG><SPAN data-ccp-props="{"335559738":320,"335559739":160}"> </SPAN></H2> <P><SPAN data-contrast="none">A few current platform behaviors are worth planning around before you build out your reseller structure.</SPAN><SPAN data-ccp-props="{"201341983":0,"335559739":160,"335559740":276}"> </SPAN></P> <H3 aria-level="3"> </H3> <H3 aria-level="3"><STRONG><SPAN data-contrast="none">Plan your billing structure before you go live</SPAN></STRONG><SPAN data-ccp-props="{"335559738":240,"335559739":120}"> </SPAN></H3> <P><SPAN data-contrast="none">Your account, billing, and project layout should be designed upfront with your account manager. Moving a project between billing setups after you're live can disrupt invoicing and reporting, so it isn't something to plan on doing later. As a rule of thumb: one billing setup per cost centre or currency, and one project per team or environment.</SPAN><SPAN data-ccp-props="{"201341983":0,"335559739":160,"335559740":276}"> </SPAN></P> <H2 aria-level="2"> </H2> <H2 aria-level="2"><STRONG><SPAN data-contrast="none">Frequently asked questions</SPAN></STRONG><SPAN data-ccp-props="{"335559738":320,"335559739":160}"> </SPAN></H2> <P aria-level="3"><STRONG><SPAN data-contrast="none">Can I create projects via the API?</SPAN></STRONG><SPAN data-ccp-props="{"335559738":240,"335559739":120}"> </SPAN></P> <P><SPAN data-contrast="none">No. Projects are created in the Build dashboard, and should only be needed for basic account structure. Subprojects are the automation layer: you can create, manage, and delete these fully via the API.</SPAN><SPAN data-ccp-props="{"201341983":0,"335559739":160,"335559740":276}"> </SPAN></P> <P aria-level="3"><STRONG><SPAN data-contrast="none">Can I delete a project myself?</SPAN></STRONG><SPAN data-ccp-props="{"335559738":240,"335559739":120}"> </SPAN></P> <P><SPAN data-contrast="none">Not yet. Today you should reach out to Support so we can remove/consolidate provisioned products and cost reporting on our side. </SPAN><SPAN data-ccp-props="{"201341983":0,"335559739":160,"335559740":276}"> </SPAN></P> <P aria-level="3"><STRONG><SPAN data-contrast="none">Can I delete a subproject myself?</SPAN></STRONG><SPAN data-ccp-props="{"335559738":240,"335559739":120}"> </SPAN></P> <P><SPAN data-contrast="none">Yes, programmatically via the API.</SPAN><SPAN data-ccp-props="{"201341983":0,"335559739":160,"335559740":276}"> </SPAN></P> <P aria-level="3"><STRONG><SPAN data-contrast="none">Should my end-customers get access to the Sinch Build dashboard?</SPAN></STRONG><SPAN data-ccp-props="{"335559738":240,"335559739":120}"> </SPAN></P> <P><SPAN data-contrast="none">No. The subproject-plus-scoped-API-key model exists specifically so your end-customers never need dashboard access. This is what keeps them properly isolated from each other, and from your account.</SPAN><SPAN data-ccp-props="{"201341983":0,"335559739":160,"335559740":276}"> </SPAN></P> <P aria-level="3"><STRONG><SPAN data-contrast="none">Can I get a reliable cost breakdown per end-customer?</SPAN></STRONG><SPAN data-ccp-props="{"335559738":240,"335559739":120}"> </SPAN></P> <P><SPAN data-contrast="none">Yes. Cost breakdown by subproject is fully supported and is the recommended way to re-bill your own clients accurately.</SPAN><SPAN data-ccp-props="{"201341983":0,"335559739":160,"335559740":276}"> </SPAN></P> <P aria-level="3"><STRONG><SPAN data-contrast="none">Can I invoice different parts of my business in different currencies?</SPAN></STRONG><SPAN data-ccp-props="{"335559738":240,"335559739":120}"> </SPAN></P> <P><SPAN data-contrast="none">Yes. You can have multiple billing accounts under the same Sinch account, for example one per cost center or currency. Talk to your account manager to set this up.</SPAN><SPAN data-ccp-props="{"201341983":0,"335559739":160,"335559740":276}"> </SPAN></P> <P aria-level="3"><STRONG><SPAN data-contrast="none">My use case doesn't fit any of this. Who do I talk to?</SPAN></STRONG><SPAN data-ccp-props="{"335559738":240,"335559739":120}"> </SPAN></P> <P><SPAN data-contrast="none">Reach out to your Sinch account manager or Sinch Support. They can advise on more complex account structures.</SPAN><SPAN data-ccp-props="{"201341983":0,"335559739":160,"335559740":276}"> </SPAN></P> </DIV> Wed, 19 Aug 2026 07:48:36 GMT Jannic_Nielsen 2026-08-19T07:48:36Z Setting Up Your Account as a Reseller https://community.sinch.com/t5/Billing-Pricing/Setting-Up-Your-Account-as-a-Reseller/ta-p/19829 <P>Setting Up Your Account as a Reseller</P> Wed, 19 Aug 2026 07:48:36 GMT https://community.sinch.com/t5/Billing-Pricing/Setting-Up-Your-Account-as-a-Reseller/ta-p/19829 Jannic_Nielsen 2026-08-19T07:48:36Z