Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Storage / Hubapi / Files
Files logo

HubSpot Files

Browse all Hubapi APIs
52
AI ReadinessFoundational (C-)52/100
See full scorecard
Agent-ready OpenAPI document · curated by JenticStorageObject StorageapiKey, oauth218 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Upload, search, replace, and delete files in the HubSpot file manager, plus manage folders, signed URLs, and asynchronous URL imports.

Use for: I need to upload a PDF report to the HubSpot file manager, Import an image from a URL into HubSpot asynchronously, Search for files in HubSpot by name, Generate a signed URL to share a private HubSpot file

Not supported: Does not store CRM contact records, send marketing emails, or manage CMS pages - use only for HubSpot file manager uploads, folders, and signed URLs.

Jentic publishes the only available OpenAPI specification for HubSpot Files, keeping it validated and agent-ready. The HubSpot Files API manages the file manager attached to a HubSpot portal - uploading binary files, importing from URLs, organising them into folders, generating signed URLs for private files, and handling GDPR deletion. Files stored here are referenced by HubSpot CMS pages, marketing emails, and CRM records, so the API is the integration surface whenever an agent or app needs to put assets into the HubSpot ecosystem.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the Files to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Files, 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.

1

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fhubapi.com%2Fhubspot-files" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fhubapi.com%2Fhubspot-files" | 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 Files API.

Upload a binary file to HubSpot via POST /files/v3/files

Import a file from a public URL asynchronously through /files/v3/files/import-from-url/async and check its task status

Search files and folders by name, type, and folder via /files/v3/files/search and /files/v3/folders/search

Replace a file in place with PUT /files/v3/files/{fileId} so existing references remain valid

Generate a signed URL for a private file through GET /files/v3/files/{fileId}/signed-url

Create, update, and delete folders, including async folder property updates

GDPR-delete a file via DELETE /files/v3/files/{fileId}/gdpr-delete

Use Cases

Patterns agents use Files API for, with concrete tasks.

★ Sync Marketing Assets into HubSpot

Upload product images, datasheets, or branded PDFs into the HubSpot file manager so they can be referenced in CMS pages and marketing emails. POST /files/v3/files accepts multipart uploads; /files/v3/files/import-from-url/async pulls assets from existing URLs without proxying through the agent.

POST a PDF datasheet to /files/v3/files with folderPath /marketing/datasheets and confirm a 201 response with the file URL.

Replace Files Without Breaking References

When a marketing PDF or image needs an updated version, PUT /files/v3/files/{fileId} replaces the binary in place. Existing CMS pages and email links keep working because the file ID and URL stay the same. This is faster and safer than uploading a fresh file and rewriting references.

PUT the new datasheet PDF to /files/v3/files/9876543210 to replace the existing file binary while preserving its public URL.

GDPR-Compliant File Deletion

Honour data subject deletion requests by calling DELETE /files/v3/files/{fileId}/gdpr-delete, which permanently removes the file and prevents recovery. This is the compliant path versus DELETE /files/v3/files/{fileId}, which is a soft delete only.

DELETE /files/v3/files/{fileId}/gdpr-delete for every file referenced by the deletion-request user record.

AI Agent File Storage via Jentic

An AI agent that generates a report PDF or image asset uses Jentic to upload it into HubSpot's file manager and then references the returned URL in a marketing email or CMS page - without juggling HubSpot OAuth flows in the agent code.

Search Jentic for upload a file to hubspot, load POST /files/v3/files, and execute with the binary and folderPath /agents/output.

Key Endpoints

18 endpoints — jentic publishes the only available openapi specification for hubspot files, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/files/v3/files

Upload a file

POST

/files/v3/files/import-from-url/async

Import a file from a URL asynchronously

GET

/files/v3/files/search

Search files

PUT

/files/v3/files/{fileId}

Replace a file in place

GET

/files/v3/files/{fileId}/signed-url

Get a signed URL for a private file

DELETE

/files/v3/files/{fileId}/gdpr-delete

GDPR-delete a file permanently

POST

/files/v3/folders

Create a folder

GET

/files/v3/folders/search

Search folders

POST

/files/v3/files

Upload a file

POST

