How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

FINOS Application API

The Application API from FINOS — 4 operation(s) for application.

FINOS Application API is one of 34 APIs that FINOS publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Application. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and a GitHub repository.

This API exposes 4 operations across 4 paths, and defines 9 schemas. It is described by OpenAPI 3.0.1, at version 25.8.1.

Requests are made against a single base URL, youragentURL.symphony.com/agent.

4 operations 4 paths 9 schemas 1 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
25.8.1
Server
youragentURL.symphony.com/agent
Resource Areas
1

Paths & Operations 4

Across 4 paths, the API surfaces 4 operations — 1 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.

Application 4
POST
/v1/admin/app/create
Creates a new app
2 params → 200400401403500
POST
/v1/admin/app/{id}/update
Updates a app
3 params → 200400401403500
POST
/v1/admin/app/{id}/delete
Deletes a app
2 params → 200400401403500
GET
/v1/admin/app/{id}/get
Gets a app
2 params → 200400401403500

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are ApplicationDetail (9 properties), ApplicationInfo (5 properties), AppAuthenticationKey (3 properties), AppNotification (2 properties). Each schema is shown below with its type and property counts.

ApplicationInfo
object
Required information for creating an application.
5 properties
AppProperties
array
Application configuration properties that are shared with the extension application, client side. Do not store sensitive information here. Since SBE 20.14.
AppProperty
object
Application configuration property that is shared with the extension application, client side. Do not store sensitive information here.
2 properties
SuccessResponse
object
2 properties
AppAuthenticationKey
object
App RSA key information.
3 properties
ApplicationDetail
object
Detailed record of application.
9 properties
AppAuthenticationKeys
object
App RSA keys information.
2 properties
AppNotification
object
Application callback information
2 properties
Error
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

finos-application-api-openapi.yml Raw ↑

Other APIs FINOS publishes across the network.

Common Domain Model
Common Cloud Controls
FINOS Admin API
FINOS AppEntitlement API
FINOS Attachments API
FINOS AuditTrail API
FINOS CertificateAuthentication API
FINOS CertificatePod API
FINOS Connection API
FINOS Datafeed API
Where this information came from

This is an independent, third-party profile of FINOS Application API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.