aid: temlavo name: Temlavo image: https://temlavo.com/opengraph-image-1c1a04?1ecd09803a86c066 description: 'Temlavo provides an Invoice Extraction API that transforms invoice PDFs and images into structured JSON accounting data. The service extracts line items, performs consistency checks, flags duplicate signals, and supplies explicit review outcomes. It aims to streamline automation workflows for developers handling financial documents.' url: https://raw.githubusercontent.com/api-evangelist/temlavo/refs/heads/main/apis.yml x-type: company x-source: harvest:new-submission x-tier: profiled x-tier-reason: enrichment pass 2026-10-02 (modular-v1; was harvest) specificationVersion: '0.20' created: '2026-10-02' modified: '2026-10-05' tags: - Company - Invoices - Extraction - Accounting tags_raw: - Company - Invoice - Extraction - API - Accounting maintainers: - FN: Kin Lane email: kin@apievangelist.com - FN: APIs.json email: info@apis.io common: - type: Plans url: plans/temlavo-plans-pricing.yml - type: Security url: security/temlavo-vulnerability-disclosure.yml - type: LLMsTxt url: llms/temlavo-llms.txt - type: Hosts url: hosts/temlavo-hosts.yml - type: Vendors url: vendors/temlavo-vendors.yml - type: Packages url: packages/temlavo-packages.yml - type: TermsOfService url: https://temlavo.com/terms - type: SDKs url: https://www.npmjs.com/package/@temlavo/sdk - type: PrivacyPolicy url: https://temlavo.com/privacy - type: APIReference url: https://temlavo.com/docs/api-reference - type: VulnerabilityDisclosure url: security/temlavo-vulnerability-disclosure.yml - type: DomainSecurity url: security/temlavo-domain-security.yml - type: Website url: https://temlavo.com - type: Documentation url: https://temlavo.com/docs - type: DeveloperPortal url: https://temlavo.com/playground - type: Pricing url: https://temlavo.com/pricing - type: Support url: https://temlavo.com/security - type: SignUp url: https://temlavo.com/sign-up - type: Login url: https://temlavo.com/sign-in apis: - aid: temlavo:temlavo-documents-api name: Temlavo Documents API description: Invoice document operations of the Temlavo Invoice Extraction API (OpenAPI 3.1, version 1.0.0) — create an invoice document and receive an upload authorization, confirm a direct upload so it is admitted for processing, retrieve the document resource with its extracted data, consistency checks and duplicate signals, and delete a document with its retained customer content. Bearer API key authentication. humanURL: https://temlavo.com/docs baseURL: https://api.temlavo.com tags: - Documents properties: - type: OpenAPI url: openapi/temlavo-documents-api-openapi.yml - type: OpenAPI name: OpenAPI (provider-hosted, docs host) url: https://temlavo.com/openapi.json - type: Documentation url: https://temlavo.com/docs - type: APIReference url: https://temlavo.com/docs/api-reference - type: JSONSchema name: Invoice JSON Schema (invoice.v1) url: https://temlavo.com/schemas/invoice.v1.json - aid: temlavo:temlavo-usage-api name: Temlavo Usage API description: Usage operation of the Temlavo Invoice Extraction API — retrieve current or historical processing usage for the account. Bearer API key authentication. humanURL: https://temlavo.com/docs baseURL: https://api.temlavo.com tags: - Usage properties: - type: OpenAPI url: openapi/temlavo-usage-api-openapi.yml - type: OpenAPI name: OpenAPI (provider-hosted, docs host) url: https://temlavo.com/openapi.json - type: Documentation url: https://temlavo.com/docs - type: APIReference url: https://temlavo.com/docs/api-reference x-submission-notes: Invoice extraction API turning invoice PDFs/images into accounting data. x-submission-probe: root 200; docs 200; OpenAPI 3.1.0 4 paths server api.temlavo.com; llms.txt 200; 404 probe 404 x-submitted-by: marketing@temlavo.com (apis.io/add, 2026-10-02) x-coverage: state: covered reason: contract-on-docs-host detail: >- The OpenAPI 3.1.0 contract (4 paths, 5 operations) is published on the docs host at https://temlavo.com/openapi.json and declares the runtime server https://api.temlavo.com. The earlier unreadable state came from looking for the contract on the API runtime host; corrected at the provider's request (api-evangelist/temlavo#1). evidence: - url: https://temlavo.com/openapi.json status: 200 - url: https://temlavo.com/schemas/invoice.v1.json status: 200 checked: '2026-10-05' x-enrichment: date: '2026-10-02' status: enriched artifacts_added: 9 pass: modular-v1 engine: identity=local,contract=local,surfaces=local,docs=local,regulatory=local x-correction-request: requested: '2026-10-05' source: - https://github.com/api-evangelist/temlavo/issues/1 request: 'Issue #1 (stefanoskalt), verified live 2026-10-05. https://temlavo.com/openapi.json returns 200 application/json: OpenAPI 3.1.0, "Temlavo Invoice Extraction API" version 1.0.0, server https://api.temlavo.com, 4 paths and 5 operations (createDocument, completeDocumentUpload, getDocument, deleteDocument, getUsage), bearer API key security, no tags. https://temlavo.com/docs, https://temlavo.com/docs/api-reference, https://temlavo.com/schemas/invoice.v1.json and https://temlavo.com/llms.txt all return 200; an invented /docs path returns a real 404. https://api.temlavo.com/ returns 200 with an empty body (it also answers 200 on an invented path, so the runtime host is not a document source). Associate the docs-host OpenAPI with the Temlavo API entry.' applied: '2026-10-05' applied_note: Saved https://temlavo.com/openapi.json verbatim as openapi/_original/temlavo-openapi.json and split it (operations untagged, so grouped by path) into openapi/temlavo-documents-api-openapi.yml (4 operations) and openapi/temlavo-usage-api-openapi.yml (1 operation), registered as two API entries with baseURL https://api.temlavo.com and the provider-hosted OpenAPI, docs, API reference and invoice JSON Schema as properties. x-coverage moved from unreadable to covered. Scoring reruns on the next scheduled pass.