canonical: https://jentic.com/apis/zeliq.com/zeliq

# Zeliq API

Zeliq is a sales intelligence and data enrichment API providing email and phone number waterfall enrichment and credit balance management. The API exposes 3 endpoints secured with apiKey authentication.

## For AI agents

Programmatically get credit balance, enrich contact with phone number. Covers 3 operations with apiKey authentication.

## Scope

Does not handle payments, crm, or developer tools - use for communications only.

## Capabilities

- Get credit balance
- Enrich contact with phone number
- Integrate Zeliq API into automated workflows
- Query and filter Zeliq API records by parameters
- Monitor Zeliq API operational status and events

## Use cases

### Communications Operations

Use the Zeliq API to perform communications operations programmatically. The API provides 3 endpoints covering core functionality including get credit balance, enrich contact with phone number, enrich contact with email.

Example prompt: Call GET `/credits/balance` to get credit balance

### Automated Credits Management

Automate credits operations by combining multiple Zeliq API endpoints. Agents can enrich contact with phone number and then enrich contact with email in a single workflow.

Example prompt: Call POST `/contact/enrich/phone` to enrich contact with phone number, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Zeliq API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'get credit balance', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/credits/balance` | Get credit balance |
| POST | `/contact/enrich/phone` | Enrich contact with phone number |
| POST | `/contact/enrich/email` | Enrich contact with email |

## Key resources

- **Credits** — Operations related to Credits
- **Enrichment** — Operations related to Enrichment

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 66 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 46 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/zeliq.com/zeliq/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring Zeliq by hand means setting its x-api-key header on every request, tracking credit balance against api.zeliq.com/api, and coding the enrichment request handling yourself. Through Jentic you install once, import Zeliq from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Zeliq carries the contact to enrich in the request body rather than the URL path, so limit the agent to the operations it needs, such as checking the credit balance or enriching a contact by email. You leave out phone enrichment unless the agent is meant to spend credits on it.
- **Credential handling:** Your Zeliq key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'enrich a contact by email' or 'get credit balance', and Jentic returns the matching Zeliq operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Twilio** — Alternative communications API
- **Sendgrid** — Alternative communications API
- **Pusher** — Complementary communications API

## FAQ

### What authentication does the Zeliq API use?

The Zeliq API uses an API key passed in the `x-api-key` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I get credit balance with the Zeliq API?

Yes. Use the GET `/credits/balance` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Zeliq API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I get credit balance through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get credit balance'. Jentic returns the matching Zeliq API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Zeliq API have?

The Zeliq API exposes 3 endpoints covering credits, enrichment operations.

### Can I limit what my agent is allowed to do with the Zeliq API?

Yes. Because you self-host Jentic One, your own rules decide which Zeliq operations and credentials the agent may use, so you can allow only the calls it needs, such as checking the credit balance with GET `/credits/balance` or enriching a contact by email with POST `/contact/enrich/email.` You can leave out phone enrichment via POST `/contact/enrich/phone` unless the agent is meant to spend credits on it. Your Zeliq API key stays with your instance and is injected only for the operations you permit.