Fund Accounting Entity Nav Extended

Description

This service API delivers CNAV-sourced NAV data, including MyNav impacts, dynamic benchmarking, extended NAV (CNAV trial), digital rates and yields, and subledger-related impacts.

Client Benefits

*The ENTITY_NAV_EXTENDED API enables clients to access extended CNAV-sourced NAV data, allowing them to review funds in scope for MyNav impacts, benchmark performance, digital rates and yields, and subledger impacts through a single, comprehensive dataset.

Data Availability

  • Daily after MyNAV approval and event 'Send data to NDS is triggered'.

Note

For additional detail on field formats and codes, please reach out to api-support@statestreet.com or your client service representative.

View Documentation

Custody Trade Status 4.0

Description

Core trade status API provides a near real-time matching, settlement (pre and post settle date), and cancellation (client or market initiated) status for all security trades (buys and sells) based upon the status in State Street’s Custody system across Sub-Custodian, CSD or ICSD. Further asset servicing trade status transparency enriched by State Street custody where applicable for lending, borrowing, collateral and other corporate action event encumbering activity leading to trade settlement issues. Availability of status of a transaction at any given time regardless of market of settlement or status of transaction.

Client Benefits

  • Access to current updates to trade status data
  • Increased efficiency and reduced query volumes through reduction of manual and email-based operations
  • Comprehensive data sets with customization and flexibility
  • Tailored API requests which allow for concise data extracts

Data Availability

  • Status of a trade is available at any given time regardless of market of settlement, or status of trade.
  • The API will provide the current status of the trade as it gets updated as part its life cycle on State Street Custody applications.
  • For example, markets where status on match to settle with counterparty is available through status received from the sub-custodian/CSD.
  • The API will provide the custody trade status data for entity IDs in which the consumer is entitled.
View Documentation

Custody Cash 4.0

Description

Set of APIs providing views of cash activity and cash balances retrievable by flexible set of parameters including account, currency and date.

Client Benefits

  • Accurate reporting of client's domestic and foreign cash balances assisting in cash management.

  • Increased efficiency and reduced query volumes through reduction of manual and email-based operations.

  • Comprehensive data sets with customization and flexibility.

  • Tailored API requests which allow for concise data extracts.

Data Availability

  • The API will provide the current custody cash available balance intra-day as it gets updated as part of its lifecycle on State Street applications.

  • The API will provide the custody cash available balance from the core authoritative source as available on State Street Custody applications.

  • The API will provide the custody cash data for entity IDs in which the consumer is entitled.

  • Net Pending Activity is not available in current release. It will default to null. Only settled balances and settled activity will be presented.

Note

For additional detail on field formats and codes, please reach out to api-support@statestreet.com or your client service representative.

View Documentation

SSGM COO Services 4.0

Description

The SSGM Operations Hub Service 4.0 API is designed to get a relatively full list of Counterparty Data. These APIs is best suited for use when there is an internal downstream APP needs some Counterparty related data.

Client Benefits

  • DIT will get the full list of the Counterparty data, so that vendor APP does not need to change regularly, so the overall efficiency is much higher *When an internal downstream APP needs some kind of Counterparty data, DIT will integrate and process the data well and then connect to the downstream APP, so that the timeline with changes will be shorter

Data Availability

  • Near real-time, 7*24 data availability
View Documentation

Universal Schema Registration and Ingestion Gateway

Overview

The Universal Schema Registration & Ingestion Gateway lets client applications register the data contracts (schemas) that describe their payloads and ingest data that is automatically validated against an approved schema before it is routed to the appropriate downstream workflow.

Schema registration is a generic, reusable capability: a schema is registered once, progresses through an approval and setup lifecycle, and once it reaches the ready-to-use state can be referenced by its schemaId from this Ingestion API as well as from any other State Street API that supports schema-based validation. Ingestion itself is specific to this service.

