DOMO Server side filtering

muhammadtalha

I am trying to make a programmatic filter, accesscode is generating successfully, but when i try to get the private dashboard, using this api endpoint (https://api.domo.com/v1/cards/embed/auth) I am hgetting the following error.

The doc I am following is: https://developer.domo.com/portal/1yafxad1u8azv-programmatic-filtering

muhammadtalha

@Matt Tannyhill , @GrantSmith @ArborRose can you guys please help me in this matter. Its a bit turgent

ArborRose

Seems the user associated with the clientId and clientSecret credentials does not have permission to access the card in the dashboard.

Make sure the user has access to the dashboard or card you are trying to embed. At least view permissions.

Check if you are generating an embed token or a private dashboard or card that the user doesn't have right to view. You could test by logging into Domo with the same credentials as your API client.

Recheck documentation and filtering for any permission issues you may have overlooked. Perhaps try creating a simple card that you know the API user has access to. Use that cards ID to see if the filtering API call works.

muhammadtalha

I have already given access to my API client all the things. As below.

And while making an embedded link, I am getting it in a private like this. What else you suggest I will do, and this dashboard is build by me,

I am not sure what else I am missing!

@ArborRose

ArborRose

I am saying review the permissions on the card, not the share/embed. The client and secret are used for API calls. The error seems to indicate that the specific card in the dashboard does not allow access to the entity using the token.

muhammadtalha

Can you please help me to redirect from where I can check cards access? Its weird though, because I am creating cards and token with my same credentials! @ArborRose

GrantSmith

Essentially, the error tells you that the user who created the API Client (client ID and secret) doesn't have access to some of the cards on the page you're embedding. I'd try to unshare and reshare the page with the user and confirm that the embed ID is correct.

The scopes on the client just tells the API which API resources the client is able to access. This is to enhance security to allow specific clients access specific parts of the api.

muhammadtalha

Thanks @GrantSmith yes I am getting this point and I am the sole owner of this dashboard which I am trying to embedd and with those same credentials I created the client ID and Secret. Can you please help me to just check from where I can check the permissions that whether my user has permission to access the cards or not. with screenshot may be, it will be really helpful. Thanks a lot.

Place from where i can see I am the only one who owns this card

GrantSmith

It's definitely shared with your user.

Next steps to confirm I'd recommend going to https://developer.domo.com/manage-clients and logging out if you're already logged in, then log back in making sure you're using your user when you're logging in. You can then confirm the client ID and Secret that you're using with your embed are the same as what you're seeing in the client management area.

If those align, then you'll want to check the access token that you're generating to make sure it's actually generating an access token.

You could also attempt to follow Domo's sample code here and plug in your codes there: https://github.com/domoinc/domo-node-embed-filters

rdgdev

I am also receiving this same API response.

To try to isolate I've created a test dashboard with just static content and selected private embed.

I've logged out of developer.domo.com and logged back in again and created a new client.

I have Admin role within my company account.

I checked company.domo.com/admin/api-clients and confirmed the API client shows there with my user as owner.

I am using the sample PHP code and added client id, secret and embed ID from above steps. I've checked the request and ensured that the access token returned from the initial api.domo.com/oauth/token request is properly supplied to the api.domo.com/v1/cards/embed/auth request in the Authorization header.

I am curious if there was a solution found to this problem, or if anyone has any other ideas. Thanks!

rdgdev

I am also receiving this same API response.

To try to isolate I've created a test dashboard with just static content and selected private embed.

I've logged out of developer.domo.com and logged back in again and created a new client.

I have Admin role within my company account.

I checked company.domo.com/admin/api-clients and confirmed the API client shows there with my user as owner.

I am using the sample PHP code and added client id, secret and embed ID from above steps. I've checked the request and ensured that the access token returned from the initial api.domo.com/oauth/token request is properly supplied to the api.domo.com/v1/cards/embed/auth request in the Authorization header.

I am curious if there was a solution found to this problem, or if anyone has any other ideas. Thanks!

rdgdev

I am also receiving this same API response.

To try to isolate I've created a test dashboard with just static content and selected private embed.

I've logged out of developer.domo.com and logged back in again and created a new client.

I have Admin role within my company account.

I checked company.domo.com/admin/api-clients and confirmed the API client shows there with my user as owner.

I am using the sample PHP code and added client id, secret and embed ID from above steps. I've checked the request and ensured that the access token returned from the initial api.domo.com/oauth/token request is properly supplied to the api.domo.com/v1/cards/embed/auth request in the Authorization header.

I am curious if there was a solution found to this problem, or if anyone has any other ideas. Thanks!