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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
InvoiceCraftly Developer Document API

InvoiceCraftly Developer Document API Structured invoicing API

EN16931-core readiness and structured XML.

Documentation Provider Profile APIs.io OpenAPI GitHub

InvoiceCraftly Developer Document API Structured invoicing API is one of 2 APIs that InvoiceCraftly Developer Document API publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 4 JSON Schema definitions.

Tagged areas include Structured invoicing. The published artifact set on APIs.io includes an OpenAPI specification and 4 JSON Schemas.

This API exposes 2 operations across 2 paths, and defines 16 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0-beta.

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

2 operations 2 paths 16 schemas 2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0-beta
Base URL
https://invoicecraftly.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

InvoiceCraftly Developer Document API Structured invoicing API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (dk_live_*) (bearerAuth). By default, every request must be authenticated.

Paths & Operations 2

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

Structured invoicing 2

EN16931-core readiness and structured XML.

POST
/api/v1/invoices/readiness
Check EN16931-core readiness
checkInvoiceReadiness body → 200400401413422503
POST
/api/v1/documents/structured
Generate EN16931-core structured XML
generateStructuredInvoice body → 200400401413422503

Schemas 16

The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are PublicDocumentV1 (13 properties), Payment (10 properties), ComplianceLine (5 properties), ComplianceSupplementV1 (5 properties). Each schema is shown below with its type and property counts.

Party
object
2 properties 2 required
ComplianceParty
object
5 properties
StructuredArtifactResponse
Logo
object
2 properties 2 required
PublicStructuredArtifactRequestV1
object
2 properties 1 required
ReadinessResponse
object
5 properties 5 required
ComplianceSupplementV1
object
Optional EN16931-core metadata. Unknown nested fields are ignored by the current normalizer; listed fields are the supported public surface.
5 properties
TaxIdMetadata
object
3 properties
LineItem
object
5 properties 4 required
TaxRegistrationIdentifier
object
2 properties
ErrorEnvelope
object
1 property 1 required
Branding
object
3 properties
PostalAddress
object
4 properties
ComplianceLine
object
5 properties 1 required
Payment
object
10 properties
PublicDocumentV1
object
13 properties 6 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

invoicecraftly-structured-invoicing-api-openapi.yml Raw ↑

Other APIs InvoiceCraftly Developer Document API publishes across the network.

InvoiceCraftly Developer Document API Documents API
AE Profile APIs.io
#Structured invoicing
← Back to I APIs
API Details
ID
invoicecraftly:invoicecraftly-structured-invoicing-api
Base URL
https://invoicecraftly.com
Docs
https://invoicecraftly.com/developers/
Provider
InvoiceCraftly Developer Document API
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=invoicecraftly-structured-invoicing-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/invoicecraftly-structured-invoicing-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of InvoiceCraftly Developer Document API Structured invoicing 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.