Transaction Limit Inquiry API - Wallet

get

https://uatmea-iss-apigw.creditpluspinelabs.com/deviceapi/apis/transaction-limits/wallets/{wallet_number}

This API is used to retrieve transaction type wise limits configured at wallet level.

HTTP Status and Response Status Matrix

HTTP Code: This is the response status code issued by a server in response to a client's request made to the server.
Error Code: This is the error code returned by Credit+ Issuing application in the ‘code’ field of the response message indicating if the request was processed successfully or failed.
Reason: This is the description of the error code returned by Credit+ Issuing application.

HTTP Code	Error Code	Reason
200	OK	The server successfully processed the request.
400	MISSING_REQUIRED_FIELD	Error example: Missing Required Field 'productType'.
400	INVALID_FIELD_VALUE	'productType' field value 'pre-paid' is invalid.
400	RECORD_NOT_FOUND	Device record not found based on the given input.
400	UNIQUE_RECORD_NOT_FOUND	Multiple records found for given search criteria.
401	UNAUTHORIZED	We couldn't recognize you.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Path Params

wallet_number

string

required

length between 9 and 24

API consumer must share wallet_number as a path parameter for API requests. The minimum length of this field is 9 and maximum length is 24.

Query Params

offset

integer

≥ 0

API consumer can share offset as a query parameter for API requests. This is the number of items to skip before starting to collect the result.

limit

integer

≥ 1

Defaults to 15

API consumer can share limit as a query parameter for API requests. This is the maximum numbers of items to be returned in response. Default values are as configured in Institution Parameter Setup > System Codes against TYPE_ID = API_SEARCH_FILTER_LIMIT and CODE = LMTW. The system code value is non-editable and set to 15 records.

Headers

X-MC-Correlation-ID

string

^[a-zA-Z0-9-]{1,100}$

API consumer can share X-MC-Correlation-ID in HTTP header for API requests. If it is not shared then the system generates a unique value for each request. X-MC-Correlation-ID must be unique for each request, Maximum supported length – 100 alphanumeric characters.

X-MC-Source

string

API consumer can share X-MC-Source (optional field) in HTTP header for API requests. For the list of Source values, see the Pre-conditions for HTTP Header of REST API topic in the Pre-requisite for Rest API section.

X-MC-Channel

string

enum

API consumer can share X-MC-Channel (optional field) in HTTP header for API requests. It is the network or channel through which request is routed. The only available value for Channel is API.

Allowed:

X-MC-Client-Client-Application-User-ID

string

length ≤ 50

API consumer can share X-MC-Client-Client-Application-User-ID in HTTP header for API requests. This is a unique identifier to track actual user performing action at the client's end. This field is used only for logging purpose. The maximum length is 50.

Response

Language

URL

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

200Successful response with transaction limits for the specified wallet.