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

Cobot Invoice API

Invoices are automatically generated once a month, based on members' activity. In addition, manual invoices can be generated at any time.

Cobot Invoice API is one of 44 APIs that Cobot publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 12 operations across 11 paths, and defines 30 schemas. It is described by OpenAPI 3.2.0, at version 2.0.

Requests are made against a single base URL, https://api.cobot.me.

12 operations 11 paths 30 schemas 1 DELETE6 GET5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0
Base URL
https://api.cobot.me
Authentication
OpenID Connect, OAuth 2.0
Terms of Service
Resource Areas
1

Authentication & Security 2

Cobot Invoice API declares 2 security schemes for authenticating requests. It supports OpenID Connect (OpenId) discovered at https://www.cobot.me/.well-known/openid-configuration. It supports OAuth 2.0 (OAuth2) using the authorizationCode flow, exposing 58 scopes. By default, every request must be authenticated.

  • OAuth2 — OAuth is "an open protocol to allow secure API authorization in a simple and standard method from desktop and web applications.". "OAuth 2.0 is the next evolut…

Paths & Operations 12

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

Invoice 12

Invoices are automatically generated once a month, based on members' activity. In addition, manual invoices can be generated at any time.

POST
/invoice_charges
Charge invoices
create-invoice-charges body → 202
POST
/invoices
Create custom
post-invoices body → 201422
GET
/invoices/{id}
Single invoice
get-invoice 1 param → 200
GET
/invoices/{id}.pdf
Single invoice PDF
get-invoice-pdf 3 params → 200
POST
/invoices/{id}/lock
Lock invoice
lock-invoice 1 param → 200
DELETE
/invoices/{id}/lock
Remove invoice lock
unlock-invoice 1 param → 200409
POST
/invoices/{id}/e_invoice
Create an e-invoice for invoice
create-e-invoice 1 param body → 200
POST
/invoices/{id}/pdf
Attach PDF to invoice
attach-invoice-pdf 1 param body → 200
GET
/invoices/{id}/payment_methods
Payment methods
get-invoice-payment-methods 1 param → 200
GET
/spaces/{spaceId}/invoice_previews
Previews
get-space-membership-invoice-previews 4 params → 200
GET
/spaces/{spaceId}/invoices
List
get-space-invoices 7 params → 200
GET
/spaces/{spaceId}/invoices/search
Search
search-space-invoices 6 params → 200

Schemas 30

The contract defines 30 schemas that model the data the API accepts and returns. The most detailed are invoiceAddress (10 properties), error (8 properties), structuredAddress (7 properties), pagination-links (5 properties). Each schema is shown below with its type and property counts.

payment-methods
object
3 properties 1 required
currency
string
ISO 4217 3 letter currency code.
create-custom-invoice
object
1 property 1 required
links
object
taxes
tax
object
3 properties
positive-decimal
string
A positive decimal number (= 0).
structuredAddress
object
Either name or company is required.
7 properties 6 required
date
string
A date in the form YYYY-MM-DD.
error
object
8 properties
revenue-account
object
2 properties 2 required
decimal
string
A decimal number.
pagination-links
object
5 properties 3 required
address-2
object
Either name or company is required.
3 properties 3 required
link
A link MUST be represented as either: a string containing the link's URL or a link object.
price
object
Price including net/gross value and all taxes.
4 properties 4 required
invoice
object
1 property 1 required
pagination-meta
object
2 properties
cost-center
object
2 properties 2 required
create_e_invoice
object
1 property
invoiceAddress
object
10 properties 8 required
failure
object
4 properties 1 required
jsonapi
object
An object describing the server's implementation
2 properties
create-invoice-charges
object
1 property 1 required
invoices
object
3 properties 1 required
invoice-charges
object
1 property 1 required
meta
object
Non-standard meta-information that can not be represented as an attribute or relationship.
attach-invoice-pdf
object
3 properties 1 required
invoice-previews
object
3 properties 1 required
-invoice-data
object
4 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cobot-invoice-api-openapi.yml Raw ↑

Other APIs Cobot publishes across the network.

Cobot API v1 (legacy)
Cobot MCP Server
Cobot Allocation API
Cobot Approval API
Cobot Article API
Cobot Booking API
Cobot Booking Credit API
Cobot Built-in Email Customizations API
Cobot Calendar Blocker API
Cobot Check In API
Cobot Contact API
Cobot Cost Center API
Where this information came from

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