Welcome to Wyre. You've found yourself trying to integrate with Wyre, but don't know where to start. This article will explain how to create a production account with Wyre and how obtain API Keys to access our API.

Terms

  • Partner - Any business entity that wants to integrate with Wyre
  • Users - An end-user of a Partner account.

How to Create a Partner Account

When a Partner wants to integrate with our product, the best way to create an account and try our API (before going to a production environment) is through our test environment. In order to create a test account, please sign up for test dashboard.

  1. Click on business account and sign up.
  2. Use an email address and password you will remember to log in
  3. No need to submit real KYC data (Phone number gets auto approved)
  4. For bank account info, click "Chase" 
  5. Enter bank details: 
  6. username: user_good
  7. password: pass_good

Once your test account is created, you can access your account id  by logging into our test dashboard. You can then generate API keys to access your account by clicking on the "Your Account" tab, then look for the API Keys tab. Click on the API Keys Tab.


Or access the API Keys tab here. From the API Keys tab, you can then generate API Keys and Secret Tokens by clicking on the "ADD API KEY" Button.


Insert a description for the keys. You can also leave the IP Whitelist tab blank.

Important: MAKE SURE TO STORE YOUR SECRET KEY SOMEWHERE SECURE. 

Once you close that window, if you don’t know your secret key, you will NOT be able to use those API keys.

Great! Now you have a set of API Keys associated with your Partner account, and are able to access the test API with Secret Key Authentication Or Bearer Token Authentication!

When you are ready to create a production account, feel free to go through the same steps outlined above. For production accounts, you'll also need to upload real identification documents, real phone numbers, etc. 

Please reach out to [email protected] if you have any questions. Thank you!

Did this answer your question?