Ready to eliminate API key management overhead?
Auth API helped Percipient Portal focus on their core product while delivering the integrations customers needed. Experience the same streamlined approach for your multi-organization SaaS platform.
Percipient Portal, a project management SaaS platform, eliminated complex API key management overhead with Auth API, enabling seamless integrations across multiple organizations while maintaining enterprise-grade security.
Auth API’s custom metadata provides immediate access to organization and user context for every API request.
Zapier and custom integrations went from concept to production in days instead of weeks.
No more time spent building or maintaining custom authentication infrastructure.
Percipient Portal serves multiple organizations with their Laravel-based project management platform. As customer demand for integrations grew—Zapier workflows, custom applications, webhook endpoints—their existing approach to API authentication couldn’t scale.
Managing API keys across multiple organizations became increasingly complex, with no clear way to maintain organizational context, user attribution, or integration types. The development team was spending more time on authentication infrastructure than core product features.
The company faced significant challenges with API key management that was limiting their ability to deliver the integrations customers needed while maintaining security and support quality.
Auth API’s custom metadata feature embedded organization ID, user ID, and integration type directly into each API key, eliminating the need for complex lookup tables or database joins.
With authentication infrastructure in place, the team could promise Zapier integration to prospects and deliver custom API access in days rather than planning multi-month development cycles.
The entire API key lifecycle—creation, authentication, expiration, revocation—became a simple API call. No custom infrastructure to build, maintain, or scale.
Enterprise customers gained confidence seeing proper API key management, turning integration capabilities from a concern into a competitive advantage.
Instead of building organizational API key management from scratch, Percipient Portal integrated Auth API. The key insight was Auth API’s custom metadata feature—they could embed all the organizational context directly into each API key.
Here’s how it works in their Laravel application:
//Creating keys with organizational context:
$apiKey = Http::post('https://api.theauthapi.com/api-keys', [
'name' => 'Zapier Integration - ' . $organization->name,
'customMetadata' => [
'customAccountId' => $organization->id,
'customUserId' => $user->id,
'integrationType' => 'zapier'
]
]);
//Verifying requests and extracting context:
$response = Http::get("https://api.theauthapi.com/api-keys/auth/{$apiKey}");
$keyData = $response->json();
// Instantly know which org and user this request is for
$orgId = $keyData['customMetadata']['customAccountId'];
$userId = $keyData['customMetadata']['customUserId'];
$integrationType = $keyData['customMetadata']['integrationType'];
This approach solved their core problem: every API request now carries its organizational context. No separate lookup tables, no complex joins, no guessing about which customer is affected when something goes wrong.
Auth API helped Percipient Portal focus on their core product while delivering the integrations customers needed. Experience the same streamlined approach for your multi-organization SaaS platform.