Create a card invitation

Create an invitation for a virtual team member card for a new, not-yet-onboarded team member. When the team member completes onboarding before the invitation's expiry date, the invitation will automatically be claimed, and the card will then be issued for the team member immediately.

Note
  • 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​

Card to create an invitation for

Request body
Body object

Possible length: <= 40 characters

A unique ID of the request that you provide.

There is no strict requirement on the format of this ID, but we suggest using v4 UUIDs.

Caution

This ID is used to prevent duplicate card creation requests in case of a lost connection or client error, so make sure you use the same request_id for requests related to the same card invitation. The deduplication is limited to 24 hours counting from the first request using a given ID.

For more information, see the guides: Manage card invitations - Idempotency.

Pattern: Value must match regular expression ^P\d+D$
Example: "P3D"

Default value: P90D

The period after which the card invitation expires if it hasn't been claimed or cancelled. Must be specified in ISO 8601 duration format. The duration is counted from the card invitation creation.

  • Minimum duration: 1 day (P1D)
  • Maximum duration: 90 days (P90D)
  • Default duration: 90 days (P90D)

The ID of the team member who will be assigned as the holder of the card after the invitation is claimed.

Tip

To retrieve a team member's ID, use the GET /team-members operation.

Possible values: [true]

Specifies the type of the card. Must be set to true, as with the API, you can create only virtual cards.

Tip

To create physical cards, use the Revolut Business app.

Possible length: non-empty and <= 30 characters

Default value: Virtual

The label for the card to be issued, displayed in the UI to help distinguish between cards. If not specified, the default label will be set according to the card's type. For card invitations created via API, it's always Virtual.

Example: {"single":{"amount":200.22,"currency":"GBP"},"week":{"amount":200.44,"currency":"GBP"}}

All spending limits set for the card.

You can have at most 1 periodic (day/week/month/quarter/all-time) and 1 non-periodic (single transaction) limit at a time. If you try to specify 2 periodic limits at a time, it will result in an error.

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 let you set the dates when the card becomes available or unavailable for spending, and define what happens after the end date.

If specified, you must provide at least one of these:

  • start_date
  • end_date together with end_date_action

The dates provided must be in the future.

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 to be available for card spending. If not specified, all categories will be allowed.

Note

The categories and merchant_controls parameters have the following restrictions:

  • If you set categories, you cannot set merchant_controls.control_type to allow.
  • You can set merchant_controls.control_type to block.
  • You may also set either categories or merchant_controls independently, or set neither.
  • Both parameters can be used together only if merchant_controls.control_type is block.

The merchant-level controls for card spending.

They let you block or allow the card to only transact with specific merchants:

  • allow: permits only the specified merchants (cannot be used if the categories parameter is set).
  • block: blocks the specified merchants (can be used with or without categories).

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.

Tip

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"

Restricts card use to specified countries, provided as 2-letter ISO 3166 codes.

The list of accounts to link to the card. If not specified, all accounts will be linked. To retrieve account IDs, use the GET /accounts operation.

Response​

Successfully created card invitation

Response body
Body object

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.

Note

Only returned for invitations in state created.

Tip

For other states, to find out when a card invitation transitioned to its final state, check the updated_at value.

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.

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 the categories parameter is set)
  • block: blocks the specified merchants (can be used with or without categories)

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.

Tip

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.
Was this page helpful?