FinSpace Public API

Name: FinSpace Public API API
Brand: FinSpace Public API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentFinanceAccountingapiKey31 EndpointsREST

For Agents

Manage datasets, changesets, dataviews, users, and permission groups inside FinSpace environments through a single data API.

Connect the FinSpace Public API to your agent

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

Install Jentic One Beta (Self-Hosted)

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

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 FinSpace Public API API.

Create and version datasets with structured schemas and ownership metadata

Load data through changesets that append, replace, or modify dataset contents

Materialise dataviews that snapshot dataset contents for downstream queries

Create and manage permission groups that scope dataset access for users

GET STARTED

Start building with FinSpace Public API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for FinSpace Public API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for the FinSpace Public API, keeping it validated and agent-ready. The FinSpace Public API manages financial datasets and data access inside an existing FinSpace environment. The API covers datasets, changesets, dataviews, users, and permission groups so that platform teams can load market data, version it across changesets, and grant scoped access to research desks. It is built for capital markets data engineering teams that need to operate the data plane of FinSpace through automation rather than the FinSpace UI.

Use Cases

Patterns agents use FinSpace Public API API for, with concrete tasks.

★ Market Data Loading and Versioning

Capital markets data teams use the FinSpace Public API to land daily and intraday market data into versioned datasets. Each load is a changeset, so the dataset history is auditable and reproducible for backtests and regulatory queries. The API supports append, replace, and modify changeset modes for full and incremental loads.

Create a changeset on dataset eod-prices in change type APPEND, sourced from s3://market-data/eod/2026-06-09/.

Dataview Materialisation for Research

Quant research teams use dataviews to materialise a stable snapshot of a dataset at a specific changeset, suitable for backtest reproducibility. The API creates and lists dataviews so notebooks and pipelines can pin to a known data state. Dataview creation is asynchronous; the API exposes status fields for polling.

Create a dataview on dataset eod-prices pinned to changeset id cs-456 with auto-update disabled.

Permission Group Management

Platform governance teams use permission groups to grant scoped access to FinSpace datasets per desk or project. The API creates groups, adds and removes users, and lists membership so identity workflows can be automated and audited. This avoids manual permission edits inside the FinSpace console.

Create a permission group named rates-desk and add user with id u-789 to that group.

Agent-Driven FinSpace Data Operations via Jentic

AI agents use the FinSpace Public API through Jentic to ingest data, materialise dataviews, and manage user access in response to upstream events. Jentic exposes FinSpace data operations as discoverable tools so an agent can search by intent and execute the matching call. This lets data agents handle routine load and access requests without operator intervention.

Search Jentic for create finspace changeset, load the CreateChangeset schema, and execute it for dataset trades-tick with source path s3://feeds/trades/2026-06-09.

Key Endpoints

31 endpoints — jentic publishes the only available openapi specification for the finspace public api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/datasetsv2

Create a FinSpace dataset

GET

/datasetsv2

List datasets in the environment

POST

/datasets/{datasetId}/changesetsv2

Create a changeset on a dataset

POST

/datasets/{datasetId}/dataviewsv2

Create a dataview on a dataset

POST

/permission-group

Create a permission group

POST

/permission-group/{permissionGroupId}/users/{userId}

Add a user to a permission group

POST

/user

Create a FinSpace user

POST

/datasetsv2

Create a FinSpace dataset

GET

/datasetsv2

List datasets in the environment

POST

/datasets/{datasetId}/changesetsv2

Create a changeset on a dataset

POST

/datasets/{datasetId}/dataviewsv2

Create a dataview on a dataset

POST

/permission-group

Create a permission group

Why though Jentic?

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

Credential isolation

AWS and FinSpace user credentials are stored encrypted in the Jentic vault. Agents receive scoped, short-lived access — raw secret access keys and FinSpace tokens never enter the agent context.

Intent-based discovery

Agents search by intent (for example load market data into finspace) and Jentic returns matching FinSpace operations with their input schemas, so the agent can call the right endpoint without browsing AWS docs.

Time to first call

Direct FinSpace integration: 2-3 days for SigV4 signing, FinSpace credential issuance, and changeset polling. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

FinSpace User Environment Management

Provisions the FinSpace environments that this Public API operates inside

Choose finspace when the task is to create, update, or delete the FinSpace environment that hosts datasets.

Complementary

Amazon SageMaker

Trains and deploys models on FinSpace dataviews

Choose SageMaker when downstream of dataview materialisation you need to train or serve a model.

Complementary

AWS Lambda

Runs custom transformation logic before changeset loads

Choose Lambda when source data needs transformation before being staged for a FinSpace changeset.

FAQs

Specific to using FinSpace Public API API through Jentic.

Why is there no official OpenAPI spec for the FinSpace Public API?

AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call the FinSpace Public API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the FinSpace Public API use?

FinSpace uses AWS Signature Version 4 request signing, with FinSpace user credentials issued by the GetProgrammaticAccessCredentials operation. Through Jentic, both AWS and FinSpace credentials are stored encrypted in the vault.

Can I load data into a dataset with this API?

Yes. POST /datasets/{datasetId}/changesetsv2 creates a changeset that loads or modifies dataset contents. The change type field accepts APPEND, REPLACE, or MODIFY to control how the new data interacts with existing changesets.

What are the rate limits for the FinSpace Public API?

AWS applies per-account, per-region throttling. Mutating calls such as CreateChangeset are throttled more aggressively than List and Get calls. Use exponential backoff on ThrottlingException responses; AWS does not publish exact TPS numbers in the spec.

How do I add a user to a permission group through Jentic?

Search Jentic for add user to finspace permission group, load the schema for POST /permission-group/{permissionGroupId}/users/{userId}, and execute it with the group and user IDs. Jentic returns the membership status.

Does this API create FinSpace environments?

No. Environment lifecycle is in the separate FinSpace User Environment Management service (finspace). This Public API operates within an existing environment.