To avoid CORS blocking, whitelist the origin domain for production environments by providing a set of approved domains to Murf.
Articles on: API
Even if you've obtained an
api-key
, there can be instances where your requests are being blocked due to CORS. For development and testing,
localhost:3000
is whitelisted by default, requests can be sent from there. For production environments, make sure the origin domain is approved as a request origin by Murf. You can provide a set of domains and they will be approved for use by Murf.
While it is possible to build workflows that access Murf API from the browser, we recommend the usage of server-side languages to integrate Murf API into your business logic.
Updated on: 16/05/2023
Even if you've obtained an
api-key
, there can be instances where your requests are being blocked due to CORS. For development and testing,
localhost:3000
is whitelisted by default, requests can be sent from there. For production environments, make sure the origin domain is approved as a request origin by Murf. You can provide a set of domains and they will be approved for use by Murf.
While it is possible to build workflows that access Murf API from the browser, we recommend the usage of server-side languages to integrate Murf API into your business logic.
Updated on: 16/05/2023
Updated on: 16/05/2023
Thank you!