Troubleshooting
Check authentication, token scope, payload fields, CSV formatting, usage limits, and failed or partial jobs before retrying a workflow.
Customer documentation
Elvesora Docs
Learn how to get an API key, run a first request, understand responses, plan credits, handle errors, and connect Elvesora products to customer data workflows.
Evaluation path
Start with a small request, then scale the workflow.
- 1 Get an API key from the self-serve signup flow and keep it in a server-side secret store.
- 2 Run a first request with a small known sample before wiring bulk uploads or automated jobs.
- 3 Save the product fields your workflow needs, including reason codes, confidence, result type, usage, and export status.
- 4 Review failed or partial jobs separately from low-quality input results so billing, retry, and data-quality decisions stay clear.
Product docs
Each product guide includes an API quickstart, fields reference, workflows, troubleshooting, billing behavior, security notes, and product boundaries.
Company Domain Lookup
Resolve company names to likely official website domains, inspect confidence, and handle not-found or low-confidence matches.
Elvesora Enrichment
Add company-level fields through REST or authenticated remote MCP, understand result types, and plan exports for CRM workflows.
Soryxa
Validate email and domain quality with policy keys, allow, block, or review decisions, reason codes, rules, batch jobs, and webhooks.
Core concepts
These terms appear across the documentation and API responses. Use them consistently when designing imports, retries, exports, and product workflows.
| Concept | Meaning |
|---|---|
| Products | Company Domain Lookup resolves names to domains, Elvesora Enrichment adds company fields, and Soryxa validates email and domain quality. |
| Inputs | Each API expects the smallest useful input: a company name for lookup, a domain for enrichment, and an email address for Soryxa. |
| Outputs | Responses include a success flag, product data, usage or credit fields where available, and explicit error shapes for failed requests. |
| Credits | Credits are counted when a request reaches a billable product workflow. Usage and limit fields help clients avoid surprise stops. |
| Teams and tokens | API tokens belong to a team account. Keep tokens server-side and rotate them when access should change. |
| Usage periods | Plan allowances are measured by the active billing period or recurring monthly Free-plan period for the product subscription. |
Security and privacy
Keep tokens out of browser code, separate team workspaces, and export only the fields needed by the customer system receiving the data.
Changelog and versioning
Review docs pages after customer-visible changes to endpoints, response fields, reason codes, billing behavior, or workflow exports.
Build your first Elvesora API workflow.
Create an API key, choose the product guide for your use case, and start with a small request before scaling to imports or automated jobs.