Credentials
Last updated
Was this helpful?
Last updated
Was this helpful?
With nearly every NexumAPI request, you will need to include the standard Credentials
object you're accustomed to from SymXchange. Whether to provide , or , etc. credentials depends on the configuration of each individual operation within a SymXchange service. We'll cover how to set that configuration in the next section.
Any changes to the credentials of an operation will need to take place in Parameter Manager > SymXchange Parameters within Symitar Quest.
For NexumAPI Playground users:
Each credential type below should work in our environment for their respective operation. If they don't, check out our Help & Feedback page for the best way to reach us!
Additionally, you will need to make sure that there is an Administrative Password set in the Client Parameters.
Reminder: The TokenId
used in this example is just an example. After a successful login for a user, you'll receive one and it will expire in 15 minutes.
Reminder: Modifying any value in will require the SymXchange instance to be restarted.
The SymXchange operations can be authenticated with various types from within the Credentials
object. The available credential types for each operation will vary and can be found in the .
The AccountNumberCredentials
credential type can be used when returning account information from Symitar. To configure an operation to use this credential type, ensure that it's set to Yes for the target operation in .
The HomeBankingCredentials
credential type can be used when returning account information from Symitar for the home banking user. To configure an operation to use this credential type, ensure that it's set to Yes for the target operation in .
The CardCredentials
credential type can be used when returning account information from Symitar with an identical card number. To configure an operation to use this credential type, ensure that it's set to Yes for the target operation in .
The MICRCredentials
credential type can be used when returning account information from Symitar with an identical MICR number. To configure an operation to use this credential type, ensure that it's set to Yes for the target operation in .
The LookupCredentials
credential type can be used when returning account information from Symitar with an identical Lookup Record and Home Banking Password. To configure an operation to use this credential type, ensure that it's set to Yes for the target operation in .
The UserNumberCredentials
credential type is typically used when there needs to be user differentiation between requests. To configure an operation to use this credential type, ensure that it's set to Yes for the target operation in .
The AdministrativeCredentials
credential type is typically used by applications as a general authentication standard which is accepted by auditors when it's coupled identifying transactions and File Maintenance (FM) via ProcessorUser
. To configure an operation to use this credential type, ensure that it's set to Yes for the target operation in .
The TokenCredentials
credential type is used with the . After a successful logon
request, a TokenId
will be returned that can be provided to any operation that's configured to use it. To configure an operation to use this credential type, ensure that it's set to Yes for the target operation in .