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

Daloopa Documents API

The Documents API from Daloopa — 5 operation(s) for documents.

Daloopa Documents API is one of 19 APIs that Daloopa publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Documents. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, authentication docs, and rate-limit docs.

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

Requests are made against a single base URL, https://app.daloopa.com.

5 operations 5 paths 14 schemas 4 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.0
Base URL
https://app.daloopa.com/api/v3
Authentication
HTTP Basic
License
Proprietary
Resource Areas
1

Authentication & Security 1

Daloopa Documents API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (apiKeyAuth).

  • apiKeyAuth — Basic authentication with base64-encoded credentials. Format: "Basic base64(email:apiKey)"

Paths & Operations 5

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

Documents 5
GET
/api/v3/documents
Company Document Lookup
company_document_lookup_v3 7 params → 200400401403429500
POST
/api/v3/documents/keyword-search
Keyword Search
opensearch_lightweight_search_v3 body → 200400401403429500
GET
/api/v3/documents/{document_id}
Retrieve Document
retrieve_document 1 param → 200400401403429500
GET
/api/v3/documents/{document_id}/metadata
Retrieve Document Metadata
retrieve_document_metadata 1 param → 200401403404429500
GET
/api/v3/documents/{document_id}/content
Retrieve Document Content
retrieve_document_content 4 params → 200400401403404429500

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are DocumentMetadataResponse (10 properties), LightweightDocumentMatch (10 properties), DocumentMetadataSerializerV3 (7 properties), DocumentContentResponse (6 properties). Each schema is shown below with its type and property counts.

RecommendedCallEnum
string
smallfull - smallfull largewithsection - largewithsection singlesectionfiling - singlesectionfiling notsupported - notsupported
DocumentSection
object
A single named section of a document with its character length.
2 properties 2 required
OperatorEnum
string
AND - AND OR - OR
LightweightBatchSearchResponse
object
Serializer for lightweight batch search responses without positional information.
6 properties 5 required
DocumentMetadataSerializerV3
object
V3 document metadata response serializer. Same shape as :class:DocumentMetadataSerializer but without the deprecated period output field. Kept as a standalone…
7 properties 7 required
DocumentContentResponse
object
Flat response for GET /api/v2/documents/{id}/content. The shape is intentionally narrow: just enough for the caller to use the text. Section-level metadata (th…
6 properties 6 required
BatchSearchRequestSerializerV3Request
object
V3 batch-search request. Same shape as :class:BatchSearchRequestSerializer but nests the v3 filters serializer, which drops the deprecated periods field.
3 properties 1 required
DocumentMetadataResponse
object
Serializer for the GET /api/v2/documents/{id}/metadata response. Surfaces structural metadata only: document identity, filing type, section breakdown with char…
10 properties 9 required
BatchSearchFiltersSerializerV3Request
object
V3 batch-search filters. Same shape as :class:BatchSearchFiltersSerializer but without the deprecated periods field (and thus no LegacyFieldAliasMixin). Kept a…
6 properties
LightweightMatch
object
Serializer for individual lightweight matches.
3 properties 3 required
PaginatedDocumentMetadataSerializerV3List
object
4 properties 2 required
BatchSearchOptionsRequest
object
Serializer for batch search options.
4 properties
LightweightDocumentMatch
object
Serializer for lightweight document matches without positional information.
10 properties 3 required
DocumentRetrievalResponse
object
Serializer for document retrieval responses including signed URL.
4 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

daloopa-documents-api-openapi.yml Raw ↑

Other APIs Daloopa publishes across the network.

Daloopa Auth API
Daloopa Companies API
Daloopa Consumption API
Daloopa Daloopa MCP Service API
Daloopa Data Warehouse API
Daloopa Databricks API
Daloopa Download API
Daloopa Export API
Daloopa Fundamentals API
Daloopa Health API
Daloopa Industry Models API
Daloopa Investing Skills API
Where this information came from

This is an independent, third-party profile of Daloopa Documents 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.