canonical: https://jentic.com/apis/satr.jp/satr-jp

# Satr Jp SATORI API

SATORI marketing automation API for customer registration, upsert, and deletion. The API exposes 3 endpoints.

## For AI agents

Programmatically register a new customer, create or update a customer. Covers 3 operations.

## Scope

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

## Capabilities

- Register a new customer
- Create or update a customer
- Delete a customer
- Query and filter SATORI API records by parameters
- Monitor SATORI API operational status and events

## Use cases

### Marketing Operations

Use the SATORI API to perform marketing operations programmatically. The API provides 3 endpoints covering core functionality including register a new customer, create or update a customer, delete a customer.

Example prompt: Call POST `/customer/registration.json` to register a new customer

### Automated Customers Management

Automate customers operations by combining multiple SATORI API endpoints. Agents can create or update a customer and then delete a customer in a single workflow.

Example prompt: Call POST `/customer/upsert.json` to create or update a customer, then verify the result

### AI Agent Integration via Jentic

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

Example prompt: Search Jentic for 'register a new customer', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/customer/registration.json` | Register a new customer |
| POST | `/customer/upsert.json` | Create or update a customer |
| POST | `/customer/delete.json` | Delete a customer |

## Key resources

- **Customers** — Operations related to Customers

## 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:** 71 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 45 / 100
  - Agent Usability: 94 / 100
  - Security: 100 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/satr.jp/satr-jp/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 SATORI API by hand means posting customer records to its public v4 endpoints and handling the registration, upsert, and delete calls yourself. Through Jentic you install once, import the SATORI API from the API Directory, and your agent calls it.
- **Permission scoping:** The SATORI API takes its customer details in the request body rather than the URL path, so you limit the agent to the operations it needs, such as registering or upserting a customer, and you leave out the delete operation unless you add it. Every operation the agent runs is one you chose.
- **Credential handling:** The SATORI API public endpoints take no credential, and Jentic executes the calls without placing any secret in the agent's prompt, logs, or context. Any configuration you do store is held encrypted by your own Jentic One instance and injected at execution time.
- **Discovery method:** Agents search Jentic by intent such as 'register a new customer' or 'upsert a customer record', and Jentic returns the matching SATORI API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mailchimp** — Alternative marketing API
- **Hubspot** — Alternative marketing API

## FAQ

### What authentication does the SATORI API use?

The SATORI API uses no authentication. 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 register a new customer with the SATORI API?

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

### What are the rate limits for the SATORI 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 register a new customer through Jentic?

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

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

The SATORI API exposes 3 endpoints covering customers operations.

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

Yes. Because you run Jentic One yourself, you decide which SATORI API operations the agent can call, so you can allow it to register a customer with POST `/customer/registration.json` and upsert one with POST `/customer/upsert.json` while leaving out the delete operation entirely. The delete call to POST `/customer/delete.json` is only available to the agent if you choose to add it. Every operation the agent runs is one you selected, and since these public endpoints take customer details in the request body, your rules govern exactly which calls it can make.