Get the invoicing status
curl --request GET \
--url https://api.melso.ai/v1/companies/{company_id}/invoicing \
--header 'Authorization: Bearer <token>'import requests
url = "https://api.melso.ai/v1/companies/{company_id}/invoicing"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text)const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://api.melso.ai/v1/companies/{company_id}/invoicing', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));{
"status": "pending",
"invoicing_ready": true,
"fiscal_network": "verifactu",
"fiscal_missing": [
"<string>"
],
"invoicing_missing": [
"<string>"
],
"authorization_url": "<string>",
"error": "<string>"
}{
"error": "invalid token",
"code": "unauthorized",
"request_id": "req_01JAB3K9X2"
}{
"error": "Review and approve in the authenticated web application",
"code": "person_required",
"request_id": "req_01JAB3K9X2"
}{
"error": "invoice not found",
"code": "not_found",
"request_id": "req_01JAB3K9X2"
}Invoicing setup
Get the invoicing status
Whether the company can issue invoices: its registration as an issuer with VERI*FACTU or TicketBAI, and what its fiscal profile still lacks.
GET
/
companies
/
{company_id}
/
invoicing
Get the invoicing status
curl --request GET \
--url https://api.melso.ai/v1/companies/{company_id}/invoicing \
--header 'Authorization: Bearer <token>'import requests
url = "https://api.melso.ai/v1/companies/{company_id}/invoicing"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text)const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://api.melso.ai/v1/companies/{company_id}/invoicing', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));{
"status": "pending",
"invoicing_ready": true,
"fiscal_network": "verifactu",
"fiscal_missing": [
"<string>"
],
"invoicing_missing": [
"<string>"
],
"authorization_url": "<string>",
"error": "<string>"
}{
"error": "invalid token",
"code": "unauthorized",
"request_id": "req_01JAB3K9X2"
}{
"error": "Review and approve in the authenticated web application",
"code": "person_required",
"request_id": "req_01JAB3K9X2"
}{
"error": "invoice not found",
"code": "not_found",
"request_id": "req_01JAB3K9X2"
}Live capability. Melso runs this in production today. Partner keys reach it once your partner account is enabled. See Availability.
authorization_url is the
page where they give it.Authorizations
Your partner secret key, mk_live_… for real companies or mk_test_…
for test companies. Keep it on your servers. See
Authentication.
Path Parameters
The company's ID. Every company-scoped call works in exactly this company.
Response
The status.
Available options:
pending, active, error The company can issue invoices.
Empty while the tax territory is unknown.
Available options:
verifactu, ticketbai, Fiscal profile fields still missing.
Invoicing fields still missing, such as vat_regime or city.
While pending, where the owner authorizes registration. Valid for 24 hours.