Developer

The Swrve Events API is a series of REST calls for sending event data to Swrve from your app. API calls – API key and user ID Swrve authenticates all API calls to *api.swrve.com using either your app API key or Identity key. This article references Swrve’s URLs for all data and content stored in both Read More

You can add and send a custom event payload (swrve_payload) with every REST and SDK call to <app_id>.api.swrve.com (<app_id>.eu-api.swrve.com). This parameter is optional. This feature enables graphing of low-cardinality data. For example, creating a histogram that shows the artist a user is currently listening to when a particular event is fired. The payload histogram feature is available Read More

The Swrve A/B Test API enables you to fetch resources held in the Swrve service according to the different variations that are available to each user in the app. The resources are returned in JSON format. This article references Swrve’s URLs for all data and content stored in both our US and EU data centers. Read More

This article explains how to send and access referrer information through the Swrve user acquisition campaign tracker. In order to make use of the functionality mentioned in this article, you must have access to the app’s API key and your personal key. For more information, see Where do I find my API key and personal Read More

The Swrve Push API lets you send push notifications to a single Swrve user via a web API call. While Swrve’s standard push notification service allows you to target a behavioral group of users at a predefined schedule from within Swrve, the Swrve Push API lets you send push notifications to individual users in response Read More

The Swrve Message Center is an API for campaigns that have been downloaded from Swrve and are intended to be accessible in a way where the app user is in control of the message lifecycle. This guide describes how the Message Center API is presented for iOS, Android and Unity. Accessing the API Once the Swrve instance Read More

Swrve allows for a session token that is a hash of your API key in the calls you make. All API calls to <app_id>.api.swrve.com are authenticated using a session token of the form app_id=user_id=timestamp=md5hash. Note that API calls to abtest.swrve.com/api/1 do not use a session token, but instead simply use the API key. The fields Read More

The Swrve Geoplace API is a series of REST calls for creating geoplaces in Swrve to use as triggers for your geo-triggered notification campaigns. Required URL parameters The following parameters are required for all API calls, in addition to those listed per method. Parameter Description api_key The API key of your app, as displayed on Read More