patchBay

Liquidity Provider Server vs ${title}

If you need a Development API that's easy to integrate, go with ${title}.

Liquidity Provider Server

API discovered from rsksmart/liquidity-provider-server

${title}

API discovered from aws-solutions-library-samples/guidance-for-iso20022-messaging-workflows-on-aws

Liquidity Provider Server

  • HTTPS supported
  • Requires No authentication
  • Currently flagged as inactive

${title}

  • Simple API key authentication
  • HTTPS supported
FeatureLiquidity Provider Server${title}
AuthenticationNoapiKey
HTTPSYesYes
CORSUnknownUnknown

When to use which?

Both Liquidity Provider Server and ${title} offer similar capabilities as Development APIs. Review their documentation to find the best fit for your specific use case.