HomeGuidesAPI ReferenceChangelog
Log In
Guides

Run a Calculation with Arcadia's Typical Baseline

This page walks through a common use case where a user needs to leverage Arcadia's synthetic building based load curves for what-if analyses in Signal's On-Demand Cost Calculation API

Use Arcadia's building baselines to run a Signal On-Demand Cost Calculation with a synthetic load curve instead of providing your own usage data.

Before you begin

Collect the following values before you build the request:

  • Select the masterTariffId for the tariff you want to calculate against.
  • Confirm whether the tariff is residential or commercial.
  • Choose the calculation date range with fromDateTime and toDateTime.
  • Choose a supported buildingId that matches the tariff type.

Request example

Start with a calculation request that includes two baseline-related propertyInputs: baselineType and buildingId.

This example uses singleFamilyDetached. Replace it with the supported buildingId value that best matches your site and tariff type.

{
    "fromDateTime": "2026-05-01T00:00:00-04:00",
    "toDateTime": "2026-06-01T00:00:00-04:00",
    "detailLevel": "RATE",
    "fields": "ext",
    "groupBy": "ALL",
    "billingPeriod": true,
    "minimums": true,
    "bundleRates": false,
    "propertyInputs": [
        {
            "keyName": "baselineType",
            "dataValue": "typicalElectricity",
            "operator": "+",
            "dataFactor": 1
        },
        {
            "keyName": "buildingId",
            "dataValue": "singleFamilyDetached"
        }
    ],
    "masterTariffId": 355
}

Required baseline inputs

To use an Arcadia baseline, include the following two propertyInputs objects together.

For more detail about how typical baseline data is modeled and how to fetch the related property data, see the Typical Baseline Overview API Reference.

baselineType

Set baselineType to typicalElectricity to tell the calculation to use an Arcadia usage baseline.

{
    "keyName": "baselineType",
    "dataValue": "typicalElectricity",
    "operator": "+",
    "dataFactor": 1
}

This baseline input replaces a consumption or demand input that would otherwise be supplied through interval dataSeries or block dataValue data.

buildingId

{
    "keyName": "buildingId",
    "dataValue": "singleFamilyDetached"
}

Set buildingId to a supported building type. This value shapes the baseline curve so it aligns with the expected usage draw for that type of building.

Replace singleFamilyDetached with the supported value that most closely matches your site.

Supported buildingId values

Choose a buildingId that matches the tariff type for the masterTariffId used in your calculation. Residential and commercial tariffs support different baseline options.

Use a residential buildingId with residential tariffs and a commercial buildingId with commercial tariffs. The buildingId should align with the tariff behind the masterTariffId in the same request.

If there is an exact match for the site, use it. If there is not an exact match, use one of the more generic options, such as RESIDENTIAL, SMALL_COMMERCIAL, MEDIUM_COMMERCIAL, or LARGE_COMMERCIAL.

Residential baseline options

Residential buildingId Values
singleFamilyDetached
singleFamilyAttached
apartmentUnder5Units
apartmentOver4Units
mobileHome
RESIDENTIAL

Commercial baseline options

Commercial buildingId Values
largeOffice
mediumOffice
smallOffice
warehouse
standAloneRetail
stripMall
primarySchool
secondarySchool
supermarket
quickServiceRestaurant
fullServiceRestaurant
hospital
outpatientHealthCare
smallHotel
largeHotel
midriseApartment
SMALL_COMMERCIAL
MEDIUM_COMMERCIAL
LARGE_COMMERCIAL

Troubleshooting

Check the following items if the request does not behave as expected:

  • Include both required baseline inputs: baselineType and buildingId.
  • Set baselineType to typicalElectricity.
  • Use a buildingId value from the residential or commercial tables above.
  • Match the buildingId category to the tariff type associated with the masterTariffId.
  • Pass buildingId as a JSON string, such as "singleFamilyDetached", not as an unquoted placeholder.
  • Do not include separate consumption or demand usage inputs when you want the calculation to use the Arcadia building baseline.
    • If you need to scale up your usage data consider using the dataFactor field