Skip to main content

Organization Attribution for API Metering

  • April 29, 2026
  • 0 replies
  • 12 views

vinicius.pereira
Community Manager

Overview

Starting today, all Personal Access Tokens (PATs) must have a billing organization assigned. This ensures every API call is correctly attributed to the account responsible for the costs with full visibility in the admin dashboard.

 

What's new?

  • New tokens: selecting a billing organization is now a required step at creation
  • Existing tokens: 45-day window for manual configuration; after the deadline, the system assigns an organization automatically
  • API usage is now consolidated per organization in the admin dashboard

 

How does this help?

  • Cost visibility per organization: every API call is attributed to the correct account, with no ambiguity
  • Centralized management for multiple accounts: teams running sub-accounts can consolidate all billing under a single parent organization
  • Simplified auditing: the admin dashboard accurately reflects who consumes what — useful for cost reviews and access governance

 

Use cases

  1. IT team managing system integrations via API: with mandatory attribution, each token is tied to the business unit responsible for the cost, eliminating manual cost splits and inter-department billing disputes.
  2. Company with multiple subsidiaries using Pipefy: the parent organization consolidates API consumption from all subsidiaries in a single dashboard, simplifying monthly close and cost allocation per entity.
  3. Operation using AI Credits via API: by linking the token to the correct organization, AI credit consumption becomes traceable per account, enabling expansion or usage review decisions based on real data.
  4. Offboarding process for employees with PAT access: when reviewing active tokens, admins can quickly identify which ones have no organization assigned and act before the automatic deadline.
  5. Internal platform cost audit: finance or IT can cross-reference API usage by organization directly in the dashboard, without requesting reports from support.

 

Most relevant for

  • Organization admins managing active tokens
  • IT teams responsible for API integrations
  • Companies with multi-account or multi-subsidiary structures
  • Users operating AI Credits via API

 

Documentation

For the full step-by-step, check the Help Center article.