Authentication Overview

Authentication is how eCourtDate verifies who is making a request. Before any system or user can access eCourtDate data, they must prove their identity — this prevents unauthorized access to your agency's information.

eCourtDate supports two authentication methods depending on your integration scenario: API Keys for server-to-server communication and OAuth / SSO for user-facing applications. This page provides a high-level comparison so you can choose the right approach for your use case.

Which method should I choose?

• Connecting a backend system, script, or scheduled job? Use API Keys — they're designed for automated, server-to-server communication with no user interaction.
• Want users to log in with their existing work accounts (Microsoft, Google, Okta)? Use OAuth / SSO — it lets individual users authenticate through your organization's identity provider.

Method 1 -- API Keys (Client Credentials)

API keys use the OAuth 2.0 client_credentials grant to obtain a bearer token. This method is designed for backend services, cron jobs, data pipelines, and any integration where a server communicates directly with the eCourtDate API without end-user interaction.

How it works:

1. Create an API key in the eCourtDate Console under APIs (console.ecourtdate.com/apis).
2. Exchange your client_id and client_secret for an access token by sending a POST request to /oauth/token with grant_type set to client_credentials.
3. Include the access token in the Authorization: Bearer <token> header on every API request.
4. Tokens expire after a set duration. Your integration should request a new token before or when the current one expires.

Best for: automated integrations, backend services, scheduled data syncs, server-to-server communication.

For full details and code examples, see the API Authentication guide.

Method 2 -- OAuth / SSO (Authorization Code)

OAuth / SSO uses the OAuth 2.0 Authorization Code flow to authenticate individual users through an identity provider. This method is designed for web applications, portals, and dashboards where users sign in with their organizational credentials.

Supported identity providers:

• Microsoft Azure AD (Entra ID)
• Google Workspace
• Okta
• AWS Cognito
• Any custom OIDC-compliant provider

How it works:

1. Configure your identity provider in the eCourtDate Console under the OAuth / SSO settings.
2. Your application redirects the user to the identity provider's login page.
3. After the user authenticates, the identity provider redirects back to your application with an authorization code.
4. Your application exchanges the authorization code for access and refresh tokens.
5. Use the access token to make API requests on behalf of the authenticated user.

Best for: user-facing web applications, internal dashboards, portals requiring individual user authentication.

For configuration instructions and provider-specific setup guides, see the OAuth / SSO documentation.

Comparison

	API Keys (Client Credentials)	OAuth / SSO (Authorization Code)
Flow	client_credentials grant	Authorization Code grant
User interaction	None -- fully automated	User signs in via identity provider
Managed in	Console > APIs	Console > OAuth / SSO settings
Credential type	Client ID + Client Secret	Redirect URI + Provider configuration
Use case	Server-to-server, batch jobs, data pipelines	Web apps, portals, user-facing dashboards
Token represents	The API key / application	An individual user session

Next Steps

• Quickstart -- See API key authentication in action with a step-by-step example.
• API Authentication -- Detailed guide for API key setup, token management, and error handling.
• OAuth / SSO -- Full configuration guide for single sign-on with supported identity providers.