Sign in

v1

latestOpenAPI 3.1.0Payrails GmbH2026-07-2614905.7 MB
Vault Records and Aliases

Get field details by alias list

Get field details for multiple provided aliases. The order in which aliases returned may not match the order in which you passed the aliases in request. Not found fields will be ignored: if you request fields by aliases a, b, c and there is no field with alias b, then only fields a and c are returned.

get/token/records/fields

Query parameters

aliasesstring required

Comma-separated aliases of fields in Payrails Vault. There should be at least one alias provided and in one call you can provide up to 10 aliases.

includeVolatileInfoboolean

Boolean indicating if additional information regarding volatile fields should be included in the response.

includeDetokenizationsboolean

Boolean indicating if additional information regarding performed detokenization attempts should be returned.

Response

Array of Field objects.

aliasstring

Merchant-facing unique alias for the field. Used as an identifier.

recordIdstring

Identifier of the record to which the alias belongs.

recordTypestring

Record type to which this field belongs, e.g. card and networkToken.

fieldTypestring

Field type of the alias, e.g. cardNumber, expiryMonth, expiryYear, securityCode, holderName, networkToken, cryptogram.

displayableValuestring nullable

Displayable value for the field.

allowedDetokenizationCountinteger nullable

It will be restricted if used on a proxy and reaches the limit mentioned in this field.

allowedSdkRevealCountinteger nullable

It will be restricted if used on a SDK reveal and reaches the limit mentioned in this field.

hasValueboolean nullable

Indicates whether the volatile field has a value associated with it. If false or not present, the field has been deleted or was never set.

maximumExpirationDatestring date-time nullable

The maximum expiration date for the volatile field value. After this date, the field value will be deleted. Please note that depending on usage of volatile field, value can be deleted even earlier, for example if allowed detokenization or reveal counts are exceeded, or when you explicitly call delete operation on the field.

Example response

[
  {
    "maximumExpirationDate": "2024-12-31T23:59:59Z",
    "detokenizations": [
      {
        "lastAttemptedAt": "2024-01-01T12:00:00Z",
        "count": 1,
        "type": "detokenization"
      }
    ]
  }
]