Troubleshooting

This page lists some problems you might encounter while using Liquidity Hub and instructions on troubleshooting them.

If you need more assistance, please raise a ticket in our support portal.

Using the Liquidity Hub API

I didn't record my client ID or client secret after creating my API credential. How can I find them?

To find the client ID of an existing credential, see Access an existing API credential.

You can't find the client secret associated with an existing API credential because it's displayed only when the credential is created. You must rotate this credential or create a new credential.

I get a 401 error code from the authentication endpoint. What do I do?

The endpoint was probably unable to validate the client ID and client secret information you provided. This could mean that one or both of the client ID and client secret strings have the incorrect number of characters. The client ID should be 32 characters long, and the client secret should be 64 characters long. Check this information and retry the request.

My API request returned a 400 error. What do I do?

The request body was probably malformed. Fix any errors in the request body and retry the request.

My API request to the POST /oauth/token operation returned a 401 error. What do I do?

This likely means that the value of the clientId and/or clientSecret field is incorrect. Verify that you have the correct values for these fields in the request body and retry the request.

My API request returned a 401 error. What do I do?

You probably don't have the permission to access the resource you requested. This can happen if your Bearer authentication token is either not valid or expired.

First, you can attempt to address expiration by requesting and using a new token. Second, you can inspect the token used in your request to confirm that it is not being truncated or modified in in any unexpected way.

My API request returned a 403 error. What do I do?

The base URL in your request is probably wrong. Verify that you are using the base URL specified in the Liquidity Hub API reference and retry the request.

My API request returned a 404 error. What do I do?

The resource you requested probably does not exist. Check the path used in your URL for accuracy. Common errors include pluralizations, extra slashes, and missing path elements.

I'm repeatedly getting 500 errors from the API. What do I do?

If you are receiving 500-range errors in response to multiple API requests, please raise a ticket in our support portal.

I can reach the API via Postman or cURL, but my middleware is getting an insecure request error. Why is this happening?

Your middleware might be blocked by SSL validation failures because the expected Liquidity Hub API cert chain is missing. Your Postman or cURL commands may succeed because they allow insecure requests (for example, using curl -k). For your middleware to securely connect, add the cert chain for Liquidity Hub API in your cert store, whether that's a Java keystore, the system trust store, or elsewhere.

I'm getting a timeout when I call the API. What do I do?

Inspect the details of your request by enabling verbose logging. For example, use the curl -v command to make a test request. If there is an issue, the process will pause for a while or stop when the issue occurs. For example, you may see a DNS resolution error or that the process is awaiting a response from the Liquidity Hub server.