Scribd
Upload
829 views

Temenos API Framework Error Management

Temenos API Framework Error Management

Uploaded by

MrCHANTHA
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
829 views

Temenos API Framework Error Management

Temenos API Framework Error Management

Uploaded by

MrCHANTHA
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

(/s/) Community Learn Products Training Downloads Suggest (/s/ideatio

Articles (/s/articlelistview)  >  Temenos API Framework Error Management

   Rate    Like    Bookmark

Temenos API Framework Error Management


BEN DAVOLLS (/s/profile/0052K000009zaxTQAQ)  •  Aug 21, 2020  •  Temenos APIs (/s/articlelistview?cat=Temenos APIs)  |  Temenos
(/s/profile/0052K000009zaxTQAQ) Documentation (/s/articlelistview?cat=Temenos Documentation)

  5.00       1       3695

Error grouping is done in the API Framework to standardise and map to valid HTTP codes. Temenos Transact error messages are mapped to custom
error codes and then mapped to standard HTTP error codes as an output. The 2 aspects of the error could be: 1. Transact errors – something went
wrong with Transact and a valid business error is displayed 2. API Framework errors – something went wrong at the API Framework layer

Error grouping is done in the API Framework to standardise and map to valid HTTP codes. Temenos Transact error messages are mapped to custom error
codes and then mapped to standard HTTP error codes as an output. The 2 aspects of the error could be:  
1. Transact errors – something went wrong with Transact and a valid business error is displayed
2. API Framework errors – something went wrong at the API Framework layer

 
Each Transact or API Framework error is finally mapped to the below HTTP status code.
Http CodeUse Case
400 Bad Request - Used to indicate nonspecific failure. 400 is the generic client-side error status, used when no other 4xx error code is appropriate.
401 Unauthorized - Must be used when there is a problem with the client’s credentials.
403 Forbidden - Should be used to forbid access regardless of authorization state.
404 Not Found - Must be used when a client’s URI cannot be mapped to a resource
500 Internal Server Error - Should be used to indicate an API malfunction

 
In the below table, if the ‘Transact Error Message’ column is empty then it is an error raised from the Temenos API Framework layer.
IRIS Error Http
Scenario Transact Error Message
Code Code
TGVCP-001 Unable to get the response from Transact 500  
TGVCP-002 Security Violation 403 SECURITY VIOLATION
TGVCP-003 Invalid Query parameters passed 400  
Query Response Parser Construction Failed/Required parameter
TGVCP-006 500  
missing
TGVCP-007 Missing Enquiry/Missing selection 400 MISSING ENQUIRY - / - MANDATORY INPUT
TGVCP-009 Mandatory URL parameters not passed 401  
INVALID/ NO SIGN-ON NAME SUPPLIED DURING SIGN-ON
TGVCP-011 Invalid credentials during the sign-on process  
PROCESS
TGVCP-014 If the Security Context configuration is not set properly 400  
TGVCP-017 Duplicate query parameter passed 400  

Error code Mapping For Version


IRIS Error Http
Scenario Transact Error Message
Code Code
TGVCP-001 Unable to get the response from Transact 500  
TGVCP-002 Application not found/Resource not found 404 APPLICATION MISSING/RECORD MISSING
TGVCP-002 Record Not Changed/Security Violation 403 RECORD NOT CHANGED/SECURITY VIOLATION
TGVCP-005 Transfer Already Authorised 400 Transfer Already Authorised
TGVCP-008 Invalid company specified 400 INVALID COMPANY SPECIFIED
Mandatory URL parameters not passed/Mandatory parameter
TGVCP-009 404 TRANSACTION ID NOT SUPPLIED
missing/transaction id not supplied
INVALID/ NO SIGN-ON NAME SUPPLIED DURING SIGN-
TGVCP-011 Invalid credentials during sign-on process 401
ON PROCESS
TGVCP-012 If the payload sent is not in Application/Json 400  
TGVCP-014 If the Security Context configuration is not set properly 400  
T24-001 If a mandatory field is missing 400 Missing field value
T24-002 If field not found 400 Field not found
T24-003 Version field validation error 400  

There are no custom error messages that are configured or practiced in the API Framework.
If you experience any issues when using Temenos Transact APIs, please visit the Forum (https://basecamp.temenos.com/s/)

  API (/s/articlelistview?tag=API) ,  error (/s/articlelistview?tag=error) ,  Transact (/s/articlelistview?tag=Transact) , 


errorcode (/s/articlelistview?tag=errorcode)
0 Comments

Post Question

Share an update... Share

Sort by:

Most Recent Activity Search this feed...

Collaborate here!
Here's where you start talking with your colleagues about this.

ompany Legal Follow

nvestor Relations Cookie Policy


https://www.temenos.com/about- (https://www.temenos.com/legal- (https://www.linkedin.com/company/temenos) (https://www.linke
s/investor-relations/) information/cookie-policy/)

ress Releases Privacy Policy


https://www.temenos.com/news/) (https://www.temenos.com/legal-
information/privacy-policy/)

Supplier Information
(https://www.temenos.com/information-
for-suppliers/)

Terms & Conditions


(https://www.temenos.com/legal-
information/website-terms-and-
conditions/)

Copyright © 2012-2023 Temenos Headquarters SA

You might also like