Why do I receive the error HTTP 400 – SERVICE_INVALID – "The addressed service is not valid." (Couldn't find 'Solaris::PartnerConfiguration' for id 'XXX')?

Cause

This error occurs when the value provided in the request header

X-Custom-Property-Partner-Id

does not match any active partner configuration in the targeted environment (LIVE or Sandbox).

In other words, the Solaris XS2A API cannot find a valid PartnerConfiguration for the given Partner ID. As a result, the request is rejected with:

HTTP 400
code: SERVICE_INVALID
title: The addressed service is not valid.

This typically happens if:

• The Partner ID has been deactivated.

• The Partner ID is no longer supported via the Solaris PSD2 interface.

• An outdated Partner ID is being used.

• The Partner ID exists in a different environment (e.g. Sandbox vs LIVE).

• There is a typo in the header value.

Solution

To resolve the issue:

1. Verify that the X-Custom-Property-Partner-Id header contains the correct and up-to-date Partner ID.

2. Ensure you are sending the request to the correct environment (LIVE or Sandbox).

3. Retrieve the current list of available partners by calling:

GET /psd2/partners

in the respective environment.

Regularly validating the Partner ID against the /psd2/partners endpoint helps prevent this error.