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

# Referrizer API

API for managing contacts, custom fields, loyalty points, and text messaging in Referrizer. The API exposes 13 endpoints secured with bearer authentication.

## For AI agents

Programmatically create new contact, list all contacts. Covers 13 operations with bearer authentication.

## Scope

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

## Capabilities

- Create new contact
- List all contacts
- Get contact
- Update contact
- Delete contact

## Use cases

### CRM Operations

Use the Referrizer API to perform crm operations programmatically. The API provides 13 endpoints covering core functionality including create new contact, list all contacts, get contact.

Example prompt: Call POST `/v1/contacts` to create new contact

### Automated Contacts Management

Automate contacts operations by combining multiple Referrizer API endpoints. Agents can list all contacts and then get contact in a single workflow.

Example prompt: Call GET `/v1/contacts` to list all contacts, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Referrizer 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 bearer tokens manually.

Example prompt: Search Jentic for 'create new contact', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/v1/contacts` | Create new contact |
| GET | `/v1/contacts` | List all contacts |
| GET | `/v1/contacts/{id}` | Get contact |
| PUT | `/v1/contacts/{id}` | Update contact |
| DELETE | `/v1/contacts/{id}` | Delete contact |
| GET | `/v1/contacts/{id}/activities` | Get contact activities |
| PUT | `/v1/contacts/{id}/loyalty-points` | Update loyalty points |
| POST | `/v1/custom-fields` | Create custom field |

## Key resources

- **Contacts** — Operations related to Contacts
- **Custom Fields** — Operations related to Custom Fields
- **Loyalty** — Operations related to Loyalty
- **Text Messaging** — Operations related to Text Messaging

## 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:** 67 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 93 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 47 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/referrizer.com/referrizer/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 the Referrizer API by hand means setting its bearer token on every request and building your own retry handling against the api.referrizer.com host. Through Jentic you install once, import the Referrizer API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** The Referrizer API puts the contact id in the URL path (`/v1/contacts/{id}`), so a rule can pin your agent to one contact: it can read that contact's activities and update its loyalty points and nothing else. You choose the operations it may call, so destructive ones like deleting a contact are not included unless you add them.
- **Credential handling:** Your Referrizer API bearer token 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 'create a new contact' or 'add loyalty points', and Jentic returns the matching Referrizer API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Hubspot** — Alternative crm API
- **Salesforce** — Alternative crm API
- **Pipedrive** — Complementary crm API
- **Zoho** — Complementary crm API

## FAQ

### What authentication does the Referrizer API use?

The Referrizer API uses a Bearer token in the Authorization 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 create new contact with the Referrizer API?

Yes. Use the POST `/v1/contacts` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Referrizer 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 create new contact through Jentic?

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

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

The Referrizer API exposes 13 endpoints covering contacts, custom fields, loyalty operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Referrizer API operations and credentials the agent may use. Since the contact id sits in the URL path (`/v1/contacts/{id}`), you can pin the agent to a single contact so it only reads that contact's activities and updates its loyalty points, for example. You choose the exact operations it may call, so destructive ones such as deleting a contact are excluded unless you explicitly grant them.