The Pontiac API (Application Programming Interface) allows users to interact with Pontiac programmatically and integrate Pontiac’s ad buying and reporting capabilities into external applications.

Using the API, developers can automate workflows such as:

• Creating Advertisers, Campaigns, Lines, Creatives, and Pixels
• Managing campaign settings and targeting
• Retrieving reporting and performance data
• Updating and optimizing active campaigns

API integration is intended for users or teams with development resources who want to incorporate Pontiac functionality into their own systems rather than completing every action through the Pontiac user interface.

Common use cases include:

• Publishers: Integrate Pontiac into an existing platform to allow advertisers to extend campaigns beyond the publisher’s owned properties and access programmatic inventory.
• Agencies: Connect proprietary planning, reporting, or insertion order systems to automate campaign creation and management.
• Trading Desks: Build custom workflows for campaign creation, reporting, bidding, and optimization.

If you are interested in using the Pontiac API, contact your Account Manager or reach out through the Help Center for additional information and access.

API Environments

Pontiac provides both production and sandbox environments.

Production

Use the production environment for live campaign activity.

API Documentation:
https://api.pontiac.media/docs/

The API documentation provides the available endpoints, request parameters, object structures, and response schemas.

Sandbox

The sandbox environment can be used to develop and test an integration without affecting live campaigns or production spend.

You can also log in to the sandbox interface to confirm that objects created or updated through API requests are appearing as expected.

Sandbox Interface:
https://sandbox.pontiac.media

Sandbox API Documentation:
https://sandbox.pontiac.media:1070/docs/

When developing an integration, we recommend testing requests in the sandbox before moving the workflow to production.

You can use the sandbox just like the regular production environment without the risk of spending any money. You can also login to the sandbox as if it were our normal ui to make sure that your calls are going through correctly.

Sandbox Interface:
https://sandbox.pontiac.media

Sandbox API Documentation:
https://sandbox.pontiac.media:1070/docs/

When developing an integration, we recommend testing requests in the sandbox before moving the workflow to production.

Using the Examples in This Guide

The examples throughout this guide use cURL.

cURL is a command-line tool for sending HTTP requests and can be used to interact directly with Pontiac’s API endpoints.

For example:

curl -X GET \
  'https://api.pontiac.media/rtb/advertisers' \
  -H 'accept: application/json' \
  -H 'auth: YOUR_AUTH_TOKEN'

The same API requests can also be made using other HTTP clients or incorporated into applications written in languages such as Python, JavaScript, Java, or PHP.

Modern versions of Windows, macOS, and Linux support cURL from the command line, although the exact command-line environment may vary by operating system.

Authentication and Security

API requests require authentication. After successfully authenticating, use the returned authentication token for subsequent requests as demonstrated in the examples throughout this guide.

Treat API usernames, passwords, and authentication tokens as sensitive credentials.

Do not share authentication tokens publicly or submit authenticated Pontiac API requests through untrusted third-party request tools.

The following walkthrough demonstrates the process of authenticating and then creating the core objects needed to launch a Campaign through the Pontiac API.

Additional Resources

Cygwin
https://www.cygwin.com/

Tutorial for setting up unix commands for windows
https://www.howtogeek.com/249966/how-to-install-and-use-the-linux-bash-shell-on-windows-10/

Online curl tool
https://reqbin.com/curl