PropelAuth API

Name: PropelAuth API
Brand: PropelAuth API
Availability: InStock

✓ Official Vendor SpecIdentity AuthAuthenticationbearer19 EndpointsREST

For Agents

Programmatically fetch user by id, update user. Covers 19 operations with bearer authentication.

Install Jentic One Beta

Connect the PropelAuth API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the PropelAuth 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 PropelAuth API.

Fetch user by ID

Update user

Delete user

Create user

GET STARTED

Start building with PropelAuth API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use PropelAuth API for, with concrete tasks.

★ Identity and Authentication Operations

Use the PropelAuth API to perform identity auth operations programmatically. The API provides 19 endpoints covering core functionality including fetch user by id, update user, delete user.

Call GET /api/backend/v1/user/{user_id} to fetch user by id

Automated Users Management

Automate users operations by combining multiple PropelAuth API endpoints. Agents can update user and then delete user in a single workflow.

Call PUT /api/backend/v1/user/{user_id} to update user, then verify the result

AI Agent Integration via Jentic

AI agents discover and call PropelAuth 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 'fetch user by id', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

19 endpoints — propelauth is a b2b authentication service.

METHOD

PATH

DESCRIPTION

GET

/api/backend/v1/user/{user_id}

Fetch user by ID

PUT

/api/backend/v1/user/{user_id}

Update user

DELETE

/api/backend/v1/user/{user_id}

Delete user

GET

/api/backend/v1/user/email

Fetch user by email

GET

/api/backend/v1/user/username

Fetch user by username

POST

/api/backend/v1/user/

Create user

GET

/api/backend/v1/user/query

Query users

POST

/api/backend/v1/user/{user_id}/disable

Disable a user

GET

/api/backend/v1/user/{user_id}

Fetch user by ID

PUT

/api/backend/v1/user/{user_id}

Update user

DELETE

/api/backend/v1/user/{user_id}

Delete user

GET

/api/backend/v1/user/email

Fetch user by email

GET

/api/backend/v1/user/username

Fetch user by username

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

PropelAuth API bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'fetch user by id') and Jentic returns the matching PropelAuth API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct PropelAuth API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using PropelAuth API through Jentic.

What authentication does the PropelAuth API use?

The PropelAuth API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I fetch user by id with the PropelAuth API?

Yes. Use the GET /api/backend/v1/user/{user_id} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the PropelAuth 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 fetch user by id through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'fetch user by id'. Jentic returns the matching PropelAuth API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the PropelAuth API have?

The PropelAuth API exposes 19 endpoints covering users, organizations, magic links operations.

PropelAuth API

Connect the PropelAuth API to your agent

Capabilities

Start building with PropelAuth API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs