This API allows the Member to answer their Security Question. You should call the Get Security Question API in order to provide the member with a Question to answer, and to get information that you will need in order to provide this API with the right request data.
API Endpoint
POSThttps://api.itsme247.com/v1.1/authentication/securityanswer
HTTP Headers
| Status |
Key |
Value |
| Required |
CU*Answers-AppKey |
GUID |
| Required |
Accept |
application/json |
| Required |
Content-Type |
application/json |
| Optional |
CU*Answers-CUID |
3 digit Credit Union ID |
Request
{
"QuestionId": 0,
"QuestionAnswer": "string"
}
| Parameter |
Type |
Description |
| QuestionId |
integer |
This is the Sequence number of the Security Question the member is answering. This is an integer that should have a value between 1 and 3 |
| QuestionAnswer |
string |
This is the answer to the Security Question that the member will type in. It’s a string with a length between 3 and 30 |
Response
{
"NextStepCode": "string"
}
| Parameter |
Type |
Description |
| NextStepCode |
string |
This parameter will tell you what to call next in the Authentication Process. There are multiple steps that could come up that are required to be processed before a member can continue. Check below for the listing. |
Response Error
Check the error table below for information on the error codes that could be returned
{
"ErrorCode": "string",
"DisplayMessage": "string",
"TechnicalMessage": "string",
"Timestamp": "datetime""
}
| Parameter |
Type |
Description |
| ErrorCode |
string |
The ErrorCode is a custom code we use to identify specific areas where something might have not worked right. Write it down and contact us if you continue to have issues. |
| DisplayMessage |
string |
This is generally something you can show to members when an error shows up. Though we encourage you to create your own message table based on the ErrorCode field above. We use these display messages for Online Banking, so you might see something tailored to a different application. |
| TechnicalMessage |
string |
This is a more detailed, developer-type message that migth help you in determining more of what’s going on. This should never be displayed to the member. |
| Timestamp |
datetime |
The date and time of the error. This is useful information to provide CU*Answers, should you need to contact us. |
Next Step Codes
These codes tell the developer which form they should present to the member next in the Authentication process. It can get detailed, so look below and make sure you have the correct forms for the responses you receive. Please note, that there is no Login Step for Credentials. That is the first call you should make for Authentication, in which you will receive your Next Step. Without Credentials, you will not receive any tokens to be used in the remaining Authentication API calls.
| Code |
Description |
| ANCQ |
Answer your Security Question. If you recevie this step, that means that all other steps are already complete for the member and will not be required. |
| PSWD |
Change or add a password. |
| SECQ |
Must create Security Questions for this account. If this step comes up, the SECA step below will never be returned and will be skipped. |
| SECA |
Must create/update Security Answers to the Security Questions. The main difference between this step and SECQ is that the member should already have Security Quetsions selected by the time they get this far.This step will generally come up when a member fails to answer their questions correctly three times in a row. In doing so, their answers will be wiped out. |
| EULA |
The member must accept the EULA for this account. |
| PIBP |
The member must accept the default PIB Profile |
| UNAM |
Must create a Username for this account |
| EMAL |
Must update/create an email address for this account |
| GOOD |
No further steps are required. The member is now fully authenticated. Session and User tokens are now full tokens and will timeout in 15 minutes. |
Error Codes
| Code |
HTTP Code |
Description |
| SC12345902 |
401 |
Member failed to answer challenge questions and disable profile. |
| NF12345743 |
500 |
Warning: One more incorrect try on challenge questions and profile will be disabled. |
| ST12345702 |
500 |
Credit union not available during stand-in processing for end of day. |
| PC12345705 |
500 |
Member not authorized to access account based on PIB profile access times. |
| NF12345748 |
500 |
Missing Vendor login script. Contact CU*Answers. |
| NF12345734 |
500 |
Invalid Credit Union Id. |
| NF12345704 |
500 |
Application keys not found. Contact CU*Answers. |
| NA12345746 |
500 |
Online banking is not active for this Credit Union. |
| 9999999999 |
500 |
Requested data not found. |
| 8888888888 |
403 |
Requested data not found. |
| API2000 |
403 |
Forbidden: You are not authorized to use this resource. |
| API2010 |
403 |
Forbidden: You are not authorized to use this resource. |
| API2011 |
403 |
Forbidden: You are not authorized to use this resource. Whitelist Issue. |
| API2012 |
403 |
Forbidden: You are not authorized to use this resource. |
| API2013 |
403 |
Forbidden: You are not authorized to use the Accounts API. |
| API2014 |
403 |
Forbidden: You are not authorized to use the Members API. |
| API2015 |
403 |
Forbidden: You are not authorized to use the CreditUnions API. |
| API2016 |
403 |
Forbidden: You are not authorized to use the Transfers API. |
| API4000 |
403 |
Forbidden: You are not authorized to use this resource. |
| HTTP404 |
404 |
The location requested could not be found. |
| HTTP415 |
400 |
The media type requested is not supported. Please use application/json. |
| OB110 |
400 |
The AppKey is missing. |
| OB111 |
400 |
The session token is missing. |
| OB112 |
400 |
The user token is missing. |
| OB113 |
403 |
The id is missing. |
| OB201 |
403 |
The AppKey provided could not be verified. |
| OB202 |
403 |
The AppKey provided could not be verified against the credit union id. |
| OB203 |
403 |
Mismatch between AppKey and credit union id. |
| OB204 |
400 |
Credit union id could not be found. Please validate HttpHeader parameters are valid. |
| OB310 |
403 |
Data received is incomplete. Please validate the data being sent in and try again. |
| OB500 |
503 |
Online access is currently disabled, please try again later or contact the Credit Union for assistance. |
| OB503 |
500 |
[This message changes based on CU Configuration for maintenance] |
| OB510 |
500 |
Data could not be retrieved for this request, please try again or contact the Credit Union for assistance. |
| OB511 |
500 |
Data could not be retrieved for this request, please try again. |
| NO12345690 |
500 |
There was a problem processing your request. Please try again or contact CU*Answers. |
| NF12345703 |
500 |
There was a problem processing your request. Please try again or contact CU*Answers. |
| NO12345678 |
500 |
There was a problem processing your request. Please try again or contact CU*Answers. |
| NO12345732 |
500 |
There was a problem processing your request. Please try again or contact CU*Answers. |
| NO12345679 |
500 |
There was a problem processing your request. Please try again or contact CU*Answers. |
| NF12345727 |
500 |
There was a problem processing your request. Please try again or contact CU*Answers. |
| NO12345699 |
500 |
There was a problem processing your request. Please try again or contact CU*Answers. |
| NO12345708 |
500 |
There was a problem processing your request. Please try again or contact CU*Answers. |
| NO12345707 |
500 |
There was a problem processing your request. Please try again or contact CU*Answers. |
| NO12345725 |
500 |
There was a problem processing your request. Please try again or contact CU*Answers. |
| NO12345726 |
500 |
There was a problem processing your request. Please try again or contact CU*Answers. |
| BT12345681 |
500 |
There was a problem processing your request. Please try again or contact CU*Answers. |
| BT12345682 |
500 |
There was a problem processing your request. Please try again or contact CU*Answers. |
| SC12345684 |
500 |
There was a problem processing your request. Please try again or contact CU*Answers. |
| SC12345683 |
500 |
There was a problem processing your request. Please try again or contact CU*Answers. |
| SC12345692 |
500 |
There was a problem processing your request. Please try again or contact CU*Answers. |
| SC12345693 |
500 |
There was a problem processing your request. Please try again or contact CU*Answers. |
| SC12345698 |
500 |
There was a problem processing your request. Please try again or contact CU*Answers. |
| SC12345735 |
500 |
There was a problem processing your request. Please try again or contact CU*Answers. |
| NF12345703 |
500 |
There was a problem processing your request. Please try again or contact CU*Answers. |
