You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello!
We are in the process of integrating the Mithril Aggregator API into the Blockfrost API. We would like our users to be able to use the official mithril-client with custom URL pointing to our proxy for Mithril API. However, to access Blockfrost endpoints, users need to authenticate by sending a header with their API key. For this, we need a way to add a custom header to requests sent by mithril-client. Additionally, this could be also useful to control caching or to set a custom user-agent to make monitoring a little bit easier.
Would it be possible to expose access to the headers sent by mithril-client, perhaps by allowing a headers object to be passed during client initialization? We’ll gladly submit a PR to implement this feature.
Thank you!
The text was updated successfully, but these errors were encountered:
Hello!
We are in the process of integrating the Mithril Aggregator API into the Blockfrost API. We would like our users to be able to use the official mithril-client with custom URL pointing to our proxy for Mithril API. However, to access Blockfrost endpoints, users need to authenticate by sending a header with their API key. For this, we need a way to add a custom header to requests sent by mithril-client. Additionally, this could be also useful to control caching or to set a custom user-agent to make monitoring a little bit easier.
Would it be possible to expose access to the headers sent by mithril-client, perhaps by allowing a headers object to be passed during client initialization? We’ll gladly submit a PR to implement this feature.
Thank you!
The text was updated successfully, but these errors were encountered: