Skip to main content
An organization is your ezyshield account boundary. API keys, verifications, checks, webhook subscriptions, webhook events, and ABA checks all belong to one organization. The API key in the Authorization header identifies both the key and its organization. You cannot use that key to access another organization’s resources.

​
What belongs to an organization

API keys

Keys authenticate requests and define which abilities the caller has.

Verifications

Point-in-time records created when ezyshield verifies details for a payee.

Checks

Later comparisons against successful verification fingerprints.

Webhooks

Subscriptions and delivery events for verification updates.

​
Dashboard and API

Use the Dashboard for account setup, team access, and interactive API-key management. Use the API for integrations and automated workflows. Both operate on the same organization.

​
First API test

After creating an API key, call Get the current organization. A successful response confirms the key is valid and attached to the organization you expect. This is the first API call in Create your first verification because it tests authentication without creating a verification or starting a contact flow.