How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Zoca Hub Spot API

The HubSpot API from Zoca — 22 operation(s) for hubspot.

Zoca Hub Spot API is one of 193 APIs that Zoca publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include HubSpot. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 22 operations across 22 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 2 base URLs: https://api.zoca.ai, https://tasks.zoca.ai.

22 operations 22 paths 2 schemas 5 GET17 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.zoca.ai
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Zoca Hub Spot API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (access-token).

  • access-token — Enter JWT token in the format Bearer

Paths & Operations 22

Across 22 paths, the API surfaces 22 operations — 5 GET, 17 POST. Each is listed below with its method, path, parameters, and response codes.

Hubspot 22
GET
/hubspot/am-meeting-url/{entityId}
Get AM Meeting URL for Location
t_value 1 param → 200400
GET
/hubspot/offboarding-meeting-url/{entityId}
Get Offboarding Meeting URL for Location
getHubspotOffboardingMeetingUrlByEntityId 3 params → 200400
GET
/hubspot/upcoming-meetings/{entityId}
Get Upcoming Meetings for Location
getHubspotUpcomingMeetingsByEntityId 2 params → 200400
POST
/tasks/api/v1/hubspot/process-onboarding
Process HubSpot onboarding
postTasksApiV1HubspotProcessOnboarding body → 200
POST
/tasks/api/v1/hubspot/sync-hubspot-data
Sync HubSpot data
postTasksApiV1HubspotSyncHubspotData body → 200400500
POST
/tasks/api/v1/hubspot/webhook
T value
postTasksApiV1HubspotWebhook → 200
GET
/tasks/api/v1/hubspot/webhook/{jobId}/status
T value
getTasksApiV1HubspotWebhookByJobIdStatus → 200
POST
/tasks/api/v1/hubspot/webhook/ticket-chat
Handle HubSpot ticket chat webhook
postTasksApiV1HubspotWebhookTicketChat → 200
POST
/tasks/api/v1/hubspot/ticket/created
Handle request created event for ticket creation
postTasksApiV1HubspotTicketCreated → 200
POST
/tasks/api/v1/hubspot/ticket/send-message
Send message to HubSpot ticket conversation
postTasksApiV1HubspotTicketSendMessage body → 200
POST
/tasks/api/v1/hubspot/webhook/ticket-update
Handle HubSpot ticket update webhook
postTasksApiV1HubspotWebhookTicketUpdate → 200
POST
/tasks/api/v1/hubspot/request/completed
Handle request completion and update HubSpot ticket
postTasksApiV1HubspotRequestCompleted → 200
POST
/tasks/api/v1/hubspot/sync-demo-call-stages
Manually trigger Demo Call stage sync
postTasksApiV1HubspotSyncDemoCallStages body → 200
POST
/tasks/api/v1/hubspot/sync-location-to-demo-call
Manually trigger Location → Demo Call sync
postTasksApiV1HubspotSyncLocationToDemoCall → 200
POST
/tasks/api/v1/hubspot/sync-checkin-meeting-urls
Manually trigger Check-in Meeting URL sync
postTasksApiV1HubspotSyncCheckinMeetingUrls → 200
POST
/tasks/api/v1/hubspot/events/send
Send custom event to HubSpot
postTasksApiV1HubspotEventsSend body → 200400
POST
/tasks/api/v1/hubspot/update-deal-trial-started
Update deal to TRIALSTARTED
postTasksApiV1HubspotUpdateDealTrialStarted → 200
POST
/tasks/api/v1/hubspot/sales/lead-upsert
Upsert a lead in HubSpot
postTasksApiV1HubspotSalesLeadUpsert body → 200
POST
/tasks/api/v1/hubspot/sales/bulk/lead-upsert
Bulk upsert leads in HubSpot from CSV
postTasksApiV1HubspotSalesBulkLeadUpsert body → 200
POST
/tasks/api/v1/hubspot/get-contacts
Search HubSpot contacts
postTasksApiV1HubspotGetContacts body → 200400
POST
/tasks/api/v1/hubspot/trigger-potential-resurrection
Trigger Potential Resurrection Pipeline
postTasksApiV1HubspotTriggerPotentialResurrection → 200500
GET
/tasks/api/v1/hubspot/properties
List HubSpot Contact + Company Properties
getTasksApiV1HubspotProperties → 200500

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed is e (5 properties). Each schema is shown below with its type and property counts.

Object
object
e
object
5 properties 5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

zoca-hubspot-api-openapi.yml Raw ↑

Other APIs Zoca publishes across the network.

Zoca ACM API
Zoca Acuity API
Zoca Addon Groups API
Zoca Aeo Lead Magnet API
Zoca Agents API
Zoca API Keys API
Zoca App API
Zoca App Blocker API
Zoca App Blocker Updates API
Zoca Approvals API
Zoca Auth API
Zoca Billing API
Where this information came from

This is an independent, third-party profile of Zoca Hub Spot API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.