![]() ![]() Learn more about API key here Libraries / SDKs Your API keys should be kept private so do not share your secret API keys. All requests made in the test environment will never hit the banking networks and will not cost you anything. Include the base64 encoded into Authorization headerĪll the API requests should be made over HTTPS instead of HTTP (all calls made over plain HTTP will fail).Encode the value above into Base64 format.Input Secret API key as username and leave the password empty.Select Basic Access Authentication or BASIC AUTH authentication.Obtain your secret API key from Dashboard.Here are the steps to authenticate your account: To authenticate your account, you have to include your secret API key in the request which can be accessed in Xendit Dashboard. We provide you API keys for both the test and live environments. You can obtain and manage your API keys in API Keys Settings. To let you explore our APIs, make sure that you have registered an account. Xendit API is organized around REST to make it cleaner and easier to understand. Include Base64 encoded value in HTTP(s) header Authorization: Basic eG5kX2RldmVsb3BtZW50X1A0cURmT3NzME9DcGw4UnRLclJPSGphUVlOQ2s5ZE41bFNmaytSMWw5V2JlK3JTaUN3WjNqdz09Og= Xnd_development_P4qDfOss0OCpl8RtKrROHjaQYNCk9dN5lSfk+R1l9Wbe+rSiCwZ3jw=:Įncode Basic Auth format above into Base64 format eG5kX2RldmVsb3BtZW50X1A0cURmT3NzME9DcGw4UnRLclJPSGphUVlOQ2s5ZE41bFNmaytSMWw5V2JlK3JTaUN3WjNqdz09Og= ![]() Input secret API key in username and leave the password empty Basic Auth format For example if your API key is xnd_development_P4qDfOss0OCpl8RtKrROHjaQYNCk9dN5lSfk+R1l9Wbe+rSiCwZ3jw= ![]() You can obtain your API keys in Dashboard. To successfully authenticate with Xendit's APIs, you must authenticate your secret API key using Basic Auth. See our Postman Guide to get started! Authentication To make it easier to get familiar with our APIs, we've published a Postman Collection so that you can see examples of all of Xendit APIs in one place. JSON is returned by all API responses, including errors. We use built-in HTTP features and HTTP verbs, which are understood by off-the-shelf HTTP clients. Our API has predictable, resource-oriented URLs, and uses HTTP response codes to indicate API errors. Use cases range from platform business to eCommerce, SaaS, and everything else in between. We help with both the money in (accepting payments) and money out (disbursing payments). Welcome! Here at Xendit, our mission is to provide payments infrastructure that helps you succeed. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |