Hello Kakao Ads API Support Team,
We are integrating with the Kakao Ads API within Salesforce and have encountered an issue with the OAuth authorization flow.
Issue Description: When users authenticate through the Kakao authorization URL, the consent screen only displays 10 accounts, even though the user has access to more accounts in their Kakao Ads Manager. We expected all accessible accounts to be presented during the authorization flow.
Current Behavior:
Authorization URL presents a maximum of 10 accounts in the consent screen
Additional accounts that the user has access to are not visible
Expected Behavior:
All accounts that the user has access to should be displayed in the consent screen
Or, if there is a pagination mechanism, it should be available to view additional accounts
Questions:
Is the 10-account limit an intentional restriction on the authorization consent screen?
If yes, is there a recommended approach to allow users to authorize access to their remaining accounts?
Is there a separate API endpoint or parameter that enables pagination or displays all accounts during authorization?
Are there any specific scopes or permissions required to view all available accounts?
Typically, approximately 10 to 20 business assets are displayed at a time.
May we ask whether the account used for the business verification is the same account associated with your inquiry?
(This will help us estimate the number of assets that may be expected to appear on the consent screen.)
It’s not the same account associated with the inquiry. Our client has more than 10 accounts, but they can only see the first 10 accounts in the consent screen.
We understand that only the first 10 accounts are currently displayed on the consent screen. We will review whether this behavior can be improved and will get back to you once we have completed our assessment.
Could you please let us know approximately how many ad accounts are associated with the client’s account?
At the moment, we are considering increasing the display limit to up to 30 accounts from a UX perspective. However, we would like to better understand real-world usage patterns and estimate an appropriate maximum number of accounts to display.
As a separate note, if the user’s ad account IDs are known in advance, it is possible to specify them when requesting the Business Authorization Code.
When account IDs are provided, the consent screen will display only those specified accounts rather than the full list. Depending on your use case, this may serve as an alternative approach.
This does not work in our case, because the authentication comes before the account selection
Is there any update on this matter, any change or suggestion or workaround
With this update, up to 30 accounts will be displayed.
If you need to view more than 30 accounts, please proceed with issuing a Business Token as well. This will allow us to identify the relevant users and verify the number of associated accounts.
I will inform our customer, they just got back to me that they have 50 accounts
What do you mean please proceed with issuing a Business Token as well ? They do have a business token
I am reaching out because I recently discovered logs showing authorization code requests without any associated Business Token issuance, which led me to mistakenly believe that no Business Token had been issued.
After reviewing the issuance history, I have confirmed that a Business Token was indeed issued. Therefore, I would appreciate it if you could kindly disregard my previous request.
Additionally, we will further review the possibility of increasing the displayed account limit to 50 accounts.
I informed the customer and they’re really pleased for this quick support.
I still have a general question, can you support maybe a pagination on the const screen? or a text box for adding manual account id? for case in the future we have a customer with more than 50 accounts?
We are currently considering various potential improvements to the user experience, including the lookup functionality you mentioned, as well as possible enhancements such as pagination and more streamlined processes for managing access permissions across all accounts.
At this stage, we are carefully reviewing these ideas and exploring what can be implemented within applicable legal and policy constraints, with the goal of improving overall usability and user experience.
However, please note that we are not yet able to provide a timeline for when these changes may be implemented. We kindly ask for your understanding in this regard.
