---
schema_version: "1"
id: 07c8e712329d522d5d593742a55e3c6140f2e181df90984727f78bcfd8e327fb
title: About Personalization API Tokens
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/mktg/264-0-0/mc_pers_api_tokens_about.md
canonical_url: https://help.salesforce.com/s/articleView?id=mktg.mc_pers_api_tokens_about.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 002ee6cfa17cf1cfda6cf9e1561cf95d2218978c9c7a7ced3aec015dbf4b6951
description: Learn more about API tokens in Marketing Cloud Personalization.
products:
  - Marketing
  - Salesforce Personalization
release: "264"
---
# About Personalization API Tokens

Learn more about API tokens in Marketing Cloud Personalization.

## Data Access Levels

Personalization's REST API provides access to read and update data at several levels:

- Create and update users and accounts within Personalization
- Receive behavioral data from offline systems
- Receive historical transaction data
- Create and update catalog data, including products and content

## Using an API Token in an API Request

When making an API request, you must set the HTTP authorization header using Basic encoding:

- Most REST clients provide the option to set Basic credentials using a username and password. In this situation, supply the API Key ID as the username, and the API Secret Key as the password.
- If you must construct the HTTP authorization header value manually, use Basic encoding as follows:

Basic <encoded-credential> where <encoded-credential> is a strict Base64 encoding of: <api-key-id>:<api-secret-key>