What is API Authentication?
The process of verifying the identity of a client making API requests, ensuring only authorized users can access trademark data and services.
API authentication is the process of verifying the identity of a client making requests to an API, ensuring that only authorized users and applications can access the service's data and functionality. Authentication is the first line of defense in API security, determining who is making a request before deciding what they are allowed to do. It is distinct from authorization, which determines what an authenticated client is permitted to access.
Common API authentication methods include API keys, OAuth 2.0 tokens, JWT (JSON Web Tokens), and basic authentication. Each method offers different trade-offs between security, complexity, and usability. API keys provide simple authentication by including a unique identifier in each request. OAuth 2.0 provides delegated authentication through an access token obtained via a separate authorization flow. JWT tokens are self-contained tokens that encode identity and permission claims. Basic authentication sends credentials (username and password) with each request, typically Base64-encoded.
Modern API authentication typically involves multiple layers. Transport layer security (TLS/HTTPS) encrypts the communication channel to prevent credential interception. Application-level authentication verifies the identity of the client through one of the methods described above. Additional security measures may include IP whitelisting, request signing, and mutual TLS for high-security environments.
The authentication method chosen depends on the use case. Server-to-server integrations often use API keys or OAuth client credentials. User-facing applications that access the API on behalf of individual users typically use OAuth authorization code flow. Mobile applications may use OAuth with PKCE (Proof Key for Code Exchange). Each pattern addresses different security requirements and trust models.
Why It Matters
Authentication is foundational to the security and viability of any API service. Without authentication, trademark data would be accessible to anyone, including competitors, bad actors, and automated scrapers. Usage tracking, rate limiting, and billing all depend on the ability to identify which client is making each request. And data privacy regulations in many jurisdictions require that access to personal data, including trademark owner information, be controlled and auditable.
For API consumers, understanding authentication is essential for successful integration. Incorrectly implemented authentication is one of the most common causes of integration failures. Expired tokens, misconfigured headers, and improperly stored credentials can all result in request failures that disrupt the client application. Conversely, poorly secured credentials can lead to unauthorized access, data breaches, and financial liability.
In the trademark data context, authentication serves additional important functions. Trademark data includes personally identifiable information such as owner names and addresses. It includes commercially sensitive information such as pending applications that have not yet been published. And it includes proprietary analysis results such as clearance scores and conflict assessments. All of this data must be protected by robust authentication to prevent unauthorized access.
Authentication also enables personalization and multi-tenancy. Different authenticated clients may have different subscription tiers, different rate limits, different access to premium features, and different data retention policies. The authentication identity is the key that links each request to the appropriate configuration.
How Signa Helps
Signa's REST API authenticates every request with an API key sent as a Bearer token: Authorization: Bearer sig_.... Keys use the format sig_ followed by 48 hex characters, and a key with an unrecognized prefix is rejected with 401 before any lookup. Keys are created, rotated and revoked in the Signa dashboard or through the API, and rotation keeps the old key working for 24 hours so services can switch without downtime. Several keys can be active at once, for example one per environment.
Each key carries one or more scopes, such as trademarks:read for search and retrieval or portfolios:manage for watches and portfolios, and a request outside a key's scopes returns 403. A missing, invalid, expired or revoked key returns 401. Keys are for server-to-server use only: never ship one in browser or mobile code; call Signa from your backend instead.
All API traffic uses HTTPS. Credits and rate limits apply per organization, shared by all its keys, and the dashboard's request logs show the requests that reached the API.
The REST API does not offer OAuth flows or single sign-on federation. OAuth is used only by Signa's MCP server, where AI clients sign the user in at app.signa.so.
Example
A trademark analytics company integrates Signa's API into its own platform, which serves individual practitioners, law firms and enterprise IP departments.
Its users never touch a Signa key. The company's backend holds Signa API keys in a secrets manager, one per environment, and proxies every request its web app makes, applying its own user authentication and permissions before calling Signa. The production key is scoped to trademarks:read, and a separate key with portfolios:manage is used only by the service that manages watches.
The team rotates both keys on a schedule. When a key is rotated, the 24-hour grace period lets it roll the new secret out to every service before the old one stops working.