Graphql endpoint not working at dispatcher | Community
Skip to main content
R
ramaem12
New Participant
May 18, 2023
Solved

Graphql endpoint not working at dispatcher

  • May 18, 2023
  • 2 replies
  • 1328 views

Version: AMS 6.5.16


Hi,

I am trying to access newly created Graphql over the dispatcher, when i try to access the same url publish i see the same results but not in dispatcher

I followed below steps to create and publish with Graphql

 

  1. Created Custom CF model
  2. Created couple of CF's in dam folder with data
  3. Created new endpoint under the /Assets/Graphql and published( selected my project as end point where i created the new cf's)
  4. Created Persisted Query under /General/GraphQL Query Editor.

author/graphql/execute.json/myproject/test2
publish/graphql/execute.json/myproject/test2

When i copied the URL and paste it in new tab it is showing the data in both author and publish but not able to access over the dispacther.
( I am getting 404 error)

Can someone explain what are the steps i need to perform here to access over the dispatcher?

FYI - I am not using any authentication for now, just want to access the JSON structure from dispatcher

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 aanchal-sikka

Hello @ramaem12 

 

It appears that the GraphQL endpoint is blocked on the dispatcher.

Please check the filter section to assure that its allowed. Example:

# GraphQL Persisted Queries & preflight requests
/0061 { /type "allow" /method '(GET|POST|OPTIONS)' /url "/graphql/execute.json*" }

Also, please review if you would want to avoid caching of the GraphQL queries.

2 replies

aanchal-sikka
aanchal-sikkaAccepted solution
New Participant
May 21, 2023

Hello @ramaem12 

 

It appears that the GraphQL endpoint is blocked on the dispatcher.

Please check the filter section to assure that its allowed. Example:

# GraphQL Persisted Queries & preflight requests
/0061 { /type "allow" /method '(GET|POST|OPTIONS)' /url "/graphql/execute.json*" }

Also, please review if you would want to avoid caching of the GraphQL queries.

Aanchal Sikka
    iamnjain
    iamnjain
    New Participant
    June 1, 2023

    Hi @ramaem12 

     

    As mentioned by aanchal, this is the only reason I also faced in my project. You need to allow in filter section at dispatcher level and It will resolve your issue.

      R
      RahulVa4
      New Participant
      May 19, 2023

      you mostly can access the dispatcher through API call's using the endpoints just try using the postman might work

       

        Terms & ConditionsAccessibility statement

        Loading footer...