Retrieve a list of card invitations
Get the list of all card invitations in your organisation.
The results are paginated and sorted by the created_at date in reverse chronological order.
- This feature is not available in Sandbox.
- To use the Card invitations API, please contact Revolut API Support.
For more information, see the guides: Manage card invitations.
Request
Default value: the date-time at which the request is made
Retrieves only card invitations created before this timestamp (created_at < created_before).
Used for pagination.
The default value is the current date and time at which you are calling the endpoint.
Provided in ISO 8601 format.
Possible values: >= 1 and <= 100
Default value: 100
The maximum number of card invitations to return per page.
To get to the next page, make a new request and use the created_at date of the last card invitation returned in the previous response as the value for created_before.
Possible values: [created, expired, failed, redeemed]
Retrieves card invitations filtered by the specified state(s).
To specify multiple values, follow this pattern: state={VALUE1}&state={VALUE2}.
If not provided, all states are returned.
Response
The list of card invitations for your business
The ID of the card invitation.
Possible values: [created, expired, failed, redeemed]
The current state of the card invitation:
created: Invitation has been created but not yet claimed.expired: Invitation has expired due to expiry date being reached or manual cancellation.failed: Invitation claim attempt failed.redeemed: Invitation has been successfully claimed.
To learn more about card invitation lifecycle, see the guide: Manage card invitations → Card invitation state.
The date and time the card invitation was created in ISO 8601 format.
The date and time the card invitation was last updated in ISO 8601 format.
Example: "2025-10-20T15:09:24Z"
The date and time after which this card invitation expires if not claimed or cancelled before then. Specified in ISO 8601 format.
Only returned for invitations in state created.
For other states, to find out when a card invitation transitioned to its final state, check the updated_at value.
The ID of the card issued after this invitation was claimed.
Only returned for invitations in state redeemed.
The ID of the team member to be assigned as the holder of the card after the invitation is claimed.
Specifies whether the issued card will be a virtual (true) or physical (false) one.
The label of the card.
The spend program assigned to the card.
To use this property, please contact Revolut API Support.
Possible length: <= 30 characters
The name of the spend program.
Example: {"single":{"amount":200.22,"currency":"GBP"},"week":{"amount":200.44,"currency":"GBP"}}
All spending limits set for the card.
The limit for a single transaction.
The value of the spending limit.
Pattern: Value must match regular expression ^[A-Z]{3}$
The currency of the spending limit, provided as ISO 4217 code in upper case.
The daily limit for transactions.
The value of the spending limit.
Pattern: Value must match regular expression ^[A-Z]{3}$
The currency of the spending limit, provided as ISO 4217 code in upper case.
The weekly limit for transactions.
The value of the spending limit.
Pattern: Value must match regular expression ^[A-Z]{3}$
The currency of the spending limit, provided as ISO 4217 code in upper case.
The monthly limit for transactions.
The value of the spending limit.
Pattern: Value must match regular expression ^[A-Z]{3}$
The currency of the spending limit, provided as ISO 4217 code in upper case.
The quarterly limit for transactions.
The value of the spending limit.
Pattern: Value must match regular expression ^[A-Z]{3}$
The currency of the spending limit, provided as ISO 4217 code in upper case.
The yearly limit for transactions.
The value of the spending limit.
Pattern: Value must match regular expression ^[A-Z]{3}$
The currency of the spending limit, provided as ISO 4217 code in upper case.
The all-time limit for transactions.
The value of the spending limit.
Pattern: Value must match regular expression ^[A-Z]{3}$
The currency of the spending limit, provided as ISO 4217 code in upper case.
The controls for the card's spending period.
They specify the dates when the card will become available or unavailable for spending, and define what happens after the end date.
Example: "2025-09-26"
The start date (inclusive) of the spending period, in ISO 8601 format (YYYY-MM-DD).
Uses the timezone set by the business, or defaults to Europe/London.
Example: "2030-12-31"
The end date (inclusive) of the spending period, in ISO 8601 format (YYYY-MM-DD).
Uses the timezone set by the business, or defaults to Europe/London.
Possible values: [lock, terminate]
The action to take after the end date of the spending period.
Possible values: [health, general, services, airlines, transport, accommodation, utilities, shopping, financial, furniture, hardware, groceries, fuel, entertainment, software, restaurants, advertising, cash, education, government]
The list of merchant categories that will be available for card spending.
If this parameter is not specified, categories are not restricted.
The merchant-level controls for card spending.
They block or allow the card to only transact with specific merchants:
allow: permits only the specified merchants (cannot be used if thecategoriesparameter is set)block: blocks the specified merchants (can be used with or withoutcategories)
Possible values: [block, allow]
The type of control to apply.
Possible number of items: non-empty and <= 20 items
The list of IDs of merchants to which the control applies.
To find merchant IDs, check transaction details (→ merchant.id).
You can fetch transaction details for a specific transaction or for all transactions.
Pattern: Value must match regular expression ^[A-Z]{2}$
Example: "GB"
The list of countries where the team member will be able to use the card. Specified as 2-letter ISO 3166 codes.
The list of accounts that will be linked to the card.