Profile System - PII data architecture

Name: Profile System - PII data architecture API
Brand: Profile System - PII data architecture
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCRMContact ManagementapiKey31 EndpointsREST

For Agents

Programmatically create client profile, get profile. Covers 31 operations with apiKey authentication.

Connect the Profile System - PII data architecture to your agent

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

Install Jentic One Beta (Self-Hosted)

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

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 Profile System - PII data architecture API.

Create client profile

Get profile

Update client profile

Delete client profile

GET STARTED

Start building with Profile System - PII data architecture API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Profile System - PII data architecture, keeping it validated and agent-ready.

>⚠️ The Profile System is only compatible with stores using the PII data architecture from [Data Protection Plus](https://developers.vtex.com/docs/guides/data-protection-plus), which is in closed beta phase, only available in select regions. > > This feature is part of [VTEX Shield](https://help.vtex.com/en/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh). If you are already a VTEX customer and want . The API exposes 31 endpoints secured with apiKey authentication.

Use Cases

Patterns agents use Profile System - PII data architecture API for, with concrete tasks.

★ CRM Operations

Use the Profile System - PII data architecture to perform crm operations programmatically. The API provides 31 endpoints covering core functionality including create client profile, get profile, update client profile.

Call POST /api/storage/profile-system/profiles to create client profile

Automated Profiles Management

Automate profiles operations by combining multiple Profile System - PII data architecture endpoints. Agents can get profile and then update client profile in a single workflow.

Call GET /api/storage/profile-system/profiles/{profileId} to get profile, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Profile System - PII data architecture 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.

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

Key Endpoints

31 endpoints — >⚠️ the profile system is only compatible with stores using the pii data architecture from [data protection plus](https://developers.

METHOD

PATH

DESCRIPTION

POST

/api/storage/profile-system/profiles

Create client profile

GET

/api/storage/profile-system/profiles/{profileId}

Get profile

PATCH

/api/storage/profile-system/profiles/{profileId}

Update client profile

DELETE

/api/storage/profile-system/profiles/{profileId}

Delete client profile

GET

/api/storage/profile-system/profiles/{profileId}/unmask

Get unmasked profile

GET

/api/storage/profile-system/profiles/{profileId}/versions/{profileVersionId}

Get profile by version

GET

/api/storage/profile-system/profiles/{profileId}/versions/{profileVersionId}/unmask

Get unmasked profile by version

POST

/api/storage/profile-system/profiles/{profileId}/addresses

Create client address

POST

/api/storage/profile-system/profiles

Create client profile

GET

/api/storage/profile-system/profiles/{profileId}

Get profile

PATCH

/api/storage/profile-system/profiles/{profileId}

Update client profile

DELETE

/api/storage/profile-system/profiles/{profileId}

Delete client profile

GET

/api/storage/profile-system/profiles/{profileId}/unmask

Get unmasked profile

Why though Jentic?

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

Credential isolation

Profile System - PII data architecture apiKey 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., 'create client profile') and Jentic returns the matching Profile System - PII data architecture operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Profile System - PII data architecture integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Hubspot

Alternative crm API

Choose Hubspot when you need a different approach to crm operations

Alternative

Salesforce

Alternative crm API

Choose Salesforce when you need a different approach to crm operations

Complementary

Pipedrive

Complementary crm API

Choose Pipedrive when you need a complementary approach to crm operations

Complementary

Zoho

Complementary crm API

Choose Zoho when you need a complementary approach to crm operations

FAQs

Specific to using Profile System - PII data architecture API through Jentic.

What authentication does the Profile System - PII data architecture use?

The Profile System - PII data architecture uses an API key passed in the `X-VTEX-API-AppKey` 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 create client profile with the Profile System - PII data architecture?

Yes. Use the POST /api/storage/profile-system/profiles endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Profile System - PII data architecture?

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 client profile through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'create client profile'. Jentic returns the matching Profile System - PII data architecture operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the Profile System - PII data architecture have?

The Profile System - PII data architecture exposes 31 endpoints covering profiles, addresses, prospects operations.