FyleHub API Documentation
REST API reference for institutional financial data operations. Query normalized financial data, configure pipelines, manage destinations, and receive webhook notifications.
API Overview
FyleHub's REST API enables programmatic access to all platform capabilities — from querying normalized financial data to managing pipelines and receiving real-time notifications. The API uses standard REST conventions with JSON request and response bodies.
- ›
Base URL: https://api.fylehub.com/v1 - ›
Authentication: API key (Bearer token) - ›
Format: JSON request and response bodies - ›
Versioning: URL-based (v1, v2) - ›
Rate limits: Configurable per client - ›
TLS 1.3 required for all requests
Quick Start
# Get all holdings for a portfolio
curl https://api.fylehub.com/v1/data/holdings \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-G -d "portfolio_id=PORT123" \
-d "as_of_date=2026-01-31"
# Response
{
"holdings": [...],
"as_of_date": "2026-01-31",
"total_market_value": 1250000000,
"source": "BNY Mellon",
"last_updated": "2026-02-01T06:00:00Z"
}
API Reference
Authentication
- POST/auth/token
- POST/auth/refresh
- DELETE/auth/token
Data Sources
- GET/sources
- GET/sources/{id}
- POST/sources
- PUT/sources/{id}
- DELETE/sources/{id}
Financial Data
- GET/data/holdings
- GET/data/transactions
- GET/data/performance
- GET/data/nav
- GET/data/positions
Pipelines
- GET/pipelines
- GET/pipelines/{id}
- POST/pipelines/{id}/run
- GET/pipelines/{id}/runs
Destinations
- GET/destinations
- POST/destinations
- PUT/destinations/{id}
- DELETE/destinations/{id}
Webhooks
- GET/webhooks
- POST/webhooks
- DELETE/webhooks/{id}
- POST/webhooks/{id}/test
Audit
- GET/audit/events
- GET/audit/events/{id}
- GET/audit/summary
Full API Documentation
Complete API reference, SDKs, code samples, and interactive API explorer are available to FyleHub clients after onboarding. Book a demo to see the full developer documentation.
Request Full API AccessSandbox environment available. SDKs in Python, JavaScript, and Java.
Frequently Asked Questions
QWhat authentication does FyleHub's API use?
FyleHub uses API key authentication for programmatic access, with OAuth 2.0 available for enterprise clients requiring SSO integration. All API requests require HTTPS. API keys are scoped by permission level — read-only, read-write, or admin — and can be rotated without service interruption.
QDoes FyleHub provide webhooks for real-time notifications?
Yes. FyleHub supports webhooks for delivery notifications, data quality alerts, and pipeline status changes. Webhook endpoints are configured per event type and can deliver to any HTTPS endpoint. Webhook payloads include delivery metadata, data quality metrics, and links to the FyleHub audit trail.
QCan I query FyleHub's normalized financial data via API?
Yes. FyleHub's Data Query API allows programmatic access to normalized financial data — holdings, transactions, NAV, performance, and other data types — using a consistent REST API regardless of source. This eliminates the need to integrate directly with each custodian's proprietary API.
QIs there a sandbox environment for development and testing?
Yes. FyleHub provides a sandbox environment with synthetic financial data for development and testing. The sandbox mirrors the production API, allowing integrations to be built and tested without requiring live custodian connections.
Build on Top of FyleHub
FyleHub's API turns institutional financial data operations into a programmatic capability. Book a demo to see the full developer platform.
Sandbox environment available. SDKs in Python, JavaScript, and Java.