Get Card Status API

get

https://uatmea-iss-apigw.creditpluspinelabs.com/cardmgmt/apis/v1/services/card/status

This API is used to retrieve the card status. The Credit+ Issuing system receives, validates and processes the request. If the request is successful, the system sends the card details in the response message. If the request fails, the system returns the corresponding error code in the response.

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 Codes	Reason
200	000	Successful
400	997	Either Mobile Number or Account Number is not specified
401	990	User is not authenticated
404	998	No card(s) found for the request
500	999	Error getting card details
400	994	Either Mobile number or Account number is not specified
400	994	Invalid type is specified
404	998	No cards
400	994	Mobile number Required
400	994	Product type should be either C, P or D

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Query Params

accountNumber

string

length ≤ 24

^[0-9]+$

Account number of the customer (either accountNumber or mobileNumber is required)

mobileNumber

string

length ≤ 15

^[0-9]+$

Mobile number of the customer (either accountNumber or mobileNumber is required)

type

string

enum

Card type to be returned (primary or all)

Allowed:

Headers

Correlation-ID

string

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

API Consumer must share a Correlation-ID in the HTTP header for API requests. The Correlation-ID must be unique for each request. It is recommended to generate universally unique identifier (UUID) of length 32 or 36 that is compliant with RFC 4122. The maximum supported length is 50 alphanumeric characters. For example, ac97d177-9345-4934-8343-0f91a7a02836. If the Correlation-ID is not received in the incoming request, the system generates the UUID dynamically and assigns it to the request.

Source

string

API Consumer can share Source in the 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.

Response

200Successful retrieval of card status