Introduction

The LATAM Pass Cobrand PNA API is the way through which our bank partners manage the life cycle of benefits that are granted to our LATAM Pass members who hold a cobrand card.

The end of the life cycle, then, occurs when a current card is cancelled or blocked, that is, when the LATAM Pass benefits must no longer be granted to the member.

To be able to make requests to the API, you must first obtain the access token. See the Authentication documentation for full information.

Baseline Gantt chart

Access the baseline Gantt chart for each type of program partnership through the links below:

1. New partnerships;
2. Existing partnerships migrating to the LATAM Pass PNA API.

Request

For a life cycle to be ended, the following data must be provided:

1. LATAM Pass member identification code or Frequent Flyer Number ( ffn);
2. Non-sensitive cobrand credit card data ( card);

See the technical documentation for the fields that comprise them.

Header

• client_id: value obtained from the API Tools > My Apps  > Client ID menu and mandatory in all requests
• access_token: access token previously obtained
• x-issue-bank: identification of the card issuing bank, must correspond to one of the values ​​presented in the technical documentation to properly allow the rules for member segmentation
• x-latam-test: fixed LatamPass, to be used in the test environment only, which means, it must not be used in the production environment

Response

Most common errors

Missing required fields or invalid values

{
   "code": 400,
   "message": "Invalid request content",
   "instructions": "Evaluate the request fields",
   "issuedDateTime": "2024-10-21T18:38:00.101662Z",
   "details": {
      "member.ffn": "must not be null",
      "card": "must not be null"
   }
}

There is no previously initiated life cycle for the member, bank and card

{
   "code": 400,
   "message": "Member not found on database",
   "instructions": "Evaluate the request fields",
   "issuedDateTime": "2024-10-01T18:40:54.112746395Z",
   "details": null
}

Technical documentation

Click here to access it.