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

FDC3 Application API

The Application API from FDC3 — 5 operation(s) for application.

FDC3 Application API is one of 6 APIs that FDC3 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.

This API exposes 5 operations across 5 paths, and defines 45 schemas. It is described by OpenAPI 3.0.0, at version 2.1.

Requests are made against a single base URL, /appd.

5 operations 5 paths 45 schemas 4 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
2.1
Base URL
https://fdc3.finos.org
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

FDC3 Application API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

Paths & Operations 5

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

Application 5
GET
/v2/apps/{appId}
Retrieve an application definition
1 param → 200400403500
GET
/v2/apps
Retrieve all application definitions
→ 200400403500
GET
/v1/apps/{appId}deprecated
Retrieve an application definition
1 param → 200400403500
POST
/v1/appsdeprecated
Create a new application definition
body → 200400403500
GET
/v1/apps/searchdeprecated
Retrieve a list of applications based on parameters provided. Depending on implementation, parameter values should self describe search format and type (e.g. Regex)
9 params → 200400403500

Schemas 45

The contract defines 45 schemas that model the data the API accepts and returns. The most detailed are BaseApplication_2 (19 properties), BaseApplication (19 properties), Application_3 (15 properties), ApplicationV1 (15 properties). Each schema is shown below with its type and property counts.

Screenshot
object
Images representing the app in common usage scenarios
4 properties 1 required
LaunchDetails
The type specific launch details of the application. These details are intended to be vendor-agnostic and MAY be duplicated or overridden by details provided i…
IntentV1
object
(Deprecated v1 API version) An intent definition as defined by spec https://github.com/FDC3/Intents/blob/main/src/Intent.yaml
4 properties 1 required
AppImageV1
object
App Image holder
1 property
ErrorDTO
object
2 properties
HostManifests
object
A mapping from host name to a host-specific application manifest object or URI from which that manifest can be retrieved. The manifest should provide details r…
WebAppDetails
object
Properties used to launch apps with type: web.
1 property 1 required
NativeAppDetails
object
Properties used to launch apps with type: native that are already installed on the device.
2 properties 1 required
OtherAppDetails
Apps with type: other are defined by a hostManifest and do not require other details.
ApplicationV1
object
(Deprecated v1 API version) Defines an application retrieved from an FDC3 App Directory, which can then be launched. Launching typically means running for a us…
15 properties 4 required
LocalizedVersions
object
Provides localized alternatives to any field of the AppD record, which may also refer to an alternative version of the application that is also localized (e.g.…
BaseApplication
object
19 properties
Icon
object
Icon holder
3 properties 1 required
ApplicationSearchResponseV1
object
2 properties
NameValuePair
object
Simple name value pair
2 properties
OnlineNativeAppDetails
object
Properties used to launch a native apps with type: onlineNative that have an online launcher, e.g. online ClickOnce app deployments.
1 property 1 required
Interop
object
Metadata that describes how the application uses FDC3 APIs. This metadata serves multiple purposes: - It supports intent resolution by a desktop agent, by decl…
3 properties
CitrixAppDetails
object
Properties used to launch apps virtualized apps with type: citrix.
2 properties 1 required
HostManifest
object
Object containing all host specific properties.
AllApplicationsResponse
object
2 properties
Application
Defines an application retrieved from an FDC3 App Directory, which can then be launched. Launching typically means running for a user on a desktop. The details…
4 required
IconV1
object
(Deprecated v1 API version) Icon holder
1 property
Type
string
The technology type that is used to launch and run the application. Each application type implies a particular set of launch details. The supported types inclu…
Intent
object
Definition of an intent that an app listens for
4 properties 1 required
LaunchDetails_2
The type specific launch details of the application. These details are intended to be vendor-agnostic and MAY be duplicated or overridden by details provided i…
WebAppDetails_2
object
Properties used to launch apps with type: web.
1 property 1 required
NativeAppDetails_2
object
Properties used to launch apps with type: native that are already installed on the device.
2 properties 1 required
OtherAppDetails_2
object
Apps with type: other are defined by a hostManifest and do not require other details.
OnlineNativeAppDetails_2
object
Properties used to launch a native apps with type: onlineNative that have an online launcher, e.g. online ClickOnce app deployments.
1 property 1 required
CitrixAppDetails_2
object
Properties used to launch apps virtualized apps with type: citrix.
2 properties 1 required
Screenshot_2
object
Images representing the app in common usage scenarios
4 properties
LaunchDetails_3
The type specific launch details of the application. These details are intended to be vendor-agnostic and MAY be duplicated or overridden by details provided i…
ApplicationSearchResponse
object
2 properties
Intent_3
object
Definition of an intent that an app listens for
4 properties 1 required
LocalizedVersions_2
object
Provides localized alternatives to any field of the AppD record, which may also refer to an alternative version of the application that is also localized (e.g.…
BaseApplication_2
object
19 properties
Icon_3
object
Icon holder
1 property
Interop_2
object
Metadata that describes how the application uses FDC3 APIs. This metadata serves multiple purposes: - It supports intent resolution by a desktop agent, by decl…
3 properties
AllApplicationsResponse_2
object
2 properties
Application_2
Defines an application retrieved from an FDC3 App Directory, which can then be launched. Launching typically means running for a user on a desktop. The details…
4 required
Application_3
object
Defines an application retrieved from an FDC3 App Directory, which can then be launched. Launching typically means running for a user on a desktop. The details…
15 properties 4 required
Type_2
string
The technology type that is used to launch and run the application. Each application type implies a particular set of launch details. The supported types inclu…
Icon_2
object
Icon holder
3 properties
AppImage
object
App Image holder
1 property
Intent_2
object
An intent definition as defined by spec https://github.com/FDC3/Intents/blob/main/src/Intent.yaml
4 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

fdc3-application-api-openapi.yml Raw ↑

Other APIs FDC3 publishes across the network.

FDC3 Desktop Agent API
FDC3 App Directory API
FDC3 Context Data
FDC3 Intents
FDC3 Desktop Agent Bridging
Where this information came from

This is an independent, third-party profile of FDC3 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.