myDSP API: How to Authenticate, Create Campaigns, and Get Reports

This article provides a summary of how to access and integrate with the myDSP API, including authentication, campaign setup, and reporting. For the most up-to-date details and code samples, please refer to our Full API Documentation.

🔐 Authentication

To use the myDSP API, you must first request your client ID and client secret from Yeesshh Support.

Once you have your credentials, generate a temporary token by sending a request to:

Endpoint:
GET /v2/oauth/token
Include your credentials using HTTP Basic Authentication.

You will receive a JWT token. This token must be used in the Authorization header for all further API requests.

📦 Campaign Management

To create a campaign:

Endpoint:
POST /v2/campaign

You must include required fields such as:

• Campaign title and URL

• Format (pop or branded)

• Status (Active or Paused)

• Targeting: countries, devices, browsers, operating systems

• Budget settings and frequency control

• Optional: adult content flags, traffic types, domain/subid/publisher targeting, bid adjustments

You can also:

• View a campaign: GET /v2/campaign/{id}

• Update a campaign: PUT /v2/campaign/{id}

• List all campaigns: GET /v2/campaign

• Clone a campaign: GET /v2/campaign/clone/{id}

• Delete a campaign: DELETE /v2/campaign/{id}

Note: If you use automatic blacklisting, a conversion pixel must be set up. Contact support for help with this.

📊 Reporting

To retrieve performance reports:

Endpoint:
POST /v2/report/get-report

You can generate reports by:

• Day

• Campaign

• Publisher

• SubID

Use filters like:

• Date range (date_from, date_to)

• Campaign IDs

• Country codes

Each report returns:

• Impressions or clicks

• Spend

• Campaign or publisher identifiers

📎 More Information

For complete details about request structure, available parameters, and full sample responses, please refer to the complete myDSP API documentation.

If you have questions or need access credentials, contact Yeesshh Support.