REST 2.0 API Credentials

Home    Back Office Operations    Settings    REST 2.0 API Credentials

On this page:

Overview

Merchants can use the REST 2.0 API Credentials Report to generate API keys required for Nuvei REST API 2.0 transaction authentication. Merchants can generate multiple API keys for each Site and Entity ID pair, with the flexibility to decide which API key to use based on their needs.

The REST 2.0 API Credentials report is available to Control Panel users assigned Admin permissions, the Developer only role, or the Temp role. The Nuvei Payment Support Team automatically creates a user with the Temp role during the merchant onboarding process. This role provides temporary access for generating API keys necessary to start processing payments. For additional API key management, a user with Admin permissions can assign the Developer only role to a user who will have full access to the REST 2.0 API Credentials report for ongoing API key management and configuration. For more information about managing users, permissions, and roles, see the Control Panel Team Settings page.

For more information about Nuvei REST API 2.0, see REST 2.0.

REST 2.0 API Credentials Report

The following information appears in the report:

  • Parent Entity ID – When generating an API key for a Parent Entity ID, all Child Entities of this parent receive the same key. This makes it easier to manage keys for multiple entities under one parent organization.
  • Entity ID – Unique identifier for a merchant account or business entity in the Nuvei system.
  • Site Name – Name of the specific site or platform associated with the API key.
  • API Key – Unique API key associated with a specific Entity ID and Site Name. Merchants can create and use several keys for different purposes, and decide which key to use for processing.

You can:

  •   – Generate an API key for the corresponding Entity ID and Site Name pair.
  • Copy an API key for processing – After generating multiple keys for an Entity ID and Site Name pair, you can copy the appropriate key to use for your processing requirements. Each key can be associated with a specific site or entity, allowing for flexibility and control over which key to use for transactions.
Last update iconLast modified March 2025