Domain list endpoint and item endpoint are formatted differently


#1

Camel case is used for list endpoint, underscores are used for item endpoint:

"actualCname": "demo-hubapi.hs-sites.com",
  "actualIp": "",
  "addedToWaf": false,
  "consecutiveNonResolvingCount": 0,
  "cosObjectTypeId": 3,
  "created": 1333053016000,
  "deletable": false,
  "domain": "demo-hubapi.hs-sites.com",
  "id": 101304,
  "isAnyPrimary": false,
  "isDnsCorrect": true,
  "isInternalDomain": true,
  "isLegacy": false,
  "isLegacyDomain": false,
  "isResolving": true,
  "isSslEnabled": true,
  "isSslOnly": false,
  "label": "demo-hubapi.hs-sites.com",
  "manuallyMarkedAsResolving": false,
  "markSslOnlyAfterProvisioning": false,
  "portalId": 62515,
  "primaryBlog": false,
  "primaryBlogPost": false,
  "primaryClickTracking": false,
  "primaryEmail": false,
  "primaryLandingPage": false,
  "primaryLegacyPage": false,
  "primarySitePage": false,
  "secondaryToDomain": "62515.hs-sites.com",
  "siteId": 69224,
  "updated": 1364439000000

“actual_cname”: “demo-hubapi.hs-sites.com”,
“actual_ip”: “”,
“added_to_waf”: false,
“consecutive_non_resolving_count”: 0,
“cos_object_type_id”: 3,
“created”: 1333053016000,
“deletable”: false,
“domain”: “demo-hubapi.hs-sites.com”,
“id”: 101304,
“is_any_primary”: false,
“is_dns_correct”: true,
“is_internal_domain”: true,
“is_legacy”: false,
“is_legacy_domain”: false,
“is_resolving”: true,
“is_ssl_enabled”: true,
“is_ssl_only”: false,
“label”: “demo-hubapi.hs-sites.com”,
“manually_marked_as_resolving”: false,
“mark_ssl_only_after_provisioning”: false,
“portal_id”: 62515,
“primary_blog”: false,
“primary_blog_post”: false,
“primary_click_tracking”: false,
“primary_email”: false,
“primary_landing_page”: false,
“primary_legacy_page”: false,
“primary_site_page”: false,
“secondary_to_domain”: “62515.hs-sites.com”,
“site_id”: 69224,
“updated”: 1364439000000


#2

Hi Adam,

Thanks for bearing with us on the inconsistencies here. We’ll keep this point in mind as we work to smooth out the inconsistencies and issues with our API.

In the meantime, it’s unlikely that we’ll make any quick changes to resolve this particular inconsistency as to avoid breaking changes for our other users.

Thanks,
-Paul