Download the PHP package engagespot/php-sdk without Composer

Engagespot PHP SDK

The Engagespot PHP SDK enables seamless integration and notification sending via the Engagespot API in PHP applications. Engagespot provides a unified platform for delivering targeted notifications to users through channels like in-app messages, web push, and email.

Installation

Install the Engagespot PHP SDK using Composer:

Getting Started

Step 1: Obtain API Credentials

Sign up for an account on Engagespot and acquire your API key and API secret.

Step 2: Initialize EngagespotClient

Include the Engagespot PHP SDK in your PHP code and create an instance of EngagespotClient with your API key, API secret, and signing key (if applicable):

here are examples of the two types of initializations for the EngagespotClient:

1. Initialization with individual parameters:

In this example, the EngagespotClient is initialized with individual parameters for the API key, API secret.

2. Initialization with an associative array:

In this example, the EngagespotClient is initialized with an associative array that includes the API key, API secret, signing key, and base URL.

Remember to replace 'your-api-key', 'your-api-secret', and 'your-signing-key' with your actual Engagespot API credentials. The base URL is optional and defaults to 'https://api.engagespot.co/v3' if not provided. The signing key is also optional and can be omitted if not used.

Data Region

Data Region is an optional parameter that allows you to specify the region where the data is stored. The default region is us. Learn more about Data Region.

• dataRegion (optional): Specify the region for data storage and processing. Available options:
  • us: US West region
  • eu: EU Central region

Step 3: Sending a Notification

Sending a Notification

Prepare notification data and use the send method:

Legacy Payload

Preferred Payload

Sending the notification

Create OR Update User

You can add any keyvalue pairs to profile.

Generating User Token

Generate a JWT token for a user for authentication:

Note : Remember that for generating user token you must need to Initialize engagespot via associative array OR by

because signingKey is required for generating user tokens

Creating Signing Key

You can generate your public-private signing key pair from Engagespot console, and this private key should be the secret signing key for generating user tokens

NOTE: When you generate the signing key, Engagespot will store only the public key in our database. You should download the private key and use it for signing your user tokens. You won't be able to retrieve the private key after this step.

Additional Configuration

Set additional configuration options if needed:

You can set SigningKey after initializing EngagespotClient by

Managing In-App Inbox Notifications

In-app inbox notifications are messages that users can view within your application. Here's how you can manage them using the EngagespotClient:

1. Initialization

Before you can interact with the in-app inbox notifications, you need to initialize the EngagespotClient with your API credentials:

2. Fetching In-App Notifications

You can fetch in-app notifications for a specific user. This retrieves a list of notifications from the in-app inbox.

• userIdentifier: The identifier of the user whose notifications you want to fetch.
• pageNo (optional): Page number of the notifications (default is 1).
• limit (optional): Maximum number of notifications per page (default is 10).

3. Marking a Notification as Read

You can mark a notification as read once the user has viewed it.

• notificationId: The ID of the notification to mark as read.

4. Marking a Notification as Unseen

You can mark a notification as unseen to indicate that it hasn't been viewed by the user yet.

• notificationId: The ID of the notification to mark as unseen.

5. Marking a Notification as Unread

You can mark a notification as unread if the user has viewed it but hasn't interacted with it in a meaningful way.

• notificationId: The ID of the notification to mark as unread.

6. Deleting a Notification

You can delete a notification from the in-app inbox if it's no longer relevant.

• notificationId: The ID of the notification to delete.

Managing Topics

Topics allow you to organize users into groups based on their interests or preferences. Here's how you can manage topics using the EngagespotClient:

1. Initialization

Before you can interact with topics, you need to initialize the EngagespotClient with your API credentials:

2. Creating a Topic

You can create a new topic with a name and an optional identifier. If an identifier is not provided, it will be generated from the name.

• name: The name of the topic.
• identifier (optional): The identifier of the topic. If not provided, it will be generated from the name.

3. Updating a Topic

You can update the name of an existing topic.

• topicId: The ID of the topic to update.
• name: The new name for the topic.

4. Deleting a Topic

You can delete a topic.

• topicId: The ID of the topic to delete.

5. Subscribing Users to a Topic

You can subscribe users to a topic.

• topicId: The ID of the topic to subscribe users to.
• users: An array of user objects to subscribe. Each user object should have an identifier and channels.

6. Unsubscribing Users from a Topic

You can unsubscribe users from a topic.

• topicId: The ID of the topic to unsubscribe users from.
• users: An array of user identifiers to unsubscribe.

7. Updating Notification Channels for a User in a Topic

You can update the notification channels for a user in a topic.

• identifier: The identifier of the user whose channels are to be updated.
• topicId: The ID of the topic.
• channels: An array of notification channels for the user.

8. Listing Subscriptions of a User to All Topics

You can list the subscriptions of a user to all topics.

• identifier: The identifier of the user.

Workflows

You can manage workflows using the EngagespotClient: currently, only the cancellation of a running workflow is supported.

Initialization

Before you can interact with workflows, you need to initialize the EngagespotClient with your API credentials:

Cancel a running workflow

• identifier: The identifier of the workflow.
• cancellationData: The cancellation data.

Exceptions

The SDK throws \InvalidArgumentException for missing or invalid parameters during initialization or notification creation.

Note

Replace placeholder values such as 'your-api-key', 'your-api-secret', and 'your-signing-key' with your actual Engagespot API credentials.

For detailed information about Engagespot API parameters, refer to the Engagespot API documentation.

Feel free to explore and contribute to the SDK!