curl --request GET \
--url 'https://api.scanova.io/webhook/hubspot/properties/?connection_id=5&object_type=contact' \
--header 'Authorization: YOUR_API_KEY'
{
"results": [
{
"name": "email",
"label": "Email",
"type": "string",
"fieldType": "text",
"groupName": "contactinformation",
"groupLabel": "Contact Information",
"displayOrder": 1,
"featured": true
}
]
}
Integrations
CRM properties
GET /webhook/hubspot/properties/
GET
/
webhook
/
hubspot
/
properties
/
curl --request GET \
--url 'https://api.scanova.io/webhook/hubspot/properties/?connection_id=5&object_type=contact' \
--header 'Authorization: YOUR_API_KEY'
{
"results": [
{
"name": "email",
"label": "Email",
"type": "string",
"fieldType": "text",
"groupName": "contactinformation",
"groupLabel": "Contact Information",
"displayOrder": 1,
"featured": true
}
]
}
Lists the mappable properties for one HubSpot CRM object type, for building a field-mapping UI (Scanova field → HubSpot property).
Hidden, read-only/calculated, and internal pipeline/stage properties (
Requires the account’s
INTEGRATION_HUBSPOT quota.integer
required
HubSpot connection id, from List HubSpot connections.
string
default:"contact"
One of
contact, company, deal, ticket.curl --request GET \
--url 'https://api.scanova.io/webhook/hubspot/properties/?connection_id=5&object_type=contact' \
--header 'Authorization: YOUR_API_KEY'
{
"results": [
{
"name": "email",
"label": "Email",
"type": "string",
"fieldType": "text",
"groupName": "contactinformation",
"groupLabel": "Contact Information",
"displayOrder": 1,
"featured": true
}
]
}
hs_pipeline, hs_pipeline_stage, pipeline, dealstage) are filtered out — they can’t be written via the API and aren’t valid mapping targets. featured: true marks the curated set of commonly-mapped fields for the object type, sorted first; the rest are sorted alphabetically by label.
502 if the live HubSpot API call fails. 404 if connection_id isn’t owned by this account.
Related
- Mappable source fields — the Scanova side of the mapping.
- Test a HubSpot configuration
- Management API overview — the auth scheme and quota architecture this endpoint is part of.
Authorizations
Send your Management API key as the raw value of the Authorization header — no "Bearer " or "Token " prefix, and no other characters. Example: Authorization: 401f7ac837da42b97f613d789819ff93537bee6a. A header containing more than one space-separated part is rejected outright. Requests also require the request's Host header to be the management API host (e.g. api.scanova.io) — the same key sent to the regular API host will not authenticate.
Response
Mappable properties for the object type.
Was this page helpful?