/files/v3/files/import-from-url/async

Import a file from a URL asynchronously

GET

/files/v3/files/search

Search files

PUT

/files/v3/files/{fileId}

Replace a file in place

GET

/files/v3/files/{fileId}/signed-url

Get a signed URL for a private file

DELETE

/files/v3/files/{fileId}/gdpr-delete

GDPR-delete a file permanently

POST

/files/v3/folders

Create a folder

GET

/files/v3/folders/search

Search folders

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

F

Files

- Foundational (C-)
52/100
72
Foundational Compliance
56
Developer Experience & Jentic Compatibility
29
AI-Readiness & Agent Experience
94
Agent Usability
52
Security
100
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
72

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4
88%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

0%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

56

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: CSignals: 4
2%

Example Density

How richly the API is illustrated with examples.

71%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

29

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4
58%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

0%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

58%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

52

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1
52%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1
100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring HubSpot Files by hand means choosing between its hapikey query, OAuth, and private-app auth, keeping the api.hubapi.com host straight across the files v3 upload, folder, and signed-URL endpoints, and handling errors yourself. Through Jentic you install once, import Files from the API Directory, store the credential once, and your agent calls it.

Permission scoping

Files puts the file id in the URL path (/files/v3/files/{fileId}/...), so a rule can pin your agent to one file: it can update it or fetch its signed URL and nothing else. You choose the operations it may call, so a destructive operation like the GDPR delete is not included unless you add it.

Credential isolation

Your HubSpot credential is stored once, encrypted, by your own Jentic One instance and injected per call at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'upload a file to HubSpot' or 'get a signed URL for a file', and Jentic returns the matching /files/v3 operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

HubSpot CMS API

→

Reference uploaded files in HubSpot CMS pages and templates

Pair with CMS API when the agent uploads a file and then needs to embed it in a page or template.

Complementary

HubSpot Marketing API

→

Reference uploaded files (logos, attachments) in marketing emails and assets

Pair when the agent uploads an asset and then attaches it to an email or campaign.

Alternative

Filestack API

→

General-purpose file upload and transformation service outside the HubSpot ecosystem

Choose Filestack when files need to live outside HubSpot or be transformed (resize, convert) before upload.

FAQs

Specific to using Files API through Jentic.

Why is there no official OpenAPI spec for HubSpot Files?

HubSpot does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Files via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the HubSpot Files API use?

Files supports HubSpot hapikey (query), OAuth 2.0 authorization code with the files or files.ui_hidden.read scopes, and private-app legacy tokens (private-app-legacy header). Through Jentic, the configured credential is stored encrypted and injected at call time.

Can I import a file from a public URL instead of uploading bytes?

Yes. POST to /files/v3/files/import-from-url/async with the source URL; HubSpot fetches the file in the background. Poll /files/v3/files/import-from-url/async/tasks/{taskId}/status to confirm completion.

What are the rate limits for the HubSpot Files API?

Files inherits HubSpot's standard rate limits - typically 100 requests / 10 seconds for hapikey, higher under OAuth on Enterprise. File size limits depend on plan tier and are enforced at upload time with a 4xx response.

How do I get a private file URL I can share through Jentic?

Search Jentic for get a signed url for a hubspot file, load GET /files/v3/files/{fileId}/signed-url, and execute with the fileId. Jentic returns the time-limited signed URL the recipient can use without HubSpot credentials.

What is the difference between DELETE and gdpr-delete?

DELETE /files/v3/files/{fileId} performs a soft delete that can be reversed. DELETE /files/v3/files/{fileId}/gdpr-delete permanently removes the file and is the correct call for data-subject deletion requests.

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

Yes. Because you run Jentic One yourself, your own rules decide which HubSpot Files operations your agent may call and which stored credential it uses. Since the file id sits in the URL path (/files/v3/files/{fileId}/...), a rule can pin the agent to a single file so it can only replace that file or fetch its signed URL and nothing else. You choose the operation set too, so a destructive call like DELETE /files/v3/files/{fileId}/gdpr-delete stays out of reach unless you explicitly add it.

GET STARTED

Start building with Files API

Explore with Jentic One
View OpenAPI Document