> ## Documentation Index
> Fetch the complete documentation index at: https://deepline.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Datagma API Guide for GTM Workflows

> Use Datagma for real-time enrichment, phone discovery, and job-change checks. Prefer LinkedIn URL or domain-backed inputs when available.

## Playbook

# Datagma Workflow Guidance

Datagma is strongest when you need real-time enrichment rather than a static
contact database. It is especially useful for direct mobile numbers, international
coverage, and job-change validation.

## When to use Datagma

* Use `datagma_full_enrichment` when you have a strong identifier such as a
  LinkedIn URL, a professional email, or a domain-backed full name.
* `datagma_enrich_person` remains a compatibility alias for the flat legacy
  response. `datagma_enrich_company` returns the native Datagma response body;
  use its canonical Deepline getters for company name and domain.
* Use `datagma_find_email` when you only need a verified work email and want a
  narrower, cheaper workflow than full enrichment.
* Do not use Datagma for personal-email-only waterfall steps. Public docs expose
  verified work email and full enrichment, not a personal-email-only endpoint.
* Use `datagma_search_phone_numbers` when you already have an email or social URL
  and want direct mobile numbers.
* Use `datagma_job_change_detection` before outreach refreshes when you need to
  confirm whether a contact is still at the same company.
* Use `datagma_find_people` to source up to 10 people by title inside a target company.

## Input strategy

1. LinkedIn URL or company domain
2. Professional email
3. Full name plus company context
4. Company-name-only lookups only when nothing stronger is available

Datagma’s own docs emphasize that LinkedIn URL and domain-backed inputs are the
most reliable. Prefer those over plain company-name searches.

## Billing behavior to remember

* Public pricing currently states `1 credit = 1 verified email`.
* Public pricing currently states `30 credits = 1 mobile phone number`.
* `datagma_find_people` is explicitly documented as 10 credits on success and
  1 credit on a no-result response.
* `datagma_full_enrichment`, `datagma_job_change_detection`, and
  `datagma_search_phone_numbers` expose `creditBurn` in the response. Deepline
  uses that vendor-reported value rather than guessing.
* Datagma does not document a per-call charge response header for these flows.
  Where `creditBurn` is absent, Deepline falls back to endpoint-specific,
  documented success fields rather than treating every non-empty profile as a
  personal-email hit.
* Catch-all email results are free on the public pricing page.

## Endpoint guidance

### `datagma_find_email`

Use for:

* verified work-email lookup from name + company context

Best inputs:

* `firstName` + `lastName` + `companyDomain`
* or `fullName` + `companyDomain`
* optionally `linkedInSlug` when you have the company LinkedIn slug

Canonical Deepline snake\_case column names map straight through, so CSV columns
named `first_name` / `last_name` / `full_name` / `company_name` /
`company_domain` / `domain` are accepted as input aliases for their camelCase
equivalents (the bare `domain` column is treated as the company web domain).

### `datagma_full_enrichment`

Use for:

* person or company enrichment
* firmographics plus person details in one pass
* real-time phone/email/company expansion

Best inputs:

* `data` set to a LinkedIn URL or professional email
* `fullName` or `firstName` + `lastName` only when paired with `data`

Important:

* `phoneFull=true` should be reserved for cases where you do not already have
  a social profile or email, matching Datagma’s docs guidance.

### `datagma_job_change_detection`

Use for:

* validating whether a contact is still at the same company

Best inputs:

* `fullName` + `companyName`
* add `jobTitle` when the contact name may be ambiguous

### `datagma_find_people`

Use for:

* prospecting inside one company by role title

Best inputs:

* `currentJobTitle`
* plus one of `linkedinId`, `domain`, or `currentCompanies`
* add `countries` when known to improve relevance

The action retains the documented contract while Deepline translates it to
Datagma's current employee-finding endpoint.

### `datagma_search_phone_numbers`

Use for:

* direct mobile-number search from an email or profile URL

Best inputs:

* both `email` and `username` when you have them
* Datagma explicitly recommends passing both together when possible

## Internal-only endpoints

Datagma also exposes reverse-email, reverse-phone, and Twitter lookup endpoints.
They remain internal in this repo because the current public docs do not disclose
standalone pricing for them. Do not move them to the public tool surface until
pricing is verified against live credentials or direct vendor confirmation.