Sinch Community

Accounts   Your Sinch account is created when you sign up in the Sinch Build Dashboard. It represents the relationship between your business and Sinch and ties together all your Sinch services.   The account resource forms the root of the resource hierarchy that relates to your business. In short, a Sinch account: Represents your relationship with Sinch Is the root of your resource hierarchy.     Billing Accounts   When you use Sinch services, you will be incurring charges to a billing account. Billing accounts maintain your account balance and contain your payment information such as name, address, currency type, and tax ID.   A Sinch account may have multiple billing account resources to control how the usage of Sinch services gets billed. This is done by linking the billing account to the projects you want it to pay for. Reach out to your Sinch Account Manager if you need help setting this up.   Billing accounts exist in two flavors: prepaid and postpaid. Prepaid billing accounts maintain an account balance that you can easily top up using your preferred billing method. Postpaid billing accounts are paid via invoice.   In short, a billing account: Collects charges for all different Sinch products and maintains your account balance Controls how other resources are billed Stores payment information such as name, address, currency type, and tax ID for your business.   Learn more about how the Sinch account model works. ... View more

No. Subprojects are tied to parent projects. Each parent project connects back to the billing information on your Sinch account.   Learn more about the Sinch account model. ... View more

Not for subprojects. With subprojects being tied to a project (a.k.a. parent project), that means the project determines billing.   Though, you can have separate billing accounts for projects. Contact your Account Manager  to get multiple billing accounts for projects. ... View more

Subprojects are a great way to keep ASP business relationships organized.   One project can have many subprojects, each with a separately tracked ID. Once a project has subprojects under it, it becomes known as a parent project. The parent project will handle payment for all subprojects, yet each subproject will have its own unique set of data tied back to your customer.     You can create a new subproject for each customer. And should they leave, it’s as easy as deleting the subproject!   Follow our Subprojects API getting started documentation to start organizing today. ... View more

No. A Subproject is strictly tied to a single parent Project.    Within the Sinch Account Model, the relationship between a parent project and its subprojects is a "one-to-many" hierarchy:     This means that while one parent project can contain multiple subprojects, each individual subproject can only roll up to one specific parent.    Note on Projects and Accounts    This strict hierarchy applies at all levels of the Sinch Account Model. Just as a subproject cannot belong to more than one parent project, a parent Project can only belong to one single Account.    Why this strict structure matters:    Access Inheritance: Subprojects inherit their UI access permissions directly from their parent project, and projects inherit from the account. Having multiple parents would create conflicting permissions.  Billing and Reporting: Costs are rolled up from the subproject to its specific parent project, and ultimately to the single account invoice. A single entity cannot report its activity or costs to two different parents simultaneously.  Resource Isolation: This strict structure ensures that resources belonging to an end-customer (in a reseller model) or a specific internal team are clearly mapped to a single management point.    Moving a Subproject    Please note that a subproject cannot be moved or transferred from one parent project to another. If you need to restructure your resources, you would typically need to provision new resources within a new subproject under the desired parent project.    Related Articles:   What is a subproject and how to manage subprojects? What is a project and managing projects? Creating a new project Sinch Account Model. ... View more

To get the most out of your Sinch account, it is important to structure your resources in a way that aligns with your business goals. By utilizing Projects and Subprojects, you can create a secure, organized environment that simplifies billing, resource management, and access control.      Learn more about how the Sinch account model works.   Organizing with Projects    A Project is your primary container. Every Sinch account starts with a default project, which is often sufficient for standard needs. However, if your implementation grows, you may want to use additional projects to separate different parts of your business.    Environmental Separation: The most common use for multiple projects is separating environments, such as creating one project for Development/Testing and another for Production. This ensures that testing activities never interfere with your live services.  Organizational Separation: You can use projects to separate completely different internal departments or business units if they require distinct resource pools and user access.    Organizing with Subprojects    A Subproject sits inside a parent project and is a powerful tool for more granular organization. While they function technically like projects, they are designed for specific organizational workflows.    The Reseller Model (Highly Recommended): If you are a reseller, the best practice is to create one Subproject per end-customer. This allows you to isolate the resources and costs for each client while maintaining a single parent project for your own overarching management.  Automation: Because subprojects support specific API automation capabilities (like programmatic creation and deletion), they are the ideal choice for businesses that need to scale their customer or project onboarding automatically.    Key Factors to Consider    When deciding how to organize your activity, keep these three rules of the Sinch Account Model in mind:    Access Inheritance: User access for the Build portal is managed at the Project level and inherited by all Subprojects within it. If two groups of users should never see each other's work, they should be in separate Projects.  API Isolation: API credentials can be generated at the Subproject level. This ensures that an API key used for one specific end-customer or application cannot be used to access resources in another.  Billing Roll-up: While you can view costs for individual subprojects, all costs ultimately roll up to the parent Project, and then to your single Account invoice.    Summary: Which should I use?   Use Case  Recommended Structure  Simple setup  Use your single Default Project.  Separating Dev/Prod  Use two separate Projects.  Reselling to Customers  Use one Subproject per customer within a Project.  Automating onboarding  Use Subprojects (via API).    ... View more

A Subproject is an additional organizational layer that sits inside a parent project within the Sinch Account Model (which consists of Accounts, Projects, and Subprojects):   Technically, a subproject functions exactly like a standard project when it comes to hosting resources. The key difference is its position in the hierarchy: while a Project’s parent is your overarching Account, a Subproject’s parent is a specific Project.      Key Characteristics of Subprojects    Hosting Resources: Just like parent projects, resources (such as phone numbers, apps, and specific API configurations) can sit directly on the subproject level.  Strict Hierarchy: There can only be one level of subprojects. A subproject cannot act as a parent to another subproject, and a subproject can only be tied to one specific parent project.  Inherited Portal Access: Subprojects do not have their own separate user management within the Sinch Build portal. They automatically inherit the UI access permissions configured on their parent project.  Isolated API Access: While portal access is inherited, API credentials and access controls configured at the subproject level are isolated from other subprojects and accounts.    When should I use a Subproject?    While standard Projects are excellent general containers for separating internal resources (such as creating different projects for "Development" vs. "Production" environments), Subprojects have specific, highly recommended use cases:    For Resellers (Highly Recommended): Subprojects are designed to perfectly represent a reseller's end-customers. By dedicating one subproject per end-customer, resellers can easily isolate costs, secure resources, and compartmentalize API access for each client. Furthermore, subprojects support certain API automation capabilities, allowing resellers to programmatically scale and manage their customer base.  For Direct Customers: If your organization has complex structural needs, subprojects can simply provide an additional tier of grouping beneath your parent projects.    Managing Subprojects    Accessing Subprojects   Click here to learn how to access your Subprojects in the Sinch Build Dashboard      Creation and Portal Management    Currently, the ability to manually create and manage subprojects from within the Sinch Build portal is primarily enabled for large-scale enterprise implementations operating alongside a dedicated Sinch Account Manager.    Note: We are aiming to enable the option for all accounts to create a limited number of projects and subprojects via self-service in the future.     API Automation    For use cases that require programmatic control (like the reseller model), subprojects offer automation capabilities through our APIs that are not available for parent projects. This includes the ability to automate the creation, configuration, and even the deletion of subprojects.      Deleting a Subproject    Currently, there is no self-service option to delete a subproject directly from within the Build portal. However, if you are utilizing the subproject automation APIs, programmatic deletion is supported. We plan to introduce self-service UI deletion in a future Build portal update.      Related Articles: Accessing your Subprojects in the Sinch Build Dashboard What is a project and how to manage projects? Sinch Account Model What is a project ID?. ... View more

  To help you effectively manage your resources, billing, and team access, Sinch uses a structured hierarchy: Accounts Projects Subprojects. Understanding this model is key to organizing your Sinch products securely, whether you are a direct customer separating internal environments or a reseller managing multiple end-customers.     The Hierarchy at a Glance   The Sinch Account Model follows a strict top-down structure:   This has a maximum depth of three tiers: Account (Top level) Project (Child of Account) Subproject (Child of Project Note: Subprojects cannot have their own child subprojects.)   Resources (such as phone numbers, apps, or API configurations) can sit directly on either the Project level or the Subproject level.     Account Level   The Account is the highest level of your Sinch organization. It represents your overarching business entity and help you manage: Billing & Cost: Your Account is the centralized entity for billing. One Account is tied to one invoice and operates in one single currency. Top-Level Access: Organization-wide settings and top-level user access are managed here.   Project Level   A Project is a general container for your Sinch resources. Every Sinch Account comes with at least one default project. Projects have the following features: Resource & Environment Separation: Projects are ideal for general separation of resources and access as desired (for example, creating separate Projects for "Development" and "Production" environments). Technical Equivalence: Technically, Projects and Subprojects function the same way when it comes to hosting resources. The main difference is that a Project's parent is the Account.   Subproject Level   A Subproject is an additional organizational layer that sits inside a parent Project. Technically, a Subproject acts exactly like a project, but it has a Project as its parent instead of an Account. Subprojects have the following features: The Reseller Use Case: Subprojects are highly recommended to represent resellers' end-customers. Because subprojects support certain API automation capabilities, they allow resellers to programmatically isolate costs and resources for individual customers securely. Strict Hierarchy: There can only be one level of subprojects. A subproject cannot act as a parent to another subproject. Inherited Management: Unlike parent Projects, Subprojects do not have their own separate user management in the Build Dashboard. They inherit the UI configurations of their parent project.   Access Control and Inheritance   Security and user access in Sinch, flow downwards, but they are handled differently depending on whether you are managing access to the Build Dashboard (UI) or access via APIs.   Build Dashboard (UI) Access: User access is configured on the Account or Project level, inherited downwards within that specific tree, and strictly isolated otherwise. Example 1: A user granted access to the whole Account automatically has access to all current and future projects and subprojects within it. Example 2: A user granted access only to Project A will have access to Project A and all of its subprojects. However, they are completely isolated from Project B unless explicitly granted access to it. Learn how to manage user access. API Access: Access controls for integrations are configured on the Project or Subproject level. API credentials are isolated between accounts and subprojects, and permissions are inherited downwards within the specific tree they are created in. Accessing your API Keys.   Frequently Asked Questions   Can I create multiple Projects and Subprojects?   Currently, the ability to manually create and manage additional projects and subprojects is enabled primarily for large-scale implementations operating alongside a dedicated Sinch Account Manager. For most users, a single default project is provisioned upon signup, which is sufficient for standard use cases.   Note: We are aiming to enable the option for all accounts to create a limited number of projects and subprojects via self-service in the future.     Can a Subproject belong to more than one Project?   No. A Subproject is strictly tied to a single parent Project. It cannot inherit from or be shared across multiple parent projects.     Can I delete a Project or Subproject?   Currently, there is no self-service deletion of Projects or Subprojects from within the Build Dashboard. For parent projects, deletion can only be performed by our team in exceptional cases via a support request.   Note: For Subprojects, certain API automation capabilities are available that do allow for programmatic deletion. We also plan to introduce self-service deletion capabilities directly within the Build Dashboard in the future.   Related Articles: What is a project and how to manage projects in Sinch? Accessing your Projects Creating a new project What is a project ID? What is a subproject and how to manage subprojects?. ... View more

