Upgrade to Contis API V2 from API V1
This page is dedicated to help Contis clients using older version of Contis APIs to new RESTful APIs standard offering.
History of API V1:
Contis APIs V1 had been launched back in 2013 with an aim to enable Contis clients to use APIs for self-serve portals and applications. These APIs were developed using XML based SOAP technology protocol and had been serving client needs since then. There was total 240+ methods supported to do various actions on Contis platform.
Introduction of API V2:
Contis APIs V2 has been launched in 2018, having more than 350+ methods supporting to cover various functionalities and scenarios on Contis platform.
Contis API V2 is a RESTFul API and managed to JSON based data format to communicate between Client and Contis server. It has been developed with latest authentication method of OAuth 2.0, OAuth is an open standard for authorization, commonly used as a way for Internet users to log in to third party website accounts without exposing their password.
What is good in API V2?
Contis V2 API is open to access via VPN and PKI security certificate. In PKI based version Payload will be covered with end-to-end security on public network. Same way in VPN Payload will be route via creating secure tunnel communication between Contis and Client server.
Contis V2 API allows you to develop mobile APP without developing wrapper between App and Contis API. Contis API V2 calls can be cached and data can be marked as cacheable, which can be reused by the browser later without having to initiate another request back to the server. This saves time and resources.
Comparison between V1 & V2 APIs
| V1 API | V2 API |
|---|---|
| Word based offline document | HTML based online document |
| Protocol | Architecture |
| SOAP Based | RESTful |
| XML | JSON |
| WS-Security | HTTP and HTTPs |
| Slower | Faster |
| MD5 and 3DES Hashing (with some support on strong enc/hashing in 1.1) |
SHA256 and AES256 |
| Slower | Faster |
| Complex and Consolidated | Simpler and Controlled |
| Non-PKI based | PKI Based |
| VPN | VPN |
Mapping of API V1 methods to API V2 methods (useful for clients migrating from API V1)
We have analysed and consolidate commonly used methods which are currently being used by API V1 clients on most frequent basis.
The list is given as below and help our API V1 clients to map their method usage to respective method(s) of API V2.
| API V1 Methods | API V2 Methods | |
|---|---|---|
| Method Name | Controller | MethodName |
| Login | Security | Login |
| Logout | Security | Logout |
| CardHolder_Create | Consumer | AddConsumer |
| CardHolder_GetInfo | Consumer | |
| CardHolder_Lookup_GetInfo | ||
| CardHolder_Update | Consumer | |
| CardHolder_AddressUpdate | ||
| CardHolder_ContactUpdate | ||
| Card_RetrivePIN | Card | ViewPin |
| Card_Activate | Card | ActivateCard |
| Card_Lookup_GetInfo | Card | |
| Card_ChangeStatus | Card | |
| Card_Request | Card | RequestNewCard |
| Card_Personalize | Card | LinkPreissuedCard |
| Card_GetActivationCode |
|
|
| Account_GetInfo | Account | GetSpecificAccount |
| Account_GetBalance | Account | GetBalance |
| Account_GetStatement | Card |
Note : For CardAPI Client |
| Account |
Note : For AccountAPI Client |
|
| Account_LoadMoney | Account | LoadConsumerAccount |
| Account_TransferMoney | P2P | Transfer |
| Account_WithdrawMoney | Account | UnloadConsumerAccount |
| Account_SetupBank | Transfer | AddRecipient |
| Account_BankWithdraw | Transfer | BankTransfer |
| Account_Chargefee | Account | ChargeFee |
| Account_GetPendingTransactions | Card | ListPendingCardAuthorizations |
| Account_GetBankAccounts | Transfer | ListRecipients |
| Account_DeleteBankAccount | Transfer | DeleteRecipient |
| Account_UploadBulkPaymentFile | Transfer | UploadPaymentFile |
| Agreement_GetAgreement | Consumer | ListTerms |
| SO_Get_Rejected_Payments | StandingOrder | ListFailedSO |
| AUTHORIZE | Security | Authorize |
| SDK_PostLoginDetails | Security | PostLoginDetails |
Note: Above method comparison is only showcasing most used methods. If you are using any specific method that is not listed above, kindly contact API support team for further information.
Q&A / Migration Support
Our well managed API Support Team will be happy to support in any difficulties for migration activity. You can reach out our API Support Team by below different communication media.
- Email : api.support@contis.com
- Slack Chat : Individual client wise separate channel will be setup by API Support Team for quick and instant support.
- Contis Online Ticketing System : You can raise your query in contis internal PMTool Ticketing system via https://pmtool.contisgroup.com which is being directly attended by API Support Team.
- Support Timings : UK working hours 08.30 to 17.30 in all Business working days.