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

Malt Fee Invoices API

Operations related to freelancer service charge invoices

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

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

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

Requests are made against a single base URL, https://api.malt.com.

3 operations 3 paths 5 schemas 3 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.0.1
Base URL
https://api.malt.com
Authentication
HTTP Bearer, API Key
Resource Areas
1

Authentication & Security 2

Malt Fee Invoices API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (BearerAuth). An API key is passed in the header as Authorization (ApiKeyAuth).

  • BearerAuth — API token obtained from your Malt representative
  • ApiKeyAuth — To obtain an access token, please follow [these instructions](https://api.malt.com).

Paths & Operations 3

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

Fee Invoices 3

Operations related to freelancer service charge invoices

GET
/freelancer/fee-invoices
Retrieve a list of service charge invoices from a date range
findFeeInvoices 2 params → 200400401403
GET
/freelancer/fee-invoices/{id}
Get a service charge invoice by its id
getFeeInvoice 1 param → 200401403404
GET
/freelancer/fee-invoices/{id}/pdf
Get an fee invoice PDF by its id
getFeeInvoicePdf 1 param → 200401403404

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are CustomerResource (8 properties), SupplierResource (8 properties), FeeInvoiceResource (7 properties), TaxResource (3 properties). Each schema is shown below with its type and property counts.

TaxResource
object
Represents a tax line item
3 properties 3 required
SupplierResource
object
Represents a supplier (freelancer) for invoicing
8 properties 1 required
CustomerResource
object
Represents a customer (client) for invoicing
8 properties 1 required
PDFInvoiceResource
object
Represents an invoice in PDF format
2 properties 2 required
FeeInvoiceResource
object
Represents a service charge invoice
7 properties 7 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

malt-fee-invoices-api-openapi.yml Raw ↑

Other APIs Malt publishes across the network.

Malt Invoices API
Malt Payments API
Malt SCIM API
Where this information came from

This is an independent, third-party profile of Malt Fee Invoices 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.