canonical: https://jentic.com/apis/telegra.ph/telegra-ph

# Telegraph API

Telegraph is a publishing tool by Telegram that lets you create richly formatted posts and share them instantly. The API allows creating accounts, publishing and editing pages, and retrieving page statistics. The API exposes 9 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create a new telegraph account, edit account information. Covers 9 operations with apiKey authentication.

## Scope

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

## Capabilities

- Create a new Telegraph account
- Edit account information
- Get account information
- Revoke access token
- Monitor Telegraph API operational status and events

## Use cases

### Social Media Operations

Use the Telegraph API to perform social media operations programmatically. The API provides 9 endpoints covering core functionality including create a new telegraph account, edit account information, get account information.

Example prompt: Call POST /createAccount to create a new telegraph account

### Automated createAccount Management

Automate createaccount operations by combining multiple Telegraph API endpoints. Agents can edit account information and then get account information in a single workflow.

Example prompt: Call POST /editAccountInfo to edit account information, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Telegraph 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 a new telegraph account', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/createAccount` | Create a new Telegraph account |
| POST | `/editAccountInfo` | Edit account information |
| POST | `/getAccountInfo` | Get account information |
| POST | `/revokeAccessToken` | Revoke access token |
| POST | `/createPage` | Create a new Telegraph page |
| POST | `/editPage/{path}` | Edit a Telegraph page |
| GET | `/getPage/{path}` | Get a Telegraph page |
| POST | `/getPageList` | Get a list of pages belonging to a Telegraph account |

## Key resources

- **createAccount** — Operations related to createAccount
- **createPage** — Operations related to createPage
- **editAccountInfo** — Operations related to editAccountInfo
- **editPage** — Operations related to editPage
- **getAccountInfo** — Operations related to getAccountInfo

## 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:** 48 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 93 / 100
  - Developer Experience & Jentic Compatibility: 56 / 100
  - AI-Readiness & Agent Experience: 52 / 100
  - Agent Usability: 94 / 100
  - Security: 15 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/telegra.ph/telegra-ph/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 Telegraph API by hand means managing its per-account access token, passing it on every call against api.telegra.ph, and building the page content and retry handling yourself. Through Jentic you install once, import the Telegraph API from the API Directory, store the access token once, and your agent calls it.
- **Permission scoping:** The Telegraph API puts the page path in the URL (`/getPage/{path}`, `/editPage/{path}`), so a rule can pin your agent to one page: it can read and edit that page and nothing else. You choose the operations it may call, so ones like revoking the access token are not included unless you add them.
- **Credential handling:** Your Telegraph access token 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 'create a page' or 'edit a page', and Jentic returns the matching Telegraph API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Facebook** — Alternative social media API
- **Twitter** — Alternative social media API
- **Linkedin** — Complementary social media API

## FAQ

### What authentication does the Telegraph API use?

The Telegraph API uses an API key passed in the `access_token` query. 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 a new telegraph account with the Telegraph API?

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

### What are the rate limits for the Telegraph 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 a new telegraph account through Jentic?

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

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

The Telegraph API exposes 9 endpoints covering createaccount, createpage, editaccountinfo operations.

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

Yes. Jentic One is self-hosted, so your own rules decide which Telegraph operations and credentials the agent may use. Because the Telegraph API carries the page path in the URL for calls like `/getPage/{path}` and `/editPage/{path}`, you can pin the agent to a single page so it reads and edits only that page. You also choose the operations it may call, so sensitive ones such as /revokeAccessToken stay out of reach unless you explicitly add them.