HubSpot Feedback Submissions

Name: Feedback Submissions API
Brand: Feedback Submissions
Availability: InStock

✓ Official Vendor SpecCRMCustomer Successoauth2, apiKey4 EndpointsREST

Install Jentic One Beta

Connect the Feedback Submissions to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Feedback Submissions, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Feedback Submissions API.

List recent feedback submissions via GET /crm/v3/objects/feedback_submissions

Retrieve a single feedback submission with all properties via GET /crm/v3/objects/feedback_submissions/{feedbackSubmissionId}

Batch-read submissions for a list of IDs through POST /crm/v3/objects/feedback_submissions/batch/read

GET STARTED

Start building with Feedback Submissions API

Explore with Jentic

View OpenAPI Document

For Agents

Read and search HubSpot feedback submission records (NPS, CSAT, CES survey responses) as CRM objects via /crm/v3/objects/feedback_submissions.

Use for: I need to find every NPS detractor (score 0-6) submitted in the last 30 days, List all CSAT submissions tied to a specific deal owner, Retrieve the full feedback submission record for a specific ID, Search for negative feedback submissions on tickets closed last week

Not supported: Does not create surveys, send invitations, or modify submission scores - use for read-only retrieval of HubSpot NPS, CSAT, and CES submissions only.

Use Cases

Patterns agents use Feedback Submissions API for, with concrete tasks.

★ Detractor Routing

When a customer submits an NPS or CSAT response below a threshold, find the submission, identify the contact, and route a follow-up task to the account owner. The search endpoint accepts filterGroups so a workflow can target only detractor scores within a recent window. Because submissions are read-only, the actual creation happens inside HubSpot when the survey is answered.

Search HubSpot feedback submissions where hs_survey_type equals NPS_TRANSACTIONAL, hs_value is less than or equal to 6, and createdate is within the last 30 days, returning each submission's contact ID.

Score and Pipeline Correlation

Pull feedback submissions and their associations to deals so a revenue team can correlate satisfaction scores with deal outcomes. The list endpoint plus association expansion returns submissions, scores, survey type, and the linked deal in one walk, which is the basis for retention and renewal analysis. Combine with deal stage filtering to focus on closed-won or churn-risk segments.

List feedback submissions with associations to deals, then filter to submissions where hs_survey_type equals CSAT and the linked deal stage is closedwon.

Contact-Level Sentiment History

Surface every feedback submission a single contact has ever made for a renewal review or escalation. The search endpoint with a hs_object_id filter on the related contact returns the full sentiment history sorted by date. Pair with the Tickets API to see which support cases preceded each score change.

Search feedback submissions associated with contact ID 12345, sorted by createdate descending, returning hs_value, hs_survey_type, and createdate.

Agent-Driven Sentiment Pulls via Jentic

An AI customer success agent reading a renewal task pulls the customer's feedback history through Jentic to summarise sentiment for the rep. The agent searches for the read or search operation, executes it with the contact ID, and returns a structured summary. The flow uses Jentic-managed credentials so the HubSpot token never enters the model's context.

Use Jentic to search 'search HubSpot feedback submissions for a contact', execute POST /crm/v3/objects/feedback_submissions/search with the contact filter, and return the latest three responses.

Key Endpoints

4 endpoints — the hubspot feedback submissions api exposes feedback submission records - typically nps, csat, and ces survey responses captured by hubspot's feedback tool - as a crm object so ai agents can read and search them alongside contacts and deals.

METHOD

PATH

DESCRIPTION

GET

/crm/v3/objects/feedback_submissions

List feedback submissions with pagination

GET

/crm/v3/objects/feedback_submissions/{feedbackSubmissionId}

Retrieve a single feedback submission

POST

/crm/v3/objects/feedback_submissions/batch/read

Batch-read feedback submissions by ID

POST

/crm/v3/objects/feedback_submissions/search

Search feedback submissions by property filters

GET

/crm/v3/objects/feedback_submissions

List feedback submissions with pagination

GET

/crm/v3/objects/feedback_submissions/{feedbackSubmissionId}

Retrieve a single feedback submission

POST

/crm/v3/objects/feedback_submissions/batch/read

Batch-read feedback submissions by ID

POST

/crm/v3/objects/feedback_submissions/search

Search feedback submissions by property filters

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your HubSpot OAuth token or private-app key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'find HubSpot NPS detractors' or 'read a feedback submission', and Jentic returns the matching Feedback Submissions operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Feedback Submissions API through Jentic.

What authentication does the HubSpot Feedback Submissions API use?

Feedback Submissions accepts OAuth 2.0 access tokens with the crm.objects.feedback_submissions.read scope and HubSpot private app API keys passed in the private-app header. Through Jentic the credential lives in your Jentic One instance and is injected at execution time so it never enters the agent's context.

Can I create or update feedback submissions through this API?

No. The API is read-only - submissions are created by HubSpot's feedback survey tool when a respondent submits a response. To capture feedback from external surveys, log it as a custom engagement or pipe it through HubSpot's feedback survey product.

What are the rate limits for the HubSpot Feedback Submissions API?

Account-level limits apply - typically 100 requests per 10 seconds for OAuth apps and 190 per 10 seconds for private apps on paid tiers. Use POST /crm/v3/objects/feedback_submissions/batch/read for any reporting job that touches more than a handful of submissions.

How do I search feedback submissions through Jentic?

Run jentic.search('search HubSpot feedback submissions'), load the schema for POST /crm/v3/objects/feedback_submissions/search, and execute it with a filterGroups payload (for example, hs_survey_type equals NPS_TRANSACTIONAL and hs_value less than 7). Jentic returns matching submissions as structured JSON.

Which survey types are exposed via this API?

The hs_survey_type property identifies the survey kind - typical values are NPS_TRANSACTIONAL, NPS_RELATIONAL, CSAT, and CES. Filter on this property to pull a single survey type into a downstream system.

Can I link feedback to a contact or deal?

Yes. Feedback submissions support associations to contacts, tickets, and other CRM objects. Expand associations on the read endpoint or query the CRM Associations API to fetch the linked contact or deal for any submission.

Can I limit what my agent is allowed to do with the HubSpot Feedback Submissions API?

Yes. Because you run Jentic One yourself, you decide which of this API's operations your agent may call, and every one of them only reads data: listing feedback submissions, retrieving one by ID, batch-reading a set of IDs, and searching by survey type or score. Since the API exposes no create or update calls, an agent scoped to it can pull NPS, CSAT, and CES results without any ability to alter a submission. You can also narrow the set further, for example allowing only the search operation, and your stored HubSpot credential is injected at execution time rather than exposed to the agent.

HubSpot Feedback Submissions

Connect the Feedback Submissions to your agent

Capabilities

Start building with Feedback Submissions API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs