Setting up Duda APS package

Below you will find the steps for installing Duda’s APS package. Some credentials should have been given to you ahead of time by Duda that enable you to 100% complete the setup of this package.

  1. Download the latest version of the package from the APS Catalog.
  2. Log in to your Odin Service Automation control panel and under the services tab on the left, click on Applications. After seeing all the applications, click on Import package.
  3. Upload the package file that you had downloaded in step one and click submit. 
  4. After importing the package, you should now see it as part of your application list.
  5. Now that we’ve got the package installed, we will want to setup an instance of this package for the system to use. To get started, open the package by clicking on the name Duda. 
  6. Head over to the Instances tab and click on +Install. This is the base step of installing the package with the default settings. This should only need to be done once during the install.
  7. During your first time installing an instance of the Duda package, it will ask you to specify the Application Endpoint URI, you should input it in the following format:
  • http://[application-endpoint-server-ip]:[port]/[package- name]
  • If you’re not familiar with creating an application endpoint, please follow the steps below. If you are, you can skip to step 8.
  • To set up an endpoint, you must configure this by directly logging into your server and running a configuration file that is provided by Odin/APS.
  • Log in to your OSA endpoint server via SSH. 
  • Make sure PHP, Apache (HTTPD) and the APS runtime library are installed for your instance. If your not sure about this, please visit the APS docs here:
  • To a folder you know and can easily access upload the most recent version of the Duda APS application zip file. In this example, I use WGET to download the most recent version to the root folder: 
  • The endpoint setup can be setup by running a script that is provided by Odin/APS Standard. To download the script, run this command: 
  • wget
  • It should look like this:
  • Now that we have both the endpoint script and the ZIP package file, we can run the endpoint script and create the endpoint for the application we need, here is the command: Duda

Blue above is the endpoint script we downloaded from APS Standard.
Green above is the folder path / endpoint we are creating on the server
Red above is the zip file that we uploaded originally.

If done successfully, your terminal / console should look like this:

You will want to copy the HTTPS endpoint URL and place that into the OSA Instance install.

  1. Place the HTTPS endpoint URL we created in the step above into the Instance setup box:
  2. After choosing the application endpoint, you’ll be asked for your logging preferences of the package. Duda recommends that you enable both:
  3. Next, confirm all the settings of the instance and click finish. This should run a task to provision the new instance, which should be very quick. Browse through to the Duda Application Instance installs, you should see that the app is installed correctly:
  4. Under the Duda application, click on the newly created Duda instance to open the settings for the instance and click on the Partner List Tab. It should look like this:
    Duda allows you to set up multiple partner accounts inside of one application instance install. This is generally used for multi-brand OSA installs that need different branding, settings, plans configurations, etc. within the Duda White-Label Website Builder. For each brand, you will need a separate Duda partner account that Duda will provide credentials for.
  5. Click on the Create button under the partner list. When adding a new partner, the Duda APS package will ask for the following fields:

Field Name:



The brand name you are giving the website building product. This will be used inside of the customer account as the tab name for the website builder. Usually companies use names such as: “Website Builder” or “Site Builder” or “Russ’ Site Builder”.

API Username

This is the API account name that relates back to your Duda partner account. Duda will usually give this directly to you, or you get it from the API section in your Duda partner account.

API Password

This is the password that is associated with the API Username above. It will never be same as the login password to your Duda account login.


This is the API endpoint URL for the Duda system. Usually this will be OR Make sure you always use https:// with this URL.

Login Username

This is the login to your Duda account directly, usually an email address.

Login URL

This is the address to your Duda white label portal.

CNAME target

The value where domains hosted by the OSA instance will point the www value of domains to. Leave this as default unless Duda provides you with a different value.

A-Record target

The static IP address that domains will point their @ (base/root) domain value to. This will redirect the root domain to the www value of the website. Usually you will place the IP address of: This is an IP address that Duda owns and controls.

Input all the corresponding fields with the information that was provided to you by Duda. After creating the partner, open up the partner settings and click synchronize in the plans list. This will pull in a list plans that Duda has made available for you as part of your account setup.

  1. At this point, we’ve completely set up the Duda partner account and we need to move into packaging the resources (plans, accounts, websites, etc..) that the package provides into the APS system. 

Configuring Resources

Next we need to configure/create all of the application resources that will be used as part of the provisioning and storage process. This can be found within the application resource types tab of the application:

Global Settings Resource

  1. Create a new resource and select Application Service Reference as the class
  2. Enter a resource Name and click Next. (We recommend naming it ‘Duda Global Settings’)
  3. For the APS Type, Select globalSettings 
  4. Click on the instance ID link in the Resource column and click Finish button on the next screen

