canonical: https://jentic.com/apis/rasayel.io/rasayel

# Rasayel GraphQL API

Rasayel GraphQL API for messaging and conversation management. Note: This is a GraphQL API with a single endpoint. Operations include message management (text, media, template), conversation management (assign, close, open), contact operations, and webhook subscriptions. The API exposes 1 endpoints.

## For AI agents

Programmatically graphql endpoint. Covers 1 operations.

## Scope

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

## Capabilities

- GraphQL endpoint
- Access Rasayel GraphQL API communications resources via REST API
- Query Rasayel GraphQL API endpoints with structured JSON responses
- Authenticate requests with none credentials managed by Jentic
- Access Rasayel GraphQL API resources programmatically via REST

## Use cases

### Communications Operations

Use the Rasayel GraphQL API to perform communications operations programmatically. The API provides 1 endpoints covering core functionality including graphql endpoint.

Example prompt: Call POST /graphql to graphql endpoint

### Data Retrieval and Monitoring

Query Rasayel GraphQL API endpoints to retrieve structured data for monitoring, reporting, or downstream processing. The API returns JSON responses that agents can parse directly, enabling automated data collection workflows.

Example prompt: Query the Rasayel GraphQL API API to retrieve current data and verify the response structure

### AI Agent Integration via Jentic

AI agents discover and call Rasayel GraphQL 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 'graphql endpoint', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/graphql` | GraphQL endpoint |

## 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:** 74 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 64 / 100
  - AI-Readiness & Agent Experience: 49 / 100
  - Agent Usability: 94 / 100
  - Security: 100 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/rasayel.io/rasayel/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 Rasayel GraphQL API by hand means building your own client around a single GraphQL endpoint where every action is a query or mutation you have to compose, even though the spec declares no auth. Through Jentic you install once, import the Rasayel GraphQL API from the API Directory, and your agent calls it.
- **Permission scoping:** Rasayel exposes one GraphQL endpoint (POST /graphql), so scoping is operations-only: you limit the agent to the GraphQL operations it needs, such as querying conversations or contacts. You choose which operations it may run, so mutations you do not want are not included unless you add them.
- **Credential handling:** The Rasayel GraphQL API declares no credential in this spec, so there is no secret to store. Any configuration your Jentic One instance holds stays out of the agent's prompt, logs, and context.
- **Discovery method:** Agents search Jentic by intent such as 'query WhatsApp conversations' or 'look up a contact', and Jentic returns the matching Rasayel operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Twilio** — Alternative communications API
- **Sendgrid** — Alternative communications API
- **Pusher** — Complementary communications API

## FAQ

### What authentication does the Rasayel GraphQL API use?

The Rasayel GraphQL 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 graphql endpoint with the Rasayel GraphQL 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 Rasayel GraphQL 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 graphql endpoint through Jentic?

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

### How many endpoints does the Rasayel GraphQL API have?

The Rasayel GraphQL API exposes 1 endpoints covering graphql operations.

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

Yes. Because Rasayel exposes a single GraphQL endpoint (POST /graphql) where every action is a query or mutation, scoping is operations-only: in your self-hosted Jentic One instance, your own rules decide which GraphQL operations the agent may run. You can allow read operations such as querying conversations or looking up contacts while excluding mutations like assigning, closing, or opening conversations unless you explicitly add them. Since the operator controls the allowed operation set, the agent can only call what you have permitted.