GraphQL Primer for REST Developers

If you’re used to REST APIs, GraphQL has a few key differences worth knowing before you start. This page covers the essentials so you can make your first request quickly.

One endpoint, one method

Unlike REST, which uses many endpoints (GET /users, POST /dashboards, etc.), GraphQL uses a single endpoint for all operations:

https://{ACCOUNT}.askwisdom.ai/graphql

Every request is a POST with a JSON body containing two fields:

Field	Description
query	The GraphQL operation (query or mutation) as a string
variables	A JSON object with input values referenced in the query

curl -X POST \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer <token>" \
  -d '{
    "query": "query ListUsers($workspaceId: ID) { listUsers(workspaceId: $workspaceId) { id email } }",
    "variables": {
      "workspaceId": "workspace_123"
    }
  }' \
  https://{ACCOUNT}.askwisdom.ai/graphql

HTTP 200 does not mean success

This is the most important difference from REST. GraphQL can return HTTP 200, even when the operation fails. Do not check the HTTP status code to determine success, always inspect the response body.

Errors appear in an errors array:

{
  "errors": [
    {
      "message": "Unauthorized",
      "locations": [{ "line": 1, "column": 1 }]
    }
  ],
  "data": null
}

For mutations, also check the status.code field in the response data:

{
  "data": {
    "createUsers": {
      "status": {
        "code": "ERROR",
        "message": "User already exists"
      }
    }
  }
}

See Error handling for details.

Postman setup

To call the WisdomAI GraphQL API from Postman:

1. Set method to POST
2. URL: https://{ACCOUNT}.askwisdom.ai/graphql
3. Headers:
   • Content-Type: application/json
   • Authorization: Bearer <your_token>
4. Body → raw → JSON:
   {
     "query": "query ListUsers($workspaceId: ID) { listUsers(workspaceId: $workspaceId) { id email } }",
     "variables": {
       "workspaceId": "workspace_123"
     }
   }
   

Common mistakes

Mistake	Fix
Missing Content-Type: application/json	Always include this header — without it, the server can’t parse the body
Sending the query as a URL parameter	GraphQL queries go in the POST body, not the URL
Not requesting return fields on mutations	Include status { code message } (or other fields) in your mutation or they won’t be returned
Checking HTTP status for errors	Always read the response body. GraphQL returns HTTP 200 even on failure

Related articles

GraphQL API overview

Endpoint, authentication, and error handling

User management

Create, update, and manage users via API

Queries

Available read operations

Mutations

Available write operations