Quantum Ideas Portal
Welcome to the FIS Treasury and Risk Manager - Quantum Edition Aha! Ideas Portal.

By visiting this portal, you will be able to contribute towards the evolution of the Quantum solution through interactions with other Quantum users, FIS trusted partners and FIS staff from around the world. Each Portal User receives 5 votes. Each user is allowed 1 vote per idea. Votes are reset when an idea is in a final state i.e. Shipped (delivered in the product).

Users will receive weekly email updates that highlight new activity. Users will receive emails for their created ideas when:

  • Status changes

  • Comment changes

Be aware that when you post content, other community members will see your name. FIS is not responsible for content posted by other Aha! Ideas Portal Users.

Add a new idea Subscribe
Status Needs review
Created by Graham Brien
Created on Feb 12, 2025

RELATED IDEAS

Computershare would like to connect with an external JPMM RFQ API from Quantum.



This is a Restful API with 2 level authentication

  1. Bearer Token

  2. Certificate

  1. Bearer token – requires the following key pair information to be passed in the body of the request:

  • grant_type

  • client_secret

  • aud

  • client_id

See "Access FX API 2.0 Spec"

Quantum does not currently support the grant_type property in an oAuth request.

See "JPM Token"

We have tried with authentication = NONE and a custom template, but then we get an error that the header is missing – which we cannot configure in Quantum.

Using a separate Header template does not appear to work, and is not recognised – unless we specify an authentication method of oAuth, but then we cannot specify the grant_type.

  1. Certificate- once we retrieve the Bearer token, then a public certificate must be passed in the header when requesting a certificate and any subsequent requests.

We believe that Certificate level authentication is supported by Quantum, however unsure if it will be possible to include the bearer token in the header of the request having not been able to get passed I.

Access FX API 2...
Access FX API 2.0 spec.png
Open full size
Access FX API 2.0 spec.png
  • Attach files
  • Admin
    Mark Zumbraegel
    Reply
    |     Feb 26, 2025

    Hi there,

    Is there a document describing connection details? We can see a certificate is required after getting the bearer token, but there is not enough information to determine if we support this already or no.