First steps - Ebury API Dev

What are the differences between an API Technical contact and an End user contact?

Further technical details of both authentication mechanisms can be found in our Authentication section.

	End User contact	API Technical contact
Scenario	When the user is logging into their application but with the credentials he/she uses to log into EBO	The user has his/her own credentials for the application. Ebury solution is just a part of the entire workflow. Machine-2-machine communication
Login	3-step process, including Strong Customer Authentication	2-step process, skips the Strong Customer Authentication
Footprint of the activities in Ebury	Actual user’s contact ID and details	Technical contact’s contactId and details

	End User contact
Scenario	When the user is logging into their application but with the credentials he/she uses to log into EBO
Login	3-step process, including Strong Customer Authentication
Footprint of the activities in Ebury	Actual user’s contact ID and details
	API Technical contact
Scenario	The user has his/her own credentials for the application. Ebury solution is just a part of the entire workflow. Machine-2-machine communication
Login	2-step process, skips the Strong Customer Authentication
Footprint of the activities in Ebury	Technical contact’s contactId and details

Do we need to Whitelist our IP addresses before proceeding?

No need to whitelist your IP addresses.

How do I get bank accounts for testing? Could these accounts already have account balances?

Reach out to our Implementation team. Provide them with the currencies you would like to test with. Also, let them know if you would like very specific account balances. We will get back to you with the ready setup.

How and when can I get access to API credentials?

You can get credentials to access our Sandbox at any time. There are no prerequisites to be met. You can request it and have it right away. Also, the Implementation team could also organize a brief demo of our API capabilities.

Regarding credentials to accessing Production, you should have completed the onboarding and KYC on Ebury’s side. Preferably, you should have also completed a fair amount of testing in Sandbox before requesting the Production credentials. All credentials are communicated via our Welcome email.

We want to offer Ebury’s services to our customers, embedded directly in our platform; how can we build workflows to act on behalf of the client?

We offer a standard solution in this case. We configure an API Technical contact on every underlying client. The API Technical contact can orchestrate and manage each of the workflows that the underlying client might be interested in. Depending on the customer’s needs, the API Technical contact can be configured with different permissions. Let us discover your problem statement together and then propose the nature of the API Technical contact required.

Does Ebury have different behaviour via Ebury’s API and Ebury Online?

No, both the API and EBO have the same behavior. For example, a user will be treated to the same behavior whether he creates a mass payment via EBO or API or needs to authorize a payment.