Core Concepts

Key concepts for working with the TexAu V3 API — credits, rate limits, webhooks, and async jobs.

Credit System

All API usage is billed in credits.

1 credit = $0.02
Credits are only deducted on successful (2xx) responses — errors are free
Two billing models exist across endpoints:

Model	How it works	Example endpoints
Per-call	Fixed credits per API call	`enrich_profile`, `post_keyword_search`, all web scraping
Per-result	Credits × number of results returned	`people_search`, `enrich_profiles_bulk`, `profile_search`

See the Credits & Pricing page for the full breakdown.

Rate Limits

Each endpoint has a monthly per-customer quota. Quotas reset at the start of each calendar month UTC.

Endpoint group	Monthly quota
LinkedIn enrichment, search, email	100,000 calls
Web scraping (meta, JSON-LD, pixels, sitemap)	100,000 calls
Web scraping (full scrape, social links, tech stack, Bing)	50,000 calls
Web emails, website intelligence, Google Trends	25,000 calls
YouTube, Slack channel members	10,000–25,000 calls

When a quota is exceeded the API returns 429 Too Many Requests. Contact us for higher limits.

Webhooks (Email APIs)

The email finding and email verification endpoints use webhook delivery instead of returning results inline. Email processing is asynchronous.

How it works:

Submit your request

Send a list of people/emails with a webhook URL in the request body.

Get a job ID

The API immediately returns a job id and initial state.

Receive webhook

When processing completes, results are POSTed to your webhook URL.

Poll as fallback

Use the inquiry endpoint (/email_finding_inquiry/{id}) to poll for results without needing a webhook receiver.

Webhook URLs must use HTTPS. HTTP webhook URLs are rejected to protect data in transit.

Caching

Most web scraping endpoints accept an optional cache parameter (default: true). When enabled:

Cached results are returned immediately for recently fetched URLs
Reduces latency and credit spend for frequently accessed pages
Set cache_bust: true to force a fresh fetch

Async Jobs

Email endpoints return a job object:

Field	Type	Description
`id`	string	UUID job identifier
`state`	string	`PROCESSING`, `DONE`, or `FAILED`

Poll the inquiry endpoint with the job id until state === "DONE".

Pagination

Search endpoints use zero-based pages:

{ "page": 0, "size": 25 }   // First 25 results
{ "page": 1, "size": 25 }   // Next 25 results

profile_search uses 1-based pagination via a page query parameter.

Base URL

All endpoints are under:

https://v3-api.texau.com/api/v1/

The building blocks

Pages

Every page is an .mdx file. Content lives in the repo and is safe to edit.

Navigation

Sidebar structure comes from documentation.json.

Components

Reusable blocks like Callouts, Steps, Tabs, and Cards keep pages consistent.

API Reference

If you use it, the API tab reads from openapi.yaml.

{
  "tab": "Documentation",
  "groups": [
    {
      "group": "Getting Started",
      "pages": [
        { "title": "Introduction", "path": "introduction" }
      ]
    }
  ]
}

How to adapt this page

Replace the terms

Swap "Pages" and "Components" for your real domain language.

Add your concepts

Create a section for the ideas your users must learn first.

Was this page helpful?

Last updated 2 weeks ago

Built with Documentation.AI