API Hub

The API Hub provides access to Thredd's API suite using a single URL. You can access services across all environments using this single URL, which will then send you automatically to the correct service and environment. Using a single URL provides you with a single, consistent interface for accessing the Thredd platform, simplifying integration and enabling seamless scalability.

The below diagram shows some of the different services that API Hub connects to:

  • Card management enables you to create and manage cards

  • Event delivery service enables you to use Thredd's webhooks, enabling you to send notifications to your customers

  • Digital wallets enables you to set up Google and Apple In-App Push Provisioning

API Hub

Figure: Diagram displaying some of the different services available for the API Hub

Connecting to the API Hub

Thredd's Secure Connectivity Framework is used to secure access to the API Hub. The main components of the Secure Connectivity Framework are:

  • Cloudentity - a Software as a Service (SaaS) capability which acts as the Identity Provider (IDP) for Thredd’s interfaces (including the Thredd Certificate Authority and Thredd Portal), and as an OAuth OpenID Provider (OP) for the registration and management of customer applications, generation and validation of access tokens, and for the enforcement of access control policies.

  • Thredd Certificate Authority or Thredd CA - a SaaS capability for the creation and management of certificates:

    • Transport Certificates — for establishing secure connections between resources.

    • Signing Certificates — for the creation of signed messages, used for authentication of clients, and non-repudiation and authentication of notifications.

    • Encryption Certificates — for the encryption of payloads using an asymmetric encryption approach.

  • mTLS Termination - on-premise infrastructure enabling the establishment of Trust Chains when clients present Thredd-issued Transport Certificates at the point of attempting to connect to protected resources.

For more information on the Secure Connectivity Framework, see Connecting to Thredd Guide. For more information on using the Secure Connectivity Framework for API Hub, see Accessing the API Hub with mTLS.

API Version Differences

The following table details some of the main differences between our different API products.

Functionality

API Hub (V2.0)

Cards API (V1.0)

Web Services (SOAP)

Cards Management

Yes

Yes

Yes

Digital Channel Services

Yes

No

No

Webhooks

Yes

No

No

For more information on the API Hub, including detailed information on the endpoints included, see the API Hub guide.