oAuth over CLI

If you use server-to-server authentication, you can authenticate with the Daisycon API using oAuth over CLI. This method allows you to complete the oAuth flow without running a public web server.

The CLI authentication flow is useful for backend scripts, cron jobs, and other server environments where browser based redirects are not practical.

Getting started

Before starting with CLI authentication, you need to:

• Create a developer account
• Create an API app
• Configure the required API permissions

During the creation of your app, make sure you only request the permissions that your application actually needs. The user who authorizes the app must also have these permissions in their account.

CLI redirect URI

When configuring your app, you can use the Daisycon CLI redirect URI:

https://login.daisycon.com/oauth/cli

This endpoint will display the authorization code in the browser so it can be copied back into your terminal.

Example CLI implementation

Daisycon provides example implementations to simplify the CLI authentication process:

• PHP oAuth CLI example
• Javascript / Node.js oAuth client

These examples guide you through generating the authorization URL, logging in through the browser, and exchanging the authorization code for an access token and refresh token.

Detailed CLI authentication guide

For a full step-by-step explanation of the CLI authentication flow, including example commands and screenshots, see the detailed guides in the Daisycon FAQ:

• oAuth authentication over CLI for advertisers
• oAuth over CLI for publishers

These guides explain the full flow, including how to generate tokens and automate API requests using refresh tokens.