Skip to main content
Send HTTP POST requests to Hardal Signal when events occur in your mobile application.

​
API Endpoint

POST https://signal.<yourcustomdomain>.com/push/hardal
Required Header: Content-Type: application/json

​
Payload Fields

FieldTypeRequiredDescriptionExample Values
typestringYesRequest type"event", "identify"
websitestringYesYour Signal ID from Hardal dashboard"your-signal-id"
namestringYesEvent name or "identify" for user identification"screen_view", "purchase", "identify"
urlstringYesCurrent screen identifier or deep link"app://product-details/123"
titlestringYesScreen or view title"Product Details"
device_typestringYesDevice type"mobile", "tablet", "desktop"
platformstringYesPlatform type"app", "web", "server"
languagestringNoUser’s language"en-US", "tr-TR"
dataobjectNoCustom parameters and event data{"transaction_id": "TX123", "value": 99.95}

​
Identify Function

Use "type": "identify" to link user identity to their sessions and activity. Set name field to "identify" and include user data like email, user_id, or profile information in the data object.

​
User Identification with Distinct Event

Send a distinct event to update user session properties and identify users after login, signup, or marketing consent: 
{
  "type": "identify",
  "website": "your-signal-id",
  "name": "distinct", 
  "url": "app://current-screen",
  "title": "Current Screen Title",
  "device_type": "mobile",
  "platform": "app",
  "data": {
    "email": "[email protected]",
    "name": "John Doe",
    "plan": "premium", 
    "user_id": "12345"
  }
}
When to use distinct events:
  • After user login or signup
  • When user provides marketing consent
  • When user profile information is updated
  • To link anonymous sessions to identified users
The distinct event updates the user’s session properties, allowing you to identify and track users across their mobile app journey.

​
Custom Events & Examples

For detailed custom event tracking examples, payload structures, and advanced usage:

Data Sending API Documentation

Complete guide with examples for tracking purchases, conversions, and custom events

​
Response Codes

  • 200: Success - Event recorded
  • 400: Invalid request format
  • 401: Invalid Signal ID