What is OAuth?

API & Technical4 min readUpdated Mar 25, 2026

An open authorization framework that enables secure, delegated access to API resources without exposing user credentials to third-party applications.

OAuth (Open Authorization) is an industry-standard authorization framework that enables third-party applications to obtain limited access to an API service on behalf of a user, without the user sharing their credentials with the third-party application. OAuth 2.0, the current version, defines several authorization flows (called "grant types") designed for different application architectures, including web applications, mobile apps, server-to-server communication, and single-page applications.

The OAuth 2.0 framework involves four roles: the resource owner (typically the end user), the client (the third-party application requesting access), the authorization server (which authenticates the user and issues tokens), and the resource server (the API that hosts the protected data). The core principle is that the user authenticates directly with the authorization server, which then issues an access token to the client. The client uses this token to access the resource server, never handling the user's actual credentials.

The most commonly used grant types include the Authorization Code flow for server-side web applications, the Authorization Code with PKCE (Proof Key for Code Exchange) flow for mobile and single-page applications, the Client Credentials flow for server-to-server communication where no user context is needed, and the Refresh Token flow for obtaining new access tokens without re-authentication.

Access tokens are typically short-lived (minutes to hours) to limit the window of exposure if a token is compromised. Refresh tokens have a longer lifetime and can be used to obtain new access tokens without requiring the user to re-authenticate. Scopes define the specific permissions granted to a token, allowing fine-grained control over what the client can access.

Why It Matters

OAuth solves a fundamental security problem in API integrations: how to grant third-party access to a service without sharing the user's password. Before OAuth, integrations often required users to provide their credentials directly to third-party applications, creating significant security risks. If the third-party application was compromised, the user's credentials were exposed. There was no way to limit the scope of access or revoke access without changing the password.

OAuth eliminates these risks by separating authentication from authorization. The user's credentials are handled only by the authorization server, never by the third-party application. Access is controlled through tokens with defined scopes and lifetimes, and access can be revoked by invalidating the token without affecting the user's password. This model provides both security and flexibility.

In the trademark data context, OAuth is particularly important for applications that access trademark data on behalf of individual users. A trademark management platform that acts for individual users needs to reach each user's monitored marks and alerts. OAuth ensures that each user's data is accessed only with their explicit authorization and only within the scope they have granted.

OAuth also enables platform ecosystems. When a trademark data provider supports OAuth, it allows a marketplace of third-party applications to build on top of the platform. Legal tech tools, analytics dashboards, portfolio management systems, and brand protection services can all access the platform's data with user consent, creating a richer ecosystem of tools and services.

How Signa Helps

Signa uses OAuth in one place: its MCP server at https://api.signa.so/mcp, which connects AI assistants and agents to Signa trademark data. Clients such as Cursor or ChatGPT discover the OAuth flow automatically. The user signs in at app.signa.so and approves access, and the client refreshes its token silently, so there is no key to paste or rotate. What a session can do depends on its scopes.

The REST API does not use OAuth. Every REST request authenticates with a Signa API key (sig_ followed by 48 hex characters) sent as a Bearer token in the Authorization header. Each key carries one or more scopes, such as trademarks:read for search and retrieval or portfolios:manage for watches and portfolios. Keys are for server-side use only and can be rotated with a 24-hour grace period. Signa does not offer OAuth client registration, a client credentials flow or third-party delegated access to the REST API. For scripts, CI or headless setups, the MCP server also accepts an API key as a Bearer token.

Example

An in-house IP team wants to ask questions about its trademark data from an AI assistant. A team member adds Signa's MCP server to the assistant, chooses OAuth, and signs in to their Signa account in the browser window that opens. The assistant can now call Signa's tools, such as trademark search, within the scopes that session was granted, and its token refreshes without further sign-ins.

The same team's nightly docketing sync runs on a server and talks to the REST API directly. It uses a Signa API key stored in the team's secrets manager, scoped to trademarks:read, and the team rotates that key on a schedule using the rotation grace period so the sync never stops.