Main Web API Documentation Information
|
|
Actual Page/Function Name:
|
customerRemoteSignIn |
Human Readable Name or Caption:
|
Customer Remote Sign In |
Page/Function Description:
|
This is how a customer logs in for e-commerce or a backend portal. These settings are internally set, and this is how you use them. There are 10 fields that you can mix and match to create your login credentials. |
Page/Function Output Type:
|
API - JSON or WDDX |
Categories:
|
eComm,customer |
Extra Page/Function Notes:
|
Parameters
|
|||||||
Scope | Name | Type | Default | Description | Required | Alternates | Known Values |
Arguments | CORP_KEY_ID | String | Pass in the corporation key. This is a combination of 3 letters from the corporation name, a dash, and then the actual corp id number. Ex: PLA-0053, XYZ-0123. As a note, the corporation ID may be padded with zeros. This is not required, but it will be added if the number is system-generated (the numbers will be stripped off later). | Yes | |||
Arguments | CUSTOMER_ID | Numeric | 0 | Pass in the customer id number if known. If passed in, it will virtually bypass the normal sign in procedure. If you know the person's id, you can skip getting any of their other login credentials. | Yes | ||
Arguments | SIGN_IN_VALUE_ONE | String | Pass in the sign in value for field one. As a note, there are corp-wide settings that already map to one of 10 existing customer fields. Whatever is passed in in this value will be matched to that field that is held in settings. For example, say that your sign in value for field 1 is email. You would enter something like yourname@something.com, and behind the scenes we would match that to the customer's email field. | No | |||
Arguments | SIGN_IN_VALUE_TWO | String | Pass in the sign in value for field two. See sign in one for more info. As a note, there are 10 fields that this might be mapped to. For example, for a zip code you might enter 55555. | No |
Results
|
||||||||||||
RET_STATUS | RET_MAIN_MESSAGE | RET_SECOND_MESSAGE | Redirect Link | Description | ||||||||
ok | success | This assumes that everything went well. | ||||||||||
|
||||||||||||
searchLogicProblem | Unable to connect to the database. Missing the [CustomerName]information that matched your search. | The sign in process was unable to complete.<br />Use your back button and try again. | ||||||||||
zeroCustomerMatch | Unable to find a matching record in the database. The [CustomerName] sign in did not take place. | As a note, the sign in values must match exactly what is stored in the database. Otherwise you will get this zero [CustomerName] match error message. Use your back button and try again. | ||||||||||
multiCustomerMatch | According to the system, more than one [CustomerName] matches was found. See notes below. | In order to protect your and others personal information, we can not sign you in at this time. Please contact us and let us know that a duplicate may exist. Once we make sure that we have the correct information on file, this sign in process will work. If you would like to try again, use your back button. |
Samples
|
|
Caption | Text |
JSON |
{"API_CALL_FUNCTION_NAME": "customerremotesignin","CUSTOMER_ID": 23169,"SIGN_IN_VALUE_ONE": "","SIGN_IN_VALUE_TWO": "","API_CORP_KEY_ID": "PLA-0053","API_USER_NAME": "demo","API_USER_PASSWORD": "1234","CORP_KEY_ID": "PLA-0053","API_CURRENT_PAYEE_ID": "3","API_INPUT_OUTPUT_TYPE": "JSON","API_URL_ENCODING": "AUTO"}
|