Third Party Provider

Once your onboarding application is processed, you will be able to update some fields in your TPP profile.

Note

All these endpoints require authentication, see the authentication documentation for the full list of headers required for these endpoints.

GET /api/v2/third-party-provider/(string:tpp_client_id)/

Retrieves the TPP associated to the tpp_client_id.

Example response:

HTTP/1.1 200 OK
Vary: Accept
Content-Type: application/json

{
    "client_id": "d83da416-2f23-4f74-b366-c2682494f3f5",
    "name": "Example Organization v2",
    "allowed_redirect_uris": ["https://example.com/callback", "example://callback"]
}

Request Headers:

• Host: Must be psd2.holvi.com

• Date: Must follow the format described in section 7.1.1.1 of RFC 7231

• Signature: See authentication documentation for more details

• X-Holvi-Client-Id: Client ID provided by Holvi

• X-Holvi-Client-Secret: Client secret provided by Holvi

• Authorization: JWT token to authenticate

Response Fields:

• client_id: Client id of the TPP

• name: Name of the TPP

• allowed_redirect_uris: Redirection URIs allowed in the user login

---

PUT /api/v2/third-party-provider/(string:tpp_client_id)/

Updates the TPP associated to the tpp_client_id.

Example request:

POST /api/v2/third-party-provider/4bae5812c969c0ea5c2453b60c2ee3fa/ HTTP/1.1
Accept: application/json

{
    "name": "Example Organization",
    "allowed_redirect_uris": ["https://example.com/callback", "example://callback"]
}

Example response:

HTTP/1.1 200 OK
Vary: Accept
Content-Type: application/json

{
    "client_id": "d83da416-2f23-4f74-b366-c2682494f3f5",
    "name": "Example Organization v2",
    "allowed_redirect_uris": ["https://example.com/callback", "example://callback"]
}

cURL command:

curl -X PUT \
  -H "Content-Type: application/json" \
  -d '{"name":"Example Organizatio","allow_redirect_uris": ["https://example.com/callback", "example://callback"]}' \
  https://psd2.holvi.com/api/v2/third-party-provider/4bae5812c969c0ea5c2453b60c2ee3fa/

Parameters

• tpp_client_id: TPP client id can be retrieved from

Request Headers:

• Host: Must be psd2.holvi.com

• Date: Must follow the format described in section 7.1.1.1 of RFC 7231

• Signature: See authentication documentation for more details

• X-Holvi-Client-Id: Client ID provided by Holvi

• X-Holvi-Client-Secret: Client secret provided by Holvi

• Authorization: JWT token to authenticate

Status Codes:

• 200: TPP info successfully updated

• 400: Invalid input

• 404: TPP with tpp_client_id not found