GET /v1/agents/knowledge/sources

What agents answer from: articles, FAQs, files and websites.

Everything in Knowledge — the sources agents answer from — newest first.

Needs the agents.knowledge:read scope.

Query parameters

Field	Type	Required	Notes
kind	string	No	article, faq, file or website.
collection	integer	No	Only this collection’s.
limit	integer	No	1 to 100; 50 by default.
starting_after	string	No	The last id of the previous page — next from it.

Request

cURL

curl "https://api.fireflo.au/v1/agents/knowledge/sources?kind=faq&collection=3" \
  -H "Authorization: Bearer $OMNI_API_KEY"

Response

200 OK — has_more says whether there is another page, and next is the starting_after for it. A source has its id, kind (article, faq, file or website), title (an FAQ’s question), its collection, whether agents use it (active) and when it last changed. status is processing while it is read, then ready — or failed, with the reason in error. An article or FAQ has its body; a website its url, how often it is checked for changes (refresh) and how many pages it reads; a file its file type and size in bytes.

{
  "data": [
    {
      "id": "b7e4c1d2-5a3f-4e8b-9c6d-1a2f3e4b5c6d",
      "kind": "faq",
      "title": "How long does a refund take?",
      "collection": {
        "id": 3,
        "name": "Returns & warranty"
      },
      "status": "ready",
      "error": "",
      "active": true,
      "updated_at": "2026-10-01T15:12:09+05:30",
      "body": "Refunds reach your account 5–7 working days after we receive the item. UPI refunds are usually faster."
    }
  ],
  "has_more": false,
  "next": null
}

Errors

Every refusal is {"error": {"code", "message", "field"}}; field is there when one input is at fault.

Status	Error code	When
400	invalid_request	limit is out of range, or starting_after isn’t an id from this list; field names it.
404	module_off	The account doesn’t have AI agents on: they aren’t in its plan, or are switched off for it.
403	scope_missing	The key doesn’t have the agents.knowledge:read scope.

Any request can also be refused for its key, its account or its rate (key_required, invalid_key, account_suspended, plan_excludes_api, address_not_allowed, rate_limited); see the overview.