How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Mendable Ingestion API

Ingest and track data sources.

Mendable Ingestion API is one of 4 APIs that Mendable publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Ingestion. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 3 operations across 3 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://api.mendable.ai/v1.

3 operations 3 paths 5 schemas 3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.mendable.ai/v1
Authentication
API Key, HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 2

Mendable Ingestion API declares 2 security schemes for authenticating requests. An API key is passed in the query as api_key (apiKeyBody). It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • apiKeyBody — Mendable apikey. Sent as the apikey field inside the JSON request body for every endpoint (modeled here as apiKey for tooling).
  • bearerAuth — Mendable apikey supplied as a Bearer token in the Authorization header.

Paths & Operations 3

Across 3 paths, the API surfaces 3 operations — 3 POST. Each is listed below with its method, path, parameters, and response codes.

Ingestion 3

Ingest and track data sources.

POST
/ingestData
Ingest a data source by URL
ingestData body → 200400
POST
/ingestDocuments
Ingest raw documents
ingestDocuments body → 200400
POST
/ingestionStatus
Check ingestion task status
ingestionStatus body → 200400

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are IngestDataRequest (5 properties), IngestDocumentsRequest (3 properties), IngestionStatusResponse (3 properties), IngestionStatusRequest (2 properties). Each schema is shown below with its type and property counts.

IngestTaskResponse
object
1 property
IngestionStatusResponse
object
3 properties
IngestionStatusRequest
object
2 properties 2 required
IngestDocumentsRequest
object
3 properties 2 required
IngestDataRequest
object
5 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mendable-ingestion-api-openapi.yml Raw ↑

Other APIs Mendable publishes across the network.

Mendable Chat API
Mendable Conversations API
Mendable Ratings API
Where this information came from

This is an independent, third-party profile of Mendable Ingestion API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.