curl --request POST \
--url 'https://api.scanova.io/webhook/hubspot/test/' \
--header 'Authorization: YOUR_API_KEY' \
--header 'Content-Type: application/json' \
--data '{
"connection_id": 5,
"object_type": "contact",
"field_map": [{"hubspot_property": "email"}, {"hubspot_property": "firstname"}]
}'
{ "success": true }
{
"success": false,
"detail": "None of the mapped fields are valid contact properties. Invalid for this object type: dealname. Re-open the field mapping and choose properties that belong to contact."
}
Integrations
Test a HubSpot configuration
POST /webhook/hubspot/test/
POST
/
webhook
/
hubspot
/
test
/
curl --request POST \
--url 'https://api.scanova.io/webhook/hubspot/test/' \
--header 'Authorization: YOUR_API_KEY' \
--header 'Content-Type: application/json' \
--data '{
"connection_id": 5,
"object_type": "contact",
"field_map": [{"hubspot_property": "email"}, {"hubspot_property": "firstname"}]
}'
{ "success": true }
{
"success": false,
"detail": "None of the mapped fields are valid contact properties. Invalid for this object type: dealname. Re-open the field mapping and choose properties that belong to contact."
}
Builds a sample record from a proposed field mapping and upserts it directly into HubSpot, to validate the configuration before it’s saved. This is stateless — it does not create or persist a webhook; the webhook is only created once you separately call List / create webhooks with
type: "hubspot".
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.array
required
Non-empty list of
{"hubspot_property": "..."} mappings — the properties to populate on the test record. Properties not valid for object_type, or internal/read-only ones, are silently skipped; if every mapped property gets skipped, the request fails with 400.curl --request POST \
--url 'https://api.scanova.io/webhook/hubspot/test/' \
--header 'Authorization: YOUR_API_KEY' \
--header 'Content-Type: application/json' \
--data '{
"connection_id": 5,
"object_type": "contact",
"field_map": [{"hubspot_property": "email"}, {"hubspot_property": "firstname"}]
}'
{ "success": true }
{
"success": false,
"detail": "None of the mapped fields are valid contact properties. Invalid for this object type: dealname. Re-open the field mapping and choose properties that belong to contact."
}
404 if connection_id isn’t owned by this account. 400 if the connection isn’t currently active, or if field_map is empty.
Related
- CRM properties — valid mapping targets for
object_type. - List / create webhooks — where the configuration is actually saved, once tested.
- 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
Test result.
Was this page helpful?