Partner Account Resource

  1. Create a new resource and select Application Service Reference as the class
  2. Enter a resource Name and click Next. (We recommend naming it ‘Duda Partner Reference’)
  3. Select partner as the APS Type
  4. Click on the instance ID link in the Resource column and click Finish button on the next screen

Plan Resource

  1. Create a new resource and select Application Service Reference as the class
  2. Enter a resource Name and click Next. (We recommend naming it similar to the plan name you’re selecting, so for example: Silver Plan)
  3. Select plan as the APS Type
  4. Click on the instance link that correlates to the plan that you named it in the previous step 

It is important to create a Plan resource for each plan you have for Partner or plan on selling. Repeat the steps above for each plan you want to be able to sell. We recommend configuring one for each plan you have access to.

PlanID Resource

  1. Create a new resource and select Application Counter (unit) as the class
  2. Enter a resource Name and click Next. (We recommend naming it ‘Duda PlanID’)
  3. Select Plan ID as the APS Type
  4. Click on the instance ID link in the Resource column and click Finish button on the next screen

Responsive Website Resource

  1. Create a new resource and select Application Service as the class
  2. Enter a resource Name and click Next. (We recommend naming it ‘Responsive Website Resource’’)
  3. Select site as APS Type.
  4. Check the box that says Automatically Provision Service
  5. Click next and then finish 

Configure Service Template

After we’ve created all the resources above, we need a service template that will be used to bundle together all the resources we need to sell Duda packages.

  1. Head over to the Products > Service Templates area and create a new service template.
  2. Give the service template a name and click next (We recommend naming it ‘Duda Service Template’)
  3. Leave the Autoprovisioning and Account-Wide Service check-boxes checked.
  4. Make sure the type is Custom
  5. From the check list, choose all resources you created before. This should include: Global Settings, Partner Account, PlanID, Responsive Website and all plan resources. It’s important you choose all of these as part of the resource template. It should look like this:

Configuring Services for Selling

Now that we have the package instance installed, configured and added into a service template, we will want to create Service Plan that can be used as a reference point for selling of plans. To do this:

  1. Head over to the OBA by clicking on the billing link at the top right of the Odin control panel.
  2. Start creating a new Service Plan under the Products > Service Plans tab.
  3. For the plan type, choose the Generic Service Plan option and click next.
  4. Give the plan a name. It should relate to the Duda plan that you are indenting to sell. So, if you’re selling the silver tier, then make sure you name it as such.
  5. Choose the Duda Service Template you had previously created in OSA. It should look like: 
  6. Under the plan category, make sure is selected on Other Services
  7. Give the Service Plan a short and detailed summary
  8. Check the Published checkbox under billing terms
  9. Choose the billing period you want to have selected on your plan
  10. Click Next
  11. Check the boxes for each Subscription period you wish to sell this plan under. Also set any prices you wish to charge here. It should look like:
  12. After you’ve configured your desired subscriptions and prices), click Next.
  13. On the next step, click  the Finish button. We will explain and configure the resource rates in the next section of this guide. 

NOTE: You’ll want to create a service plan for each Duda plan you expect to sell.

Resource Rates

This is the most confusing step step -- so make sure you follow closely here. We need to correlate the internal plan resource ID to the service plan that you are planning to sell. The first step will be to head to the partner settings of APS Duda package. On this page, you can see all the plans that are configured for your account with their internal ID:

We recommend taking a screenshot of this page and saving it for reference during the resource rate configuration inside of the Service Plan(s).

After you know the internal ID’s of the plan resources, head over to the service plans in OBA. For each Duda Service Plan you’ve already created, you’ll want to edit and apply the correct resource ID configuration. To do this, find the Service Plan you’ve created and click on it. Head to the Resource Rates tab and click Add New Resource Rate:

Select the Duda Plan ID checkbox (resource) and make sure the Resource Category is Additional Resources and click next.

In the Inc. Amount box, place the Internal Plan ID that references back to the Duda plans that are available to you. See here:

Make sure that for all Service Plans you plan on selling -- that each one has this resource rate configured correctly for the corresponding plan you want to sell.



Priority Phone Support

English phone support is available 18 hours a day,
Monday through Friday, 3am to 9pm (EST).

United States +1 866-776-1550 3am to 9pm (Eastern)
United Kingdom +44 (0)800-011-9071 8am to 2am (London)
France +33 (0)9-75-18-84-74 9am to 3am (Paris)
Israel +972 (0)3-720-8922 10am to 4am (Jerusalem)
Australia +61 (0)2-8880-9166 7pm to 1pm (Sydney)
To schedule a call in French, Portuguese, Hebrew or Russian, please email us at

Please Log in as a DudaPro

Priority Phone Support is available exclusively to DudaPros. Log in to your DudaPro account now to see our international support numbers.

Log In
Not a DudaPro? Start a free trial now!