What this API is used for

  • Establish a strongly-typed contract between the client and State Street so that only well-formed, expected payloads are accepted.
  • Onboard a new payload format by registering a schema instead of changing and redeploying services.
  • Guarantee that every payload conforms to an agreed contract before it enters the processing pipeline, so bad data is rejected at the edge instead of failing deep inside a workflow.

APIs that depend on schema registration

Schemas registered through this API are shared across services. Consumers include: * Ingestion (POST /ingestions/{schemaId}, this service) validates every inbound payload against the referenced schema before routing it downstream. * Webhook Notifications Receiver validates inbound webhook/notification events against the registered schema identified by schemaId before they are routed for downstream processing. * Any future API that needs contract enforcement can reference a schemaId produced here instead of implementing its own validation.

Quick start

text 1. Register a schema -> POST /schemas/register -> receive schemaId 2. Wait until ready to use -> GET /schemas/{schemaId}/status (progress is also emailed to notifyEmail) 3. Ingest data -> POST /ingestions/{schemaId}

Authentication

All endpoints are protected by OAuth 2.0 client credentials. Request an access token with Basic Auth using your Client ID and Client Secret, then send the returned bearer token on every API request. Token lifetime is dynamic, with a maximum of 30 minutes.

| Environment | Token endpoint | | --- | --- | | UAT | https://api-uat.statestreet.com/oauth/accesstoken | | PROD | https://api.statestreet.com/oauth/accesstoken |

Token request settings * Method: POST * Grant type: client_credentials * Auth: Basic Auth with Client ID and Client Secret * Accept header: application/json

Example: obtain access token (UAT) bash curl --request POST \ --url "https://api-uat.statestreet.com/oauth/accesstoken" \ --header "Accept: application/json" \ --user "YOUR_CLIENT_ID:YOUR_CLIENT_SECRET" \ --data "grant_type=client_credentials"

Example: obtain access token (PROD) bash curl --request POST \ --url "https://api.statestreet.com/oauth/accesstoken" \ --header "Accept: application/json" \ --user "YOUR_CLIENT_ID:YOUR_CLIENT_SECRET" \ --data "grant_type=client_credentials"

Token response json { "access_token": "obAPdUGVlb8RCIQT7c7WR6P9.--", "scope": "read", "token_type": "Bearer", "expires_in": "1799", "status": "approved" }

Example: use access token bash curl -X POST "https://api-uat.statestreet.com/ingestions-schemas-uat/v1/schemas/register" \ -H "accept: application/json" \ -H "X-Request-Id: 99391c7e-ad88-49ec-a2ad-99ddcb1f7721" \ -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \ -H "Content-Type: application/json" \ -d '{...}'

Request headers

  • X-Request-Id (required): a client-generated UUID that uniquely identifies the request; it is echoed back as requestId and used for end-to-end tracing.
  • Content-Type: application/json for JSON, application/xml for XML, or application/iso20022 for ISO 20022 XML payloads.

Error handling

Errors are returned with the appropriate HTTP status and a consistent JSON body: json { "requestId": "99391c7e-ad88-49ec-a2ad-99ddcb1f7721", "traceId": "0123456789abcdef", "code": "BAD_REQUEST", "message": "Human-readable description of what went wrong" } Common status codes: 400 (validation/payload error), 401 (missing or invalid token), 403 (not authorized for this client/schema), 404 (unknown schemaId), 413 (payload too large), 415 (unsupported media type), 429 (rate limited), and 5xx (service errors).

Capabilities

POST /schemas/register

Register a new schema and receive a schemaId. For JSON, include the full JSON Schema as an escaped string in schema; for ISO20022, omit schema (payloads are validated against the standard ISO 20022 message definitions). Registration is asynchronous — track progress via notifyEmail or GET /schemas/{schemaId}/status.

