Feedback Submissions

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

✓ Official Vendor SpecCRMCustomer Successoauth2, apiKey4 EndpointsREST

For Agents

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

Quickstart

Get started with Feedback Submissions in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"search HubSpot feedback submissions"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

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

Search submissions by survey type, score, or contact via POST /crm/v3/objects/feedback_submissions/search

GET STARTED

Start building with Feedback Submissions API

Explore with Jentic

View OpenAPI Document

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.

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. It exposes a list endpoint, a single-record retrieve, a batch read, and a search endpoint, all read-oriented because feedback submissions are created by HubSpot when a survey response arrives. Use it to pipe customer sentiment into reporting, route detractors, or correlate scores with deal outcomes.

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 though Jentic?

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

Credential isolation

HubSpot OAuth tokens and private app keys are stored encrypted in the Jentic vault. Agents receive a scoped execution token — the raw HubSpot credential is injected at call time and never enters the agent's context.

Intent-based discovery

Agents search Jentic by intent (e.g., 'find HubSpot NPS detractors') and Jentic returns the POST /crm/v3/objects/feedback_submissions/search operation with its input schema, so the agent calls the right endpoint without browsing HubSpot docs.

Time to first call

Direct HubSpot integration: 1-2 days for OAuth scopes, association expansion, and pagination handling. Through Jentic: under 1 hour — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

HubSpot Contacts

Resolve the contact tied to each feedback submission

Use Contacts to fetch contact details after a feedback submission lookup so the agent can act on the response.

Complementary

HubSpot Tickets

Tie negative feedback to a follow-up support ticket

Use Tickets after finding a detractor to open a follow-up case for the customer success team.

Complementary

HubSpot Deals

Correlate feedback scores with deal stage and renewal status

Use Deals to filter feedback to renewal-stage opportunities for a churn-risk report.

Alternative

Typeform

Capture survey responses outside HubSpot when the team uses Typeform forms

Choose Typeform when surveys live outside HubSpot; sync responses into HubSpot via custom engagement logging.

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 the MAXsystem vault 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.