Every Project and Subproject within your Sinch Account is assigned a unique, alphanumeric identifier known as a Project ID. This ID is essential for configuring your applications, making API calls, and for identifying specific environments when communicating with Sinch Support.   Why do I need a Project ID?   The Project ID serves as a unique "address" for your resources. You will typically need it to: Authenticate API Requests: Most Sinch APIs require a Project ID to route your messages and requests to the correct environment. Configure SDKs: When integrating Sinch into your apps, the Project ID ensures your code connects to your specific project resources. Support Requests: Providing your Project ID allows our support team to quickly locate your project and troubleshoot issues.   How to find your Project ID   Log in to the Sinch Build Dashboard. You can easily access all your projects from the Project top menu. Click the Project menu at the top left of the screen:   A list of your projects is displayed. If you have multiple projects then you can search for your project or the project ID in the search field at the top of the project list. Your current project is highlighted (in yellow and with a tick mark).   To view details of a project select the project you are interested in and click the options icon (three vertical dots)  to the right of the project name. The details of your project are displayed.   The Project ID is displayed at the top of the details list and you can click the copy icon to copy it to your clipboard.   Project ID vs. Subproject ID   While they are sitting at different levels of your account hierarchy, Project IDs and Subproject IDs function identically from a technical perspective. If you are a reseller or an enterprise customer, utilizing Subprojects to separate end-customers, you will use the specific ID of the Subproject when configuring API access for that particular customer's resources.   Related Articles Sinch Account Model What is a project and how to manage projects in Sinch? What is a subproject and how to manage subprojects? ... View more