Sample request body (JSON schema): json { "schemaType": "JSON", "notifyEmail": "user@example.com", "schema": "{\"$schema\":\"http://json-schema.org/draft-07/schema#\",\"type\":\"object\",\"required\":[\"batchId\",\"records\"],\"properties\":{\"batchId\":{\"type\":\"string\"},\"records\":{\"type\":\"array\"}}}" }

Sample request body (ISO 20022 — no schema): json { "schemaType": "ISO20022", "notifyEmail": "user@example.com" }

Sample response (201 Created): json { "requestId": "99391c7e-ad88-49ec-a2ad-99ddcb1f7721", "traceId": "0123456789abcdef", "schemaId": "e6ff6721-48f6-4090-848b-d13b2ebb5c36", "schemaType": "JSON", "status": "received" }

curl: bash curl -X POST "https://integrationservices-dev.statestr.com/extsvcs/api/v1/schemas/register" \ -H "Authorization: Bearer $ACCESS_TOKEN" \ -H "X-Request-Id: 99391c7e-ad88-49ec-a2ad-99ddcb1f7721" \ -H "Content-Type: application/json" \ -d '{ "schemaType": "JSON", "notifyEmail": "user@example.com", "schema": "{\"$schema\":\"http://json-schema.org/draft-07/schema#\",\"type\":\"object\",\"required\":[\"batchId\",\"records\"]}" }'

GET /schemas/{schemaId}/status

Returns the current lifecycle state of a registered schema. Poll this until status is ready_for_use before referencing the schemaId for ingestion.

Sample response (200 OK): json { "requestId": "99391c7e-ad88-49ec-a2ad-99ddcb1f7721", "traceId": "0123456789abcdef", "schemaId": "e6ff6721-48f6-4090-848b-d13b2ebb5c36", "schemaType": "JSON", "status": "ready_for_use" }

curl: bash curl -X GET "https://integrationservices-dev.statestr.com/extsvcs/api/v1/schemas/e6ff6721-48f6-4090-848b-d13b2ebb5c36/status" \ -H "Authorization: Bearer $ACCESS_TOKEN" \ -H "X-Request-Id: 99391c7e-ad88-49ec-a2ad-99ddcb1f7721"

POST /ingestions/{schemaId}

Submits a payload that is validated against the schema referenced by schemaId and, on success, routed to the client-specific workflow. The schemaId must be ready_for_use. Send JSON, XML, or ISO 20022 XML using the matching Content-Type.

Sample request body (JSON): json { "clientReferenceNumber": "crn24fsuaaau9hh", "payload": { "batchId": "BATCH-20250917-001", "asOfDate": "2025-09-17", "records": [ { "instrumentId": "ABC123", "quantity": 1000, "currency": "USD" } ] } }

Sample response (201 Created): json { "requestId": "99391c7e-ad88-49ec-a2ad-99ddcb1f7721", "traceId": "0123456789abcdef", "message": "Ingestion Request Processed" }

curl: bash curl -X POST "https://integrationservices-dev.statestr.com/extsvcs/api/v1/ingestions/e6ff6721-48f6-4090-848b-d13b2ebb5c36" \ -H "Authorization: Bearer $ACCESS_TOKEN" \ -H "X-Request-Id: 99391c7e-ad88-49ec-a2ad-99ddcb1f7721" \ -H "Content-Type: application/json" \ -d '{ "clientReferenceNumber": "crn24fsuaaau9hh", "payload": { "batchId": "BATCH-20250917-001", "asOfDate": "2025-09-17", "records": [ { "instrumentId": "ABC123", "quantity": 1000, "currency": "USD" } ] } }'

POST /schemas/upgrade

Links a newer schema as the override for an existing schema so contracts can evolve without breaking live integrations. The new schema is marked as pending and the old schema remains active until confirmation.

Client benefits

  • One standardized API for schema registration and ingestion.
  • Flexible format support.
  • Dedicated dev, uat and production environments with separate URLs.
  • Email notifications at every step of the registration lifecycle.

