فوتّر

فوتّر Orgs API

The Orgs API from فوتّر — 2 operation(s) for orgs.

GitHub OpenAPI

Operations 2

POST /api/v1/orgs Create an unverified prepaid workspace #
POST /api/v1/orgs/claim Claim with an existing verified Supabase session and obtain a live key #

Specifications

⚙
OpenAPI
https://artifacts.apis.io/fawtar-app/openapi/fawtar-app-orgs-api-openapi.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/fawtar-app:fawtar-app-orgs-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

fawtar-app-orgs-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Fawtar Business Orgs API
  x-capabilities: https://fawtar.app/.well-known/fawtar-capabilities.json
  version: 1.0.0
  description: 'Arabic-first invoicing, accounting, payroll and point of sale for Saudi businesses. Invoice QR fields do not establish full system compliance or Phase 2 integration. Filtering and sorting follow ransack conventions, and the API-KEY header is accepted alongside Authorization: Bearer, so a client written against Qoyod can be repointed here by changing the base URL and the key. Agent capabilities, sandbox onboarding and prepaid prices: https://fawtar.app/.well-known/fawtar-capabilities.json'
  contact:
    name: Fawtar
    url: https://fawtar.app/docs/api
servers:
- url: https://fawtar.app
security:
- bearerAuth: []
tags:
- name: Orgs
paths:
  /api/v1/orgs:
    post:
      operationId: createAgentOrganization
      summary: Create an unverified prepaid workspace
      security: []
      description: Anonymous callers get a pending org and existing signup/login claim URL, never a live key. A provider-verified Supabase session for the same email can receive a live key. Existing owners use Integrations. Claiming is not taxpayer verification. Three requests/IP/day.
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                email:
                  type: string
                  format: email
                name:
                  type: string
                  minLength: 1
                  maxLength: 120
              required:
              - email
              - name
              additionalProperties: false
      responses:
        '201':
          description: Unverified organization and claim URLs or scoped live key for verified session
          content:
            application/json:
              schema:
                type: object
                additionalProperties: true
        '403':
          description: Email mismatch/unverified
          content:
            application/json:
              schema:
                type: object
                additionalProperties: true
        '409':
          description: Already owns an org
          content:
            application/json:
              schema:
                type: object
                additionalProperties: true
        '422':
          description: Invalid input
          content:
            application/json:
              schema:
                type: object
                additionalProperties: true
        '429':
          description: Issuance cap reached
          content:
            application/json:
              schema:
                type: object
                additionalProperties: true
        '503':
          description: Unavailable
          content:
            application/json:
              schema:
                type: object
                additionalProperties: true
      tags:
      - Orgs
  /api/v1/orgs/claim:
    post:
      operationId: claimAgentOrganization
      summary: Claim with an existing verified Supabase session and obtain a live key
      security:
      - supabaseSession: []
      description: Use a Supabase access token in Authorization (or the normal login cookie). The email must match the pending org. Tax invoices and ZATCA remain blocked until separate fiscal verification.
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                token:
                  type: string
                  minLength: 43
                  maxLength: 43
              required:
              - token
              additionalProperties: false
      responses:
        '201':
          description: Claimed unverified org and one-time secret live API key
          content:
            application/json:
              schema:
                type: object
                additionalProperties: true
        '401':
          description: Verified session required
          content:
            application/json:
              schema:
                type: object
                additionalProperties: true
        '409':
          description: Invalid/expired claim or another owned org
          content:
            application/json:
              schema:
                type: object
                additionalProperties: true
        '429':
          description: Issuance cap reached
          content:
            application/json:
              schema:
                type: object
                additionalProperties: true
      tags:
      - Orgs
components:
  securitySchemes:
    supabaseSession:
      type: http
      scheme: bearer
      description: Provider-verified Supabase access token, for onboarding claims only.
    bearerAuth:
      type: http
      scheme: bearer
      description: 'Authorization: Bearer fwt_live_… or fwt_test_…'
    apiKeyHeader:
      type: apiKey
      in: header
      name: API-KEY
      description: Qoyod-compatible header carrying the same key.