# Ijaz API > What your technical team needs to read Ijaz data from your systems: a REST API, a Power BI connector, an MCP server, signed webhooks, and a guide to connecting through Zapier, Make and Power Automate. Every connection is read-only: no key can change anything in Ijaz, and each key reads only the datasets it was given. ## Authentication Send the key in the header Authorization: Bearer . The OData feed also accepts Basic authentication (the key as the password). Never put the key in a link or a web page. ## Limits 60 requests a minute and 10,000 a day per key. x-ratelimit-* headers on every answer, and retry-after with a 429. ## REST Base: https://ijaz.ai/api/v1 Each dataset at /api/v1/, newest first. Parameters: from and to (YYYY-MM-DD in Riyadh time, or ISO 8601), limit (1 to 500, default 100), and cursor from next_cursor for the next page. The default is the last 90 days. ## Datasets and fields ### /api/v1/mentions (Posts with tone; OData entity Mentions) Every platform post that named the company or its competitors, with its tone as Ijaz read it or your team corrected it. own_account marks the official accounts' posts, which the dashboards do not count as mentions or in share of voice. - id: string - posted_at: datetime - platform: string - url: string - author_handle: string - author_name: string - author_followers: int - text: string - lang: string - subject: string - section: string - tone: string - tone_by: string - sarcasm: bool - aspects: json - likes: int - replies: int - shares: int - views: int - parent_text: string - own_account: bool ### /api/v1/articles (News; OData entity Articles) News stories that named the company or its competitors, with the outlet's tier and the tone. - id: string - published_at: datetime - title: string - url: string - outlet: string - domain: string - lang: string - tier: int - tone: string - topic: string - subject: string - section: string ### /api/v1/stories (Stories and their level; OData entity Stories) The stories the alerts follow: their level now, the highest they reached, and their size. - id: string - last_item_at: datetime - first_at: datetime - title_ar: string - title_en: string - kind: string - level: string - peak: string - status: string - items: int - negative: int - accounts: int - tier1_press: int - closed_at: datetime ### /api/v1/alerts (Alerts; OData entity AlertEvents) The alerts' log: opened, raised, lowered, closed, notified. - id: string - at: datetime - story_id: string - title_ar: string - title_en: string - event: string - from_level: string - to_level: string ### /api/v1/reviews (Reviews; OData entity Reviews) Google Maps reviews of the branches you follow, with the rating and the tone. - id: string - posted_at: datetime - branch: string - owner: string - competitor: string - rating: int - text: string - tone: string - url: string ### /api/v1/followers (Followers, day by day; OData entity FollowersDaily) Each followed account's follower count, as read each day. - id: string - day: date - platform: string - handle: string - owner: string - competitor: string - label: string - followers: int ## OData (Power BI) /api/v1/odata lists the tables and /api/v1/odata/$metadata describes them. Each table takes $top, $skip and $filter on its time field (ge, gt, le, lt). The default is the last year. ## MCP POST https://ijaz.ai/api/mcp (JSON-RPC, Authorization: Bearer ) - list_mentions: Every platform post that named the company or its competitors, with its tone as Ijaz read it or your team corrected it. own_account marks the official accounts' posts, which the dashboards do not count as mentions or in share of voice. Fields: id, posted_at, platform, url, author_handle, author_name, author_followers, text, lang, subject, section, tone, tone_by, sarcasm, aspects, likes, replies, shares, views, parent_text, own_account. Newest first. - list_articles: News stories that named the company or its competitors, with the outlet's tier and the tone. Fields: id, published_at, title, url, outlet, domain, lang, tier, tone, topic, subject, section. Newest first. - list_stories: The stories the alerts follow: their level now, the highest they reached, and their size. Fields: id, last_item_at, first_at, title_ar, title_en, kind, level, peak, status, items, negative, accounts, tier1_press, closed_at. Newest first. - list_alert_events: The alerts' log: opened, raised, lowered, closed, notified. Fields: id, at, story_id, title_ar, title_en, event, from_level, to_level. Newest first. - list_reviews: Google Maps reviews of the branches you follow, with the rating and the tone. Fields: id, posted_at, branch, owner, competitor, rating, text, tone, url. Newest first. - list_followers_daily: Each followed account's follower count, as read each day. Fields: id, day, platform, handle, owner, competitor, label, followers. Newest first. - summary: Counts for the period: posts by tone, news by tier, open stories by level. Uses only the datasets the key may read. ## Webhooks A JSON POST with the headers ijaz-event, ijaz-delivery and ijaz-signature (t=,v1=). Compute the HMAC of "t.body" with your secret and compare, and reject anything older than 5 minutes. We retry after 1, 5 and 30 minutes, then 2, 6 and 24 hours. - alert.opened: A new alert opened on a story - alert.escalated: An open alert's level rose - alert.notified: The recipients were told of an alert, by its level - report.ready: A report is ready - audit.log: A new line in the account's activity log ## Errors 401 invalid key, 402 the account is not active (cancelled, paused, trial or paid period ended), 403 outside the plan or the key's access, 404 no such dataset, 400 invalid parameter, 429 over the limit. Body: {"error":{"code","message"}}. ## Keys and the account's status A key works while the account is active. Once the account is cancelled or paused, or its trial or paid period ends, all its keys (REST, OData and MCP) stop with a 402 and the code billing, and work again when it is renewed. A group's key follows the group's contract. ## Group keys A group key reads either one company, chosen when it is created, or every group company: today's and any added later, which the group account manager confirms when creating it. Every row carries company_id and company, and ?company= narrows a request to one company. When a company joins, its activity log records which group keys now read its data; when it leaves, the group's keys narrowed to it are revoked. Group webhooks receive every member company's events, each with company_id and company. Human-readable docs: https://ijaz.ai/developers Changelog: https://ijaz.ai/changelog?product=developers