Adobe Analytics Api 2.0. Profile is not valid error | Community
Skip to main content
D
DavidShiel_d
New Participant
May 22, 2019
Solved

Adobe Analytics Api 2.0. Profile is not valid error

  • May 22, 2019
  • 4 replies
  • 7839 views

Hi,

I am upgrading form API 1.4 to API 2.0.

The problem is that except for "discover me api", I cannot use anything else and get:

{

    "error_code": "403025",

    "message": "Profile is not valid"

}

I am using a sandbox account.

Any information?

Thanks

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by seburke1

Hi Davidw50065164,

My initial suggestion would be that your adobe.io integration doesn't have proper permissions or is a part of a product profile in Admin Console that has the proper permissions.  In Admin Console if you are a product admin or system admin.  In an Analytics product profile, you need to make sure permissions have web services things as well as any report suites and things you need to access.  Then in the integrations tab in that profile you need to make sure your adobe.io integration is added there.  Worth noting you do need a separate Adobe.IO integration for each Experience Cloud organization.

I hope that helps,

Seth

4 replies

D
DavidShiel_dAuthor
New Participant
May 23, 2019

Hi Settytb,

According to your response, I think I have all the permissions setup. In my first few screenshots, I can use the "discover me" method to get the information for my company and it works good. I think this has proved that the OAuth token I get is correct.

The problem is I copy and paste the company id I get and use it in other methods but none of them works.

U
user01447
New Participant
January 5, 2022

Hi David,

 

We are facing exactly the same issue that you have reported here. Can you help us with what fixed the issue for you.

 

Thanks,

    S
    seburke1
    Employee
    May 23, 2019

    Hi davidw50065164,

    Good points, the oauth integration uses the users permissions that you authenticate with.  So, when you hit the oauth it will prompt you to follow the login workflow.  You will need to make sure that your user that you logged in with is a user in that profile that you showed in the screenshot that has all the permissions.  Adding the integrations is specifically for service token/jwt integrations.  Because they behave as their own user, you need to give them access to a profile for permissions.  But, because you used oauth that uses your own adobe permissions for the user you authenticated through. If all that is in order, than it may not be a product profile/permission issue.

    I hope that helps,

    Seth

    D
    DavidShiel_dAuthor
    New Participant
    May 23, 2019

    Hi Settytb,

    Can you help me make sure I have the permission, if not, how should i grant that.

    In Adobe Admin Console, I have included all the permissions that I have seen.

    Worth noticing that I have three integrations inside Adobe IO console. However, under Integrations tab, I cannot find the integration for the OAuth connection. I create that integration by following the tutorial.

    S
    seburke1Accepted solution
    Employee
    May 23, 2019

    Hi Davidw50065164,

    My initial suggestion would be that your adobe.io integration doesn't have proper permissions or is a part of a product profile in Admin Console that has the proper permissions.  In Admin Console if you are a product admin or system admin.  In an Analytics product profile, you need to make sure permissions have web services things as well as any report suites and things you need to access.  Then in the integrations tab in that profile you need to make sure your adobe.io integration is added there.  Worth noting you do need a separate Adobe.IO integration for each Experience Cloud organization.

    I hope that helps,

    Seth

    Terms & ConditionsAccessibility statement

    Loading footer...