Skip to content

GraphQL API

The primary API for every Flowtig application.

GraphQL is the primary interface for building applications on the Flowtig platform.

Every business application—including Contacts, Worktime, Time Tracking, Invoices and Warehouse—communicates through GraphQL. The API provides strongly typed access to tenant-specific business data while enforcing permissions and organisational boundaries automatically.

Application API

If you're building a Flowtig application, GraphQL will be your primary API.

Business logic belongs in GraphQL.


Why GraphQL?

Flowtig uses GraphQL because different applications require different data while sharing the same platform.

GraphQL allows every client to request exactly the data it needs without unnecessary network requests or endpoint duplication.

Typical advantages include:

  • Strong typing
  • Precise field selection
  • Predictable schemas
  • Self-documenting APIs
  • Efficient data fetching

What can I build?

Every Flowtig application communicates through GraphQL.

Examples include:

Applications own their business domain while sharing the same authentication and permission model.


Tenant Isolation

Every GraphQL request is executed within the context of a single organisation.

The platform automatically enforces:

  • Tenant isolation
  • Membership validation
  • Service permissions
  • Object-level authorization

Applications never need to manually switch databases or filter data by organisation.

Built into the platform

Multi-tenancy is part of the platform architecture rather than an application concern.

Learn more in the Architecture guide.


Queries & Mutations

GraphQL exposes two primary operation types.

Queries

Use queries whenever you want to retrieve information.

Typical examples include:

  • Fetch contacts
  • Retrieve invoices
  • Load projects
  • Search warehouse items

Mutations

Use mutations whenever data should be created, updated or removed.

Typical examples include:

  • Create an invoice
  • Update a contact
  • Delete a warehouse item
  • Complete a task

Schema Design

Every Flowtig application owns its own GraphQL schema.

This keeps business domains clearly separated while allowing applications to evolve independently.

The platform encourages:

  • Clear schema ownership
  • Consistent naming
  • Strong typing
  • Stable contracts

Interactive Documentation

The complete GraphQL schema is available through the interactive GraphQL explorer.

There you can:

  • Browse all types
  • Discover available queries
  • Explore mutations
  • Inspect relationships
  • Execute test queries

👉 https://api.flowtig.com/graphql/docs


You may also be interested in:


Need help?

Questions about the GraphQL API?

Visit the interactive API documentation or contact us through:

👉 https://flowtig.com/contact