Referrizer API

Name: Referrizer API
Brand: Referrizer API
Availability: InStock

✓ Official Vendor SpecCRMContact Managementbearer13 EndpointsREST

For Agents

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

Install Jentic One Beta

Connect the Referrizer API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Referrizer API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Freferrizer.com%2Freferrizer" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Freferrizer.com%2Freferrizer" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Referrizer API.

Create new contact

List all contacts

Get contact

Update contact

GET STARTED

Start building with Referrizer API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Referrizer API for, with concrete tasks.

★ 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.

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.

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.

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

Key Endpoints

13 endpoints — api for managing contacts, custom fields, loyalty points, and text messaging in referrizer.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using Referrizer API through Jentic.

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.

Referrizer API

Connect the Referrizer API to your agent

Capabilities

Start building with Referrizer API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs