GraphQL

The GraphQL gateway is a thin read layer over the same product services as the REST endpoints — same secret-key auth, same environments, same rate limits. Use it when a client needs a precise slice of data in one round trip; use REST for everything else (all writes, Link, AI products).

Example query

curl https://api.feelconnect.dev/v1/graphql \
  -H "Authorization: Bearer $FEELCONNECT_SECRET_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "query": "query($token: String!) { item(accessToken: $token) { itemId status institutionName accounts { accountId name type balances { current isoCurrencyCode } } transactions(count: 2) { transactionId date name amount category } } }",
    "variables": { "token": "fc_at_..." }
  }'

{
  "data": {
    "item": {
      "itemId": "item_7dJ3nWqZ5xC9vK1mTf4g",
      "status": "active",
      "institutionName": "Meridian Trust",
      "accounts": [
        {
          "accountId": "acct_9hK2mQxP7cW1nR4tYb8s",
          "name": "Everyday Checking",
          "type": "depository",
          "balances": {
            "current": 4327.18,
            "isoCurrencyCode": "USD"
          }
        }
      ],
      "transactions": [
        {
          "transactionId": "txn_3fW8kQxT1mB6nY2cRj9z",
          "date": "2026-07-24",
          "name": "GREENMART #204 SEATTLE WA",
          "amount": 84.31,
          "category": "Groceries"
        }
      ]
    }
  }
}

Schema surface

• item(accessToken) — status, institution, consented products.
• item.accounts — the same fields as /accounts/get, camelCased.
• item.transactions(count, offset, startDate, endDate) — the same fields as /transactions/get.
• Read-only: no mutations exist. Link, item management, and AI products are REST-only.
• Errors follow GraphQL conventions (errors[] in the body) but auth failures still return the REST envelope with 401.