Get Card Account External
POSThttps://api.tripleup.dev/partner/card-account.by-ids
Returns a CardAccount instance using one or more of its associated external IDs:
- external card account ID
- external card program ID
- external publisher ID
The receiver returns the same object as calling the /card-accounts/{id}
endpoint with the triple card account ID if a matching CardAccount
exists.
Request
- application/json
Body
Partner-provided, external ID for a Card Account.
External IDs should be stable and never sensitive.
External IDs do not need to be globally unique, but we encourage the use of UUIDs. They must be unique for the Card Account within the scope of its parent Card Program.
To protect against accidental inclusion of sensitive personal information, external IDs may not be 9-digit numbers or use the US Tax ID format (###-##-####).
Possible values: non-empty
and <= 255 characters
, Value must match regular expression ^(?!\d{3}-\d\d-\d{4}$)
id-for-entity
Partner-provided, external ID for a Card Program.
External IDs should be stable and never sensitive.
External IDs do not need to be globally unique, but we encourage the use of UUIDs. They must be unique for the Card Program within the scope of its parent Publisher.
To protect against accidental inclusion of sensitive personal information, external IDs may not be 9-digit numbers or use the US Tax ID format (###-##-####).
Possible values: non-empty
and <= 255 characters
, Value must match regular expression ^(?!\d{3}-\d\d-\d{4}$)
id-for-entity
Partner-provided, external ID for a Publisher.
External IDs should be stable and never sensitive.
External IDs do not need to be globally unique, but we encourage the use of UUIDs. They must be unique for the Publisher within the scope of its parent Portfolio Manager.
To protect against accidental inclusion of sensitive personal information, external IDs may not be 9-digit numbers or use the US Tax ID format (###-##-####).
Possible values: non-empty
and <= 255 characters
, Value must match regular expression ^(?!\d{3}-\d\d-\d{4}$)
id-for-entity
Responses
- 200
- 400
- 403
- 404
- 409
- 415
- 422
- 500
- 501
- 503
Card Account
- application/json
- Schema
- Example (auto)
Schema
ENROLLED
- The account is enrolled for rewardsNOT_ENROLLED
- The account is not enrolled for rewardsCLOSED
- The account is closed and cannot receive rewards
The triple-defined ID for the entity.
Possible values: non-empty
and <= 100 characters
triple-abc-123
RFC 3339 date time used for creation and mod times
2021-12-01T01:59:59.000Z
2-letter ISO-3166 country code
Possible values: >= 2 characters
and <= 2 characters
, Value must match regular expression ^[A-Z]{2}$
US
ZIP Code™, ZIP+4, or postal code
Possible values: non-empty
and <= 15 characters
15206
Partner-provided, external ID for a Card Account.
External IDs should be stable and never sensitive.
External IDs do not need to be globally unique, but we encourage the use of UUIDs. They must be unique for the Card Account within the scope of its parent Card Program.
To protect against accidental inclusion of sensitive personal information, external IDs may not be 9-digit numbers or use the US Tax ID format (###-##-####).
Possible values: non-empty
and <= 255 characters
, Value must match regular expression ^(?!\d{3}-\d\d-\d{4}$)
id-for-entity
The triple-defined ID for the entity.
Possible values: non-empty
and <= 100 characters
triple-abc-123
Possible values: [ENROLLED
, NOT_ENROLLED
, CLOSED
]
ENROLLED
RFC 3339 date time used for creation and mod times
2021-12-01T01:59:59.000Z
{
"card_program_id": "triple-abc-123",
"created_at": "2021-12-01T01:59:59.000Z",
"default_country_code": "US",
"default_postal_code": "15206",
"external_id": "id-for-entity",
"id": "triple-abc-123",
"status": "ENROLLED",
"updated_at": "2021-12-01T01:59:59.000Z"
}
TripleBadRequestError
- application/json
- Schema
- Example (auto)
Schema
The 3-digit HTTP Response Status code
Possible values: [400
]
content required
{
"status_code": 400,
"content": {
"details": [
null
],
"error_message": "The request is malformed.",
"exception": "TripleBadRequestError"
}
}
TripleNotAuthenticatedError
- application/json
- Schema
- Example (auto)
Schema
The 3-digit HTTP Response Status code
Possible values: [401
]
content required
{
"status_code": 401,
"content": {
"details": [
null
],
"error_message": "Client authentication failed.",
"exception": "TripleNotAuthenticatedError"
}
}
TripleInvalidPathError
- application/json
- Schema
- Example (auto)
Schema
The 3-digit HTTP Response Status code
Possible values: [404
]
content required
{
"status_code": 404,
"content": {
"details": [
null
],
"error_message": "The url path or path parameter is invalid.",
"exception": "TripleInvalidPathError"
}
}
TripleIntegrityError
- application/json
- Schema
- Example (auto)
Schema
The 3-digit HTTP Response Status code
Possible values: [409
]
content required
{
"status_code": 409,
"content": {
"details": [
null
],
"error_message": "The request was well-formed but violated entity integrity constraints.",
"exception": "TripleIntegrityError"
}
}
TripleUnsupportedMediaType
- application/json
- Schema
- Example (auto)
Schema
The 3-digit HTTP Response Status code
Possible values: [415
]
content required
{
"status_code": 415,
"content": {
"details": [
null
],
"error_message": "The request defined an unsupported media type.",
"exception": "TripleUnsupportedMediaType"
}
}
TripleUnprocessableEntity
- application/json
- Schema
- Example (auto)
Schema
The 3-digit HTTP Response Status code
Possible values: [422
]
content required
{
"status_code": 422,
"content": {
"details": [
null
],
"error_message": "The request was well-formed but could not be processed.",
"exception": "TripleUnprocessableEntity"
}
}
TripleInternalServerError
- application/json
- Schema
- Example (auto)
Schema
The 3-digit HTTP Response Status code
Possible values: [500
]
content required
{
"status_code": 500,
"content": {
"details": [
null
],
"error_message": "Triple was unable to process the request due to an internal error.",
"exception": "TripleInternalServerError"
}
}
TripleNotImplementedError
- application/json
- Schema
- Example (auto)
Schema
The 3-digit HTTP Response Status code
Possible values: [501
]
content required
{
"status_code": 501,
"content": {
"details": [
null
],
"error_message": "The request failed because it requires a feature that is not yet implemented.",
"exception": "TripleNotImplementedError"
}
}
TripleServiceUnavailable
- application/json
- Schema
- Example (auto)
Schema
The 3-digit HTTP Response Status code
Possible values: [503
]
content required
{
"status_code": 503,
"content": {
"details": [
null
],
"error_message": "The request failed due to a triple service interruption.",
"exception": "TripleServiceUnavailable"
}
}
Authorization: oauth2
name: triple_authtype: oauth2scopes:api.tripleup.com/partner.view_offers
description: The triple API uses OAuth2 with a client id and client secret. The URL to get an OAuth2 token is here: https://auth.tripleup.dev/oauth2/token This is an example of how to call the API from the command line. Code will need to be developed by the partner in their servers. ```bash # Fetch an access token TOKEN_URL=https://auth.tripleup.dev/oauth2/token CLIENT_ID=fake CLIENT_SECRET=another-fake # Fetch a space-separated list of scopes # If not provided, will return an access token # with all scopes to which the client has access SCOPE=api.tripleup.com/partner.publishers TOKEN_RESPONSE=$(curl -s -X POST $TOKEN_URL \ --user $CLIENT_ID:$CLIENT_SECRET \ --data grant_type=client_credentials \ --data-urlencode "scope=$SCOPE") # Use an access token ACCESS_TOKEN=$(echo $TOKEN_RESPONSE | jq -r '.access_token') TOKEN_TYPE=$(echo $TOKEN_RESPONSE | jq -r '.token_type') API_URL=https://api.tripleup.dev curl -X GET "$API_URL/partner/publishers" \ --header "Authorization: $TOKEN_TYPE $ACCESS_TOKEN" ``` See the _Client credentials grant_ section at the bottom of this [AWS blog post](https://aws.amazon.com/blogs/mobile/understanding-amazon-cognito-user-pool-oauth-2-0-grants/) for more information.flows: { "clientCredentials": { "tokenUrl": "https://auth.tripleup.dev/oauth2/token", "scopes": { "api.tripleup.com/partner.portfolios": "Manage Portfolio Manager details and portfolios of Publishers\n", "api.tripleup.com/partner.publishers": "Manage Publisher details, Card Programs, Consumers, Card Accounts,\nand Transactions\n", "api.tripleup.com/partner.view_offers": "View recommended Offers, search Offers, and view Offer details\n", "api.tripleup.com/partner.content_providers": "Manage Content Provider details, Merchants, Merchant Locations,\nand Offers\n" } } }
- python
- curl
- csharp
- go
- nodejs
- ruby
- php
- java
- powershell
- dart
- javascript
- c
- objective-c
- ocaml
- r
- swift
- kotlin
- rust
- HTTP.CLIENT
- REQUESTS
import http.client
import json
conn = http.client.HTTPSConnection("api.tripleup.dev")
payload = json.dumps({
"card_account_external_id": "id-for-entity",
"card_program_external_id": "id-for-entity",
"publisher_external_id": "id-for-entity"
})
headers = {
'Content-Type': 'application/json',
'Accept': 'application/json',
'Authorization': 'Bearer <token>'
}
conn.request("POST", "/partner/card-account.by-ids", payload, headers)
res = conn.getresponse()
data = res.read()
print(data.decode("utf-8"))