Daisycon Developers
Authentication
The Daisycon API uses OAuth authentication. To get started you need a Daisycon advertiser account, publisher account, or both. After authentication your application can request data or perform actions through the API based on the permissions granted to the application.
OAuth authentication
Daisycon supports OAuth with PKCE for both advertiser and publisher accounts. The detailed implementation guide is maintained in our FAQ documentation, where you will find the latest endpoints, parameters and authentication flow examples.
Before you start
- Make sure you can log in to MyDaisycon with an advertiser or publisher account.
- Create a developer account in MyDaisycon and register your app.
- Select the permissions required for your app.
- If your application connects to multiple accounts, a separate authorization is usually required per account.
OAuth flow overview
The OAuth process consists of an authorization step and a token exchange. During this process your application receives an access token that can be used for API requests and a refresh token that allows your application to obtain a new access token when the previous one expires.
Technical details such as endpoints, parameters and code examples are documented in the FAQ guides linked above. These guides are updated when changes are made to the authentication process.
Common authentication issues
- Permission mismatch, the authenticating user does not have the permissions requested by the application.
- Redirect URI mismatch, the redirect URI used in the request does not exactly match the URI configured in the application.
- Incorrect client configuration, for example using the wrong client ID or an incorrect authentication flow.
- Outdated implementation, using older authentication examples instead of the current OAuth implementation.
If you use server-to-server authentication, you can authenticate with the Daisycon API using oAuth over CLI.
