Skip to content

Client-side Setup

To start using the Backendless APIs, .NET and Xamarin applications must add a reference for the Backendless library and  its dependencies. The library is available as a NuGet package.

Once the Backendless reference is added, the client application must initialize the SDK with one of the approaches shown below.

  1. Using your Backendless subdomain name: Every Backendless application receives a subdomain under the backendless.app domain. The subdomain is in the format of xxxx.backendless.app, where xxxx is a name assigned to your application. The subdomain is used to identify your backend when the client app uses Backendless APIs and also to run client-side applications created with UI Builder. To see the subdomain name assigned to your application navigate to the main dashboard of your application, you will see the Backendless subdomain field. Use the copy icon on the right side of the field to copy the value:
    subdomain-maindash
    The code to initialize your .NET/Unity/Xamarin application with your subdomain name is:

    Backendless.InitApp( "https://your-subdomain-name.backendless.app" );
    

  2. Your own domain name. You can assign a custom domain to your application using the Manage > App Settings > Custom Domain section of Backendless Console. When a custom domain is assigned, your .NET/Unity/Xamarin application should be initialized with the following code:

    Backendless.InitApp( "http://your-custom-domain" );
    

    To enable SSL for your custom domain, make sure your application is on the Scale plan. Configure a custom domain in Backendless Console, we will gladly generate an SSL certificate for your domain.

  3. Backendless native endpoint. Every Backendless cluster (hosting zone) has a native endpoint. Your application's backend is running in one of the clusters below. It is important to make sure to use the endpoint that correspond to the cluster. The North American endpoint is automatically embedded in the SDK, it is not necessary to set it in the code, however, the EU endpoint must be explicitly specified. Use the code below based on the cluster your app is in:
    North American cluster:
    Backendless.InitApp( "application-Id", "API-key" );
    

    South American cluster:
    Backendless.URL = "https://api.sa.backendless.com";
    Backendless.InitApp( "application-Id", "API-key" );
    

    European Union cluster:
    Backendless.URL = "https://eu-api.backendless.com";
    Backendless.InitApp( "application-Id", "API-key" );
    

    The values for "application-Id" and "API-key" must be obtained from Backendless Console. They are available on the main dashboard as well as the Manage > App Settings screen.

Most of the Backendless SDK for .NET classes are available in the BackendlessAPI and BackendlessAPI.Async namespaces. Import the classes with the following statements:

using BackendlessAPI;  
using BackendlessAPI.Async;  
using BackendlessAPI.Exception;

Application ID and API Key

Values for the application-id and api-key arguments in the application initialization call must be obtained through the Backendless Console:

  1. Login to your account and select the application.
  2. Click the Manage icon from the vertical icon-menu on the left.
  3. The App Settings section is selected by default. The interface contains values for Application ID and API keys for each supported client-side environment.
  4. Use the Copy icon to copy the value into the system clipboard.
    appsettings-keys.zoom60

Make sure to use the ".NET API Key" for the dotNET-API-key argument.