Key API identifiers

This post lists essential identifiers used in Pushwoosh API requests. These identifiers are required for authentication, message creation, targeting, segmentation, tracking, and managing users across your applications.

A unique identifier assigned to each application in your Pushwoosh account. It is required in most API calls to specify the target app.

Where to find it

Pushwoosh Control Panel → Below the application name.

A unique token assigned to a Pushwoosh account, used to authenticate API requests. It enables access to manage projects, send messages, modify settings, and retrieve data. Each account has at least one token created by default. Learn more

Where to find it

Pushwoosh Control Panel → API Access.

A unique identifier assigned to a device by the Pushwoosh SDK. Automatically set by the SDK or passed during device registration. Learn more

Where to find it

• In device logs. Learn more

• In User Explorer when searching by User ID

• In the CSV file downloaded from the Segments list

A token issued by platform providers that identifies an app-device pair for delivering push notifications. Collected automatically by the SDK when push permissions are granted. Learn more

Where to find it

• In device logs. Learn more

• In User Explorer, enter the HWID in the search field to find the associated device, then open the device details to view the push token.

Indicates the platform of the target device using a numeric code. Set automatically by the SDK.

Supported values:

1 – iOS
3 – Android
7 – macOS
8 – Windows
9 – Amazon
10 – Safari
11 – Chrome
12 – Firefox
14 – Email
17 – Huawei
18 – SMS
21 – WhatsApp
22 – Line

A custom identifier assigned to a user, enabling cross-device and personalized targeting. Learn more

Where to find it

Pushwoosh Control Panel → Audience → User Explorer

A unique identifier assigned to each message upon creation. It follows a specific format: XXXX-XXXXXXXX-XXXXXXXX.

This code is essential for:

• Tracking the status and delivery of a specific message.
• Canceling (or deleting) a previously sent message.
• Getting message statistics.

Where to find it

• Pushwoosh Control Panel: Navigate to Message history, then open the properties of the desired message. The Message Code will be displayed there.
• /createMessage API response: When creating a new message via the API, the Message Code is included in the response.

An identifier for a saved message preset (for example, push or SMS). Learn more

Where to find it

Pushwoosh Control Panel → Content → Presets.

You can find the preset code in two places:

• In the list view, displayed below the preset name.

• In the URL when editing or creating a preset (it’s the last part of the URL).

Example:

URL: https://app.pushwoosh.com/applications/XXXXX-XXXXX/sms-presets/edit/AAAAA-BBBBB

Preset code: AAAAA-BBBBB

Identifier for a rich media template. Learn more

Where to find it

Pushwoosh Control Panel → Content → Rich media.

Example:
URL: https://app.pushwoosh.com/applications/XXXXX-XXXXX/rich-media/AAAAA-BBBBB/statistics
Rich media code: AAAAA-BBBBB

The email content code is a unique identifier for saved email content. Learn more

Where to find it

Pushwoosh Control Panel → Content → Email content.

The code is the last part of the URL.

Example:

URL: https://app.pushwoosh.com/applications/XXXXX-XXXXX/email-content/edit/AAAAA-BBBBB
Email content code: AAAAA-BBBBB

A unique identifier used to reference a specific campaign for tracking, and analysis.

Where to find it

The campaign code appears in the URL when viewing campaign-related statistics in the Pushwoosh Control Panel. To locate it, go to Statistics → Aggregated statistics, click on the desired campaign, and copy the code found at the end of the URL.

Example:

URL: https://app.pushwoosh.com/applications/XXXXX-XXXXX/statistics/aggregated-message?campaignCode=YYYYY-YYYYY

Campaign code: YYYYY-YYYYY

A unique identifier used to associate messages with specific marketing campaigns for tracking and performance analysis.

Where to find it

The Journey ID appears in the URL of the campaign canvas in the Pushwoosh Control Panel.

Example:
URL: https://app.pushwoosh.com/journeys/XXXXX-XXXXX/1/aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee

Journey ID: aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee

The name of a predefined user segment created in Pushwoosh for audience targeting. Learn more

Where to find it

Pushwoosh Control Panel → Segments.

A unique code in the format XXXXX-XXXXX that identifies a segment (also called a filter) in Pushwoosh. This code is used in API calls, automation logic, and dynamic segmentation rules.

Where to find it

You can find the segment code in the segment definition preview inside the Segments section of the Pushwoosh Control Panel. The filter code appears at the beginning of the targeting logic.

Example:

Tag("XXXXX-XXXXX", "In-app Purchase", noteq, "0.00")

In this case, XXXXX-XXXXX is the filter (segment) code.

A custom attribute assigned to users or devices. Used for dynamic segmentation and personalization. Learn more

Where to find it

Pushwoosh Control Panel → Tags or via /getTags API.

The name of a tracked event (e.g., purchase, login, subscription). Used to trigger automated workflows or for analytics. Learn more

Where to find it

Pushwoosh Control Panel → Audience → Events.

Identifies a geofenced area used to trigger location-based notifications. Learn more

Where to find it

Pushwoosh Control Panel → Geozones.