Overview
The Adrop REST API allows you to request ads directly from the server-side without using an SDK. This is useful when integrating ads with web servers, backend services, or platforms that don’t support SDKs.Basic Information
| Item | Value |
|---|---|
| Base URL | https://api-v2.adrop.io |
| Protocol | HTTPS |
| Authentication | App Key (Authorization header) |
Authentication Setup
An App Key is required to use the API.Getting Your App Key
- Log in to the Adrop Console
- Navigate to the Settings tab
- Download the platform-specific
adrop_service.jsonfrom the App menu - Find your App Key in the JSON file
Authorization Header
Include theAuthorization header in all API requests:
Common Parameters
Required Parameters
| Parameter | Type | Description |
|---|---|---|
unit | STRING | Ad unit ID |
Recommended Parameters
| Parameter | Type | Description |
|---|---|---|
uid | STRING | User unique identifier |
pf | STRING | Platform (android, ios, web) |
lcl | STRING | Locale (e.g., en_US, ko_KR) |
Optional Parameters
| Parameter | Type | Description |
|---|---|---|
theme | STRING | Theme mode (light, dark) |
adId | STRING | Advertising identifier (ADID/IDFA) |
contextId | STRING | Context targeting ID |
The
uid parameter is used for controlling ad frequency per user and mapping targeting information. Accurate targeting may not be possible without it.Supported Ad Formats
Banner Ads
Returned as HTML for direct web rendering
Native Ads
Returned as structured data for custom UI implementation
Related Documentation
Targeting Settings
User properties and context targeting configuration
Event Tracking
Send user behavior events and track conversions
Error Codes
API error codes and troubleshooting