canonical: https://jentic.com/apis/ricoh360.com/ricoh360

# RICOH360 Tours API

RICOH360 Tours GraphQL API for managing virtual tours, team API keys, and webhook subscriptions. AWS AppSync-based GraphQL implementation. The API exposes 1 endpoints secured with apiKey authentication.

## For AI agents

Programmatically execute graphql query or mutation. Covers 1 operations with apiKey authentication.

## Scope

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

## Capabilities

- Execute GraphQL query or mutation
- Manage payments data programmatically
- Integrate RICOH360 Tours API into automated workflows
- Query and filter RICOH360 Tours API records by parameters
- Monitor RICOH360 Tours API operational status and events

## Use cases

### Payments Operations

Use the RICOH360 Tours API to perform payments operations programmatically. The API provides 1 endpoints covering core functionality including execute graphql query or mutation.

Example prompt: Call POST /graphql to execute graphql query or mutation

### Data Retrieval and Monitoring

Query RICOH360 Tours 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 RICOH360 Tours API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call RICOH360 Tours 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 'execute graphql query or mutation', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/graphql` | Execute GraphQL query or mutation |

## Key resources

- **GraphQL** — Operations related to GraphQL

## 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: 87 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 43 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/ricoh360.com/ricoh360/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 RICOH360 Tours API by hand means setting its apiKey in the Authorization header, targeting the us-west-2 AppSync GraphQL host, and shaping every request as a GraphQL query or mutation over the single /graphql endpoint. Through Jentic you install once, import the RICOH360 Tours API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** This API exposes one /graphql endpoint where the operation travels in the request body, so scope the agent to the operations it needs rather than a single resource: you decide whether it runs read queries only or is also allowed to send mutations. Every operation the agent can run is one you have added to that allowed set.
- **Credential handling:** Your RICOH360 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 'run a tours GraphQL query' or 'update tour data', and Jentic returns the matching RICOH360 Tours API 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 RICOH360 Tours API use?

The RICOH360 Tours 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 execute graphql query or mutation with the RICOH360 Tours API?

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

### What are the rate limits for the RICOH360 Tours 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 execute graphql query or mutation through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'execute graphql query or mutation'. Jentic returns the matching RICOH360 Tours API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the RICOH360 Tours API have?

The RICOH360 Tours API exposes 1 endpoints covering graphql operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which of the RICOH360 Tours API operations the agent may call and which stored API key it may use. This API exposes a single POST /graphql endpoint where the operation travels in the request body, so you scope the agent to the specific operations it needs: you decide whether it runs read queries only or is also allowed to send mutations. Every operation the agent can run is one you have added to that allowed set.