resource_ids values (if required for those scopes)
From the docs I can say that these details should have been configured for our app but isn’t. Could you guide us on from where can we get the above values?
The three settings required to issue a Business Authentication Token can be checked and configured in the Kakao Developers Console.
1. Business Authentication Redirect URI registration
You can register the Business Authentication Redirect URI under the app key you are currently using.
Please register the URI of the service server that will receive the Business Authorization Code.
2. Approved scope v alues for our app
If the resource_ids parameter is not provided, the user will be asked to grant access to all available resources.
3. resource_ids values (if required for those scopes)
Since you have the required Moment permissions, you can configure resource access requests for both Kakao Moment and Keyword Ad
We are building our own integration for sending audiences to Kakao
Audiences will be exported from Nike S3 to kakao custom data API.
A scheduled job (DAG) reads S3 and calls the Customer Data API (e.g. POST ``https://apis.moment.kakao.com/openapi/v4/customerData) to upload identifiers for Moment targeting.
Our Kakao Developers app is already set up by our cloud team:
App name: Adobe Experience Platform
App ID:1384833 (Biz app)
Authentication (needs confirmation)
The docs describe Business Authentication (GET authorize → POST token → use business access token on Moment APIs). For a fully automated DAG, it is unclear how this should work in practice. We want to confirm the intended pattern with Kakao.
Authorize URL we plan to use — is this correct?
Questions
For server-side scheduled uploads (no user in the loop per run), is the intended model a one-time (or occasional) “bootstrap” where a human opens the authorize URL, agrees on the consent screen, and our callback URL receives code — and only then our backend exchanges code for access_token and stores it for the DAG??
Can the DAG call Customer Data APIs using only a stored business access_token (+ adAccountId header), with no browser step on each run? If yes, what is the recommended token lifecycle (expiry, revocation, re-consent)? Docs mention no refresh token — what should advertisers do for daily/weekly audience sync??
redirect_uri: Must this be implemented and registered by the app owner under Platform key → Business Authentication redirect URI? For an advertiser using an enterprise app (App ID 1384833), who should register and host the callback — advertiser vs platform vendor??
code: Confirm it is returned only as a query parameter on redirect to redirect_uri (e.g. ?code=...&state=...), not via any other channel. Any TTL / one-time use constraints we should implement?
For Customer Data create/update only, is scope=moment_management sufficient, or is moment_delete also required for PUT updates?
Confirm resource_ids=moment:{adAccountId} for a single ad account, and where the advertiser should obtain the numeric ad account ID (not Developers App ID).
Any additional app approvals beyond Biz app + Request additional features (Kakao Moment) for the Customer data management APIs?
The URL you provided is the URI to which you were redirected for Kakao Account login when attempting Business Authentication. Please refer to the guide below and use the URL for requesting a business authorization code.
Business Authentication uses OAuth 2.0 and is not limited to one-time use. You can obtain a business authentication token and continue using it. You must revoke the token when you no longer need it. There is a limit on the maximum number of tokens that can be issued.
Business Authentication does not provide refresh tokens. You can revoke tokens directly. An access token only grants access to API resources; advertisers’ data is handled through the Kakao Moment API.
Either an advertiser or a hosting provider can implement Business Authentication. The data you can retrieve is limited to the ad account used for Business Authentication.
This follows the OAuth 2.0 standard, and the authorization code is provided only as a query parameter. To enhance the security of the single-use authorization code, please refer to the security recommendations below.