canonical: https://jentic.com/apis/sipay.com.tr/sipay-com-tr

# SiPay Wallet API

STS API for SiPay wallet payment transactions. The API exposes 1 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create payment. Covers 1 operations with apiKey authentication.

## Scope

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

## Capabilities

- Create payment
- Manage payments data programmatically
- Integrate SiPay Wallet API into automated workflows
- Query and filter SiPay Wallet API records by parameters
- Monitor SiPay Wallet API operational status and events

## Use cases

### Payments Operations

Use the SiPay Wallet API to perform payments operations programmatically. The API provides 1 endpoints covering core functionality including create payment.

Example prompt: Call POST `/v1/Transaction/Payment` to create payment

### Data Retrieval and Monitoring

Query SiPay Wallet API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary SiPay Wallet API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call SiPay Wallet 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 apiKey tokens manually.

Example prompt: Search Jentic for 'create payment', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/v1/Transaction/Payment` | Create payment |

## Key resources

- **Transactions** — Operations related to Transactions

## 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:** 63 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 94 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 42 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/sipay.com.tr/sipay-com-tr/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 SiPay Wallet API by hand means setting up its key in the Authorization header and threading it through the payment call on the walletapi host yourself. Through Jentic you install once, import SiPay Wallet from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** The SiPay Wallet API carries the payment details in the request body rather than as a resource id in the URL path, so scope the agent by operations: limit it to the operations it needs, such as submitting a payment, and leave any other operations out unless you add them.
- **Credential handling:** Your SiPay Wallet API key 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 'take a wallet payment', and Jentic returns the matching SiPay Wallet operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Stripe** — Alternative payments API
- **Adyen** — Alternative payments API
- **Square** — Complementary payments API
- **Paypal** — Complementary payments API

## FAQ

### What authentication does the SiPay Wallet API use?

The SiPay Wallet API uses an API key passed 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 payment with the SiPay Wallet API?

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

### What are the rate limits for the SiPay Wallet 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 payment through Jentic?

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

### How many endpoints does the SiPay Wallet API have?

The SiPay Wallet API exposes 1 endpoints covering transactions operations.

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

Yes. Because Jentic One is self-hosted by you, your own rules decide which SiPay Wallet API operations and credentials the agent may use. Since the SiPay Wallet API carries payment details in the request body rather than as a resource id in the URL path, you scope the agent by operations: grant only the calls it needs, such as submitting a payment through POST `/v1/Transaction/Payment`, and leave every other operation out unless you add it. Your stored API key is injected only for the operations you have allowed, so the agent can act on nothing you have not explicitly permitted.