Paraşüt
Paraşüt is a Turkish cloud pre-accounting (ön muhasebe) and e-invoicing SaaS for small businesses, freelancers and accountants. Its REST API V4 exposes nearly everything the Paraşüt web app can do — contacts, products, inventory and warehouses, sales invoices and offers, purchase bills, bank and cash accounts and transactions, employees, salaries and taxes — plus Turkey's official electronic document flows (e-Fatura, e-Arşiv and e-SMM). The API follows JSON:API conventions, is authenticated with OAuth2, and handles e-document creation asynchronously via trackable jobs. Backed by 500 Global.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Paraşüt the way a machine reads it — 31 machine-readable artifacts across 24 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Paraşüt scores 44.6/100 (thin), with a separate agent-readiness read of 65/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Paraşüt
Each block below is one kind of artifact we hold for Paraşüt. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 24
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Paraşüt Accounts API
The Accounts API from Paraşüt — 5 operation(s) for accounts.
Paraşüt ApiHome API
The ApiHome API from Paraşüt — 1 operation(s) for apihome.
Paraşüt BankFees API
The BankFees API from Paraşüt — 5 operation(s) for bankfees.
Paraşüt Contacts API
The Contacts API from Paraşüt — 4 operation(s) for contacts.
Paraşüt EArchives API
The EArchives API from Paraşüt — 3 operation(s) for earchives.
Paraşüt EInvoiceInboxes API
The EInvoiceInboxes API from Paraşüt — 1 operation(s) for einvoiceinboxes.
Paraşüt EInvoices API
The EInvoices API from Paraşüt — 3 operation(s) for einvoices.
Paraşüt Employees API
The Employees API from Paraşüt — 4 operation(s) for employees.
Paraşüt ESmms API
The ESmms API from Paraşüt — 3 operation(s) for esmms.
Paraşüt InventoryLevels API
The InventoryLevels API from Paraşüt — 1 operation(s) for inventorylevels.
Paraşüt ItemCategories API
The ItemCategories API from Paraşüt — 2 operation(s) for itemcategories.
Paraşüt Products API
The Products API from Paraşüt — 2 operation(s) for products.
Paraşüt PurchaseBills API
The PurchaseBills API from Paraşüt — 11 operation(s) for purchasebills.
Paraşüt Salaries API
The Salaries API from Paraşüt — 5 operation(s) for salaries.
Paraşüt SalesInvoices API
The SalesInvoices API from Paraşüt — 8 operation(s) for salesinvoices.
Paraşüt SalesOffers API
The SalesOffers API from Paraşüt — 8 operation(s) for salesoffers.
Paraşüt ShipmentDocuments API
The ShipmentDocuments API from Paraşüt — 2 operation(s) for shipmentdocuments.
Paraşüt StockMovements API
The StockMovements API from Paraşüt — 1 operation(s) for stockmovements.
Paraşüt StockUpdates API
The StockUpdates API from Paraşüt — 1 operation(s) for stockupdates.
Paraşüt Tags API
The Tags API from Paraşüt — 2 operation(s) for tags.
Paraşüt Taxes API
The Taxes API from Paraşüt — 5 operation(s) for taxes.
Paraşüt TrackableJobs API
The TrackableJobs API from Paraşüt — 1 operation(s) for trackablejobs.
Paraşüt Transactions API
The Transactions API from Paraşüt — 1 operation(s) for transactions.
Paraşüt Warehouses API
The Warehouses API from Paraşüt — 2 operation(s) for warehouses.
Scroll within the panel for all 24 ·
Arazzo Workflows 2
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
_Index
ARAZZOParaşüt — invoice a customer and officialize as e-Arşiv
Create a contact, issue a sales invoice, officialize it as an e-Arşiv document, and poll the trackable job until done.
ARAZZOMCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
para-t-mcp.yml
MCP SERVERSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Paraşüt — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/para-t · machine-readable index on apis.io