canonical: https://jentic.com/apis/supabase.co/supabase

# Supabase Dalil OAuth Resource API

API for OAuth clients to manage Dalil resources. The API exposes 45 endpoints secured with bearer authentication.

## For AI agents

Programmatically create a new lead, search leads. Covers 45 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for identity and authentication only.

## Capabilities

- Create a new lead
- Search leads
- Update a lead's phone book information
- Get all leads with phone book data
- Monitor Dalil OAuth Resource API operational status and events

## Use cases

### Identity and Authentication Operations

Use the Dalil OAuth Resource API to perform identity auth operations programmatically. The API provides 45 endpoints covering core functionality including create a new lead, search leads, search leads by and criteria.

Example prompt: Call POST /leads to create a new lead

### Automated Accounts Management

Automate accounts operations by combining multiple Dalil OAuth Resource API endpoints. Agents can search leads and then search leads by and criteria in a single workflow.

Example prompt: Call GET `/leads/search` to search leads, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Dalil OAuth Resource 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 a new lead', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/leads` | Create a new lead |
| GET | `/leads/search` | Search leads |
| GET | `/leads/search_by_and` | Search leads by AND criteria |
| PUT | `/leads/update` | Update a lead's phone book information |
| GET | `/leads/polling_trigger` | Get all leads with phone book data |
| POST | `/contacts` | Create a new contact |
| GET | `/contacts/search` | Search contacts |
| GET | `/contacts/search_by_and` | Search contacts by AND criteria |

## Key resources

- **Accounts** — Operations for accounts
- **Calendar Event Webhook** — Operations for calendar event webhook
- **Calendar Initial Sync** — Operations for calendar initial sync
- **Cleanup Integration App Customer** — Operations for cleanup integration app customer
- **Contacts** — Operations for contacts

## Why Jentic

- **Setup:** Wiring the Dalil OAuth Resource API by hand means handling its JWT bearer auth against the Supabase Edge Functions host and managing token refresh and retries yourself. Through Jentic you install once, import the Dalil OAuth Resource API from the API Directory, store the bearer token once, and your agent calls it.
- **Permission scoping:** The lead and contact operations take their targets in the request body rather than as URL path ids, so scope the agent to the operations it needs, such as searching leads or reading contacts. Write operations like creating a lead or updating a contact are only in reach if you include them in the allowed set.
- **Credential handling:** Your Dalil OAuth Resource 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 lead' or 'search contacts', and Jentic returns the matching Dalil OAuth Resource API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Auth0** — Alternative identity auth API
- **Okta** — Alternative identity auth API

## FAQ

### What authentication does the Dalil OAuth Resource API use?

The Dalil OAuth Resource 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 a new lead with the Dalil OAuth Resource API?

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

### What are the rate limits for the Dalil OAuth Resource 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 a new lead through Jentic?

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

### How many endpoints does the Dalil OAuth Resource API have?

The Dalil OAuth Resource API exposes 45 endpoints covering accounts, calendar event webhook, calendar initial sync operations.

### Can I limit what my agent is allowed to do with the Dalil OAuth Resource API?

Yes. Because you run Jentic One yourself, your own rules decide which Dalil OAuth Resource API operations and credentials the agent may use. You can allow read-only calls such as searching leads (GET `/leads/search`) or searching contacts (GET `/contacts/search`) while withholding write operations like creating a lead (POST /leads) or updating a contact. Since these operations take their targets in the request body rather than the URL, a write endpoint is only reachable when you add it to the agent's allowed set.