---
schema_version: "1"
id: b4e2075eab3af67355e4b7f67b1ebec88364237487fc0c52b35e9c3effa8d8f1
title: API Reference
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/data-cloud/data-cloud-engagement-mobile-sdk/guides/c360a-api-engagement-mobile-sdk-api-reference.md
canonical_url: https://developer.salesforce.com/docs/data/data-cloud-engagement-mobile-sdk/guide/c360a-api-engagement-mobile-sdk-api-reference.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: ed320b55689b5e762a055ab3c0c09f009e2ea0c5352f73126c8dec10ab73f74f
products:
  - Data 360 Engagement Mobile SDK
  - Data 360 Developer Documentation
---
# API Reference

This section provides comprehensive documentation for the Engagement Mobile SDK APIs and features.

- [**Initialization**](https://developer.salesforce.com/docs/data/data-cloud-engagement-mobile-sdk/guide/c360a-api-engagement-mobile-sdk-initialization.md)

  - : Configure the Data Cloud Module before using any API services. Use `CdpConfigBuilder` (iOS) or `CdpConfig.Builder` (Android) to build your SDK configuration with required settings like `appId` and endpoint from your Mobile Connector. Optionally, configure the `trackScreens`, `trackLifecycle`, and `sessionTimeoutInSeconds` settings.

- [**Capturing Engagement Data**](https://developer.salesforce.com/docs/data/data-cloud-engagement-mobile-sdk/guide/c360a-api-engagement-mobile-sdk-capturing-engagement-data.md)

  - : Collect granular data about customer mobile app interactions through comprehensive event tracking capabilities.

- [**Capturing Profile Data**](https://developer.salesforce.com/docs/data/data-cloud-engagement-mobile-sdk/guide/c360a-api-engagement-mobile-sdk-capturing-profile-data.md)

  - : Gather profile data through the SDK's Identity APIs to build comprehensive customer profiles.

- [**Capturing Behavior Data**](https://developer.salesforce.com/docs/data/data-cloud-engagement-mobile-sdk/guide/c360a-api-engagement-mobile-sdk-capturing-behavior-data.md)

  - : Track detailed customer behavior patterns and mobile app interactions through advanced event tracking.

- [**Consent Management**](https://developer.salesforce.com/docs/data/data-cloud-engagement-mobile-sdk/guide/c360a-api-engagement-mobile-sdk-consent-management.md)

  - : Implement managed consent solutions for data collection. Your mobile application handles presenting opt-in or opt-out choices to users and sets the Data 360 Module consent property accordingly.

- [**Location Tracking**](https://developer.salesforce.com/docs/data/data-cloud-engagement-mobile-sdk/guide/c360a-api-engagement-mobile-sdk-location-tracking.md)

  - : Enable location tracking for all events using the `setLocation` method. Configure `coordinates` and `expiresIn` parameters for precise location data collection.

- [**Logging and Debugging**](https://developer.salesforce.com/docs/data/data-cloud-engagement-mobile-sdk/guide/c360a-api-engagement-mobile-sdk-logging-and-debugging.md)

  - : Configure SDK logging for development and debugging. Use `setLogger` (iOS) or `setLogging` (Android) on the `SFMCSdk` instance to enable logging with customizable logging levels and output destinations. Logs are captured using the native unified logging system.

- [**Post Data from an Authenticated Server-to-Server Connection**](https://developer.salesforce.com/docs/data/data-cloud-engagement-mobile-sdk/guide/c360a-api-engagement-web-mobile-sdk-authenticated-server-to-server.md)

  - : Use the `POST` method to send event data through an authenticated server-to-server connection. Use a server-to-server connection when your server already collects engagement data that you want to forward to Data 360 or when you require an authenticated connection.

- [**Post Data from an Unauthenticated Server-to-Server Connection**](https://developer.salesforce.com/docs/data/data-cloud-engagement-mobile-sdk/guide/c360a-api-engagement-web-mobile-sdk-unauthenticated-server-to-server.md)

  - : Use the `POST` method to send event data through an unauthenticated server-to-server connection. Use an unauthenticated server-to-server connection when your server already collects engagement data that you want to forward to Data 360 and you don’t require an authenticated connection.