Data availability

  • Data in DEV/UAT may be purged periodically and must not be treated as permanent storage.
  • Updates and processing occur in near real-time across all environments.
  • Production ingestion is monitored to ensure high reliability and availability.
View Documentation

Agent Forge Service

Description

Agent Forge is an end-to-end platform dedicated to empowering organizations with intelligent, ready-to-use AI agents and automation tools. The core service of Agent Forge is to connect users with a curated ecosystem of AI agents that can be seamlessly integrated into business processes, driving efficiency, innovation, and scalability.

Client Benefits

Benefits include:

  • Comprehensive agent lifecycle management from creation to deployment

  • Curated marketplace of pre-built AI agents for various business functions

  • Seamless integration with existing business applications and workflows

  • Advanced evaluation and monitoring capabilities for agent performance

  • Enterprise-grade security with OAuth2 authentication and role-based access

  • Scalable infrastructure supporting multi-tenant deployments

Data Availability

The platform provides reliable access to agent management capabilities with comprehensive metadata including trace IDs, approval workflows, performance metrics, and audit trails to ensure transparency and governance compliance.

View Documentation

Swap Trade

Description

  • This API facilitates the real-time distribution of Equity Swap Regulatory Reporting data, Allocation Confirmations, Pending Swap , Allege Accept Reject, Reg Trade Position Amendment and Realtime Alerts data from the NuvoPrime trade booking system to downstream platforms such as Traiana and Regulatory Reporting systems, via the FCO platform.
  • It processes JSON-formatted Equity Swap data from NuvoPrime, stores it in FCO for traceability, and then publishes it to the appropriate downstream systems.
  • This API is exclusively intended for use by Nuvo Prime. It is a custom implementation designed to align with the data format standards used by both upstream and downstream systems.

Data Flow Overview: * NuvoPrime → FCO API → Traiana’s Harmony give-up platform * NuvoPrime → FCO API → Regulatory Reporting platform

Client Benefits

  • This allows self-service for initiation for requests.
  • This facilitates the ingestion of Equity Swap data from external system.

Data Availability

  • Available in both UAT and Production environments.
  • Supports near real-time data updates.
View Documentation

IMS West Breaks Transition.

Description

IMS West Breaks Transition API offers client ability to retrieve Transition related Breaks information based on Account numbers. Client can request IMS West system to retrieve all the data captured as part of the break tracker for one or multiple accounts.

Client Benefit

  • Time savings and elimination of email manual follow ups.

  • Provides transparency on account setup to client.

  • Eliminated manual touch points to reduces risk.

Data Availability

  • Near real-time transparency to client for accountable actions (eliminating emails and phone calls) by accessing data in workflow tool.

  • Streamlined workflows across various teams at IMS and client.

View Documentation

IMS West New Separate Account Transition Checklist.

Description

IMS West Separate Account Transitions Checklist API offers client ability to provide data from New Separate Account transition checklist process.

IMS Transition Associate completes the information in the New Separate Account Transition checklist process and the data is retrieve by client via this API.

Client Benefit

  • Time savings and elimination of email manual follow ups.

  • Provides transparency on account setup to client.

  • Eliminated manual touch points to reduces risk.

Data Availability

  • Real time transparency to client for accountable actions (eliminating emails and phone calls) by accessing data in workflow tool.

  • Streamlined workflows across various teams at IMS and client.

View Documentation

DynamicSQL Management Service

Description

The DynamicSQL Management Service provides comprehensive application lifecycle management capabilities for text-to-SQL applications. It enables users to request new applications, manage configurations, handle approvals, and validate entitlements and RAI client credentials.

Client Benefits

Benefits include:

  • Streamlined application onboarding and approval workflows

  • Comprehensive application configuration management

  • Entitlement validation and security controls

  • RAI client credential validation

  • Application lifecycle management from request to production

Data Availability

The service ensures reliable access to application metadata, configurations, and approval status with support for filtering and pagination.

View Documentation