biziq
API docs by Redocly

Biziq API (1.0)

Download OpenAPI specification:Download

Biziq Documentation: [email protected]

Terms conditions and legal terms
Privacy Policy

Overview

The Biziq API is a collection of web services that allow you to receive payments from customers, be notified of those payments, refund them if necessary, among others.

URLs

The API endpoints are available through the following domains:

  • For sandbox environment:
      https://sandboxapi.biziq.app/
  • For production environment:
      https://api.biziq.app/

Authentication

To check your credentials for the API you can go to the API tab on our software.

Server-to-server requests to the API you must be authenticated via Account ID and API Key. If you are associated to more than one company you may also need the Company VAT. To do so, include the following HTTP headers in your API requests:

accountid: <YOUR_ACCOUNT_ID>
apikey: <YOUR_API_KEY>
company_vat: <YOUR_COMPANY_VAT>

When these headers are missing or incorrect, a 401 HTTP status code is returned.

Errors

Biziq uses HTTP response status codes to indicate the success or failure of your API requests. If your request fails, Biziq returns an error using the appropriate status code.

In general, there are three status code ranges you can expect:

  • 2xx success status codes confirm that your request worked as expected
  • 4xx error status codes indicate an error because of the information provided (for example, a required parameter was omitted).
  • 5xx error status codes are rare and indicate an error with Biziq’s servers.

Some 4xx errors that could be handled programmatically include an error code (a short string with a brief explanation) as a value for code.

Below is a list of possible error codes that can be returned, along with additional information about how to resolve them.

Authentication Error

This error can have multiple potential causes. Here are some examples:

  • Missing/Invalid aaccountid and/or apikey Headers
  • Your account has been blocked
  • You don't enough permissions to the action requested

Invalid Content Type Error

This error can only have one cause, you provided an invalid/unsupported content type header.

Invalid JSON Error

This error happens when you provide a bad formated JSON payload.

Invalid Params Error

This error indicates the information provided was incorrect of insufficient (for example, a required parameter was omitted).

Internal Error

This error indicates that an unexpected error ocurred on our servers.

User

This segment outlines various requests that users can execute to effectively manage their personal information within the Biziq platform.

Create User

To successfully create a user, users are only required to furnish the AUTHORIZATIONS parameters.

Authorizations:
(accountidapikeycompany_vat)
query Parameters
address
string

Use's address

city
string

User's city

country
required
string

User's country

birth_date
date

User's birth date

name
required
string

User's name

email
required
email

User's email

password
required
string

User's password

confirm_password
required
string

Must be equal to password

password
required
string

User's password

postal_code
string

User's postal code

Responses

Response samples

Content type
application/json
{
  • "response": "success",
  • "user": {
    }
}

User Details

To successfully get user's data, users are only required to furnish the AUTHORIZATIONS parameters.

Authorizations:
(accountidapikeycompany_vat)

Responses

Response samples

Content type
application/json
{
  • "response": "success",
  • "user": {
    }
}

Company

This segment provides comprehensive insights and guidelines on leveraging the company settings capabilities of the Biziq API.

Get Company

To successfully get company's data, users are only required to furnish the AUTHORIZATIONS parameters.

Authorizations:
(accountidapikeycompany_vat)

Responses

Response samples

Content type
application/json
{
  • "response": "success",
  • "message": {
    }
}

Crate Company

To successfully create a Company, users are required to furnish the relevant data within the request body, formatted in JSON. The body parameters integral to this request include:

Authorizations:
(accountidapikeycompany_vat)
query Parameters
ask_access
boolean

IF the Company already exists, this paramenter will help create a request to access the company

address
required
string

Company's address

city
required
string

Company's city

conservatory
string

Company's conservatory

company_type
string

Company's type

country
required
string

Company's country

name
required
string

Company's name

new_services
required
boolean

If you want to receive updates on the services available for your Company

services
required
Array of arrays

The Biziq services you want to use in your Company

share_capital
required
number

The Company's share capital

postal_code
required
string

Company's address postal code

vat_number
required
string

Company's VAT Number

Responses

Response samples

Content type
application/json
{
  • "response": "success",
  • "message": {
    }
}

Update Company

To successfully update a Company, users are required to furnish the relevant data within the request body, formatted in JSON. The body parameters integral to this request include:

Authorizations:
(accountidapikeycompany_vat)
query Parameters
city
required
string

Company's address

business_email
required
string

Company's email

city
required
string

Company's address city

postal_code
required
string

Company's address postal code

Responses

Response samples

Content type
application/json
{
  • "response": "success",
  • "message": {
    }
}

Clients

This segment provides comprehensive insights and guidelines on leveraging the invoicing capabilities of the Biziq API. Whether you’re initiating transactions, managing financial records, or enhancing your invoicing workflows, this section serves as your go-to resource. Endpoints for managing Clients under the Invoicing section.

Get Clients

To successfully get company's clients, users are required to furnish the relevant data within the request body, formatted in JSON. The body parameters integral to this request include:

Authorizations:
(accountidapikeycompany_vat)
query Parameters
name
string

To search for clients with that name

code
string

To search for clients with that code

Responses

Response samples

Content type
application/json
{
  • "response": "success",
  • "message": {
    }
}

Credit Notes

This segment provides comprehensive insights and guidelines on leveraging the invoicing capabilities of the Biziq API. Whether you’re initiating transactions, managing financial records, or enhancing your invoicing workflows, this section serves as your go-to resource. Endpoints for managing credit notes under the Invoicing section.

Create Credit Note

Authorizations:
(accountidapikeycompany_vat)
query Parameters
date
string <Y-m-d>

Date of the Credit Note

name
required
string

Name of the Original Document

serie
required
string

Name of the Series, belonging to the same Company as the Original Document, of the Credit Note type

reason
required
string

Reason why the Credit Note is being created

object

Items present in the Original Document (optional; if not provided, all items available in the Original Document will be used).

Responses

Response samples

Content type
application/json
{
  • "response": "success",
  • "message": {
    }
}

Get Credit Note

Authorizations:
(accountidapikeycompany_vat)
query Parameters
name
string

Invoice Identification

document_id
string

Document Identification

Request Body schema: application/json
Any of
name
required
string
document_id
string

Responses

Request samples

Content type
application/json
{
  • "name": "string",
  • "document_id": "string"
}

Response samples

Content type
application/json
{
  • "response": "success",
  • "message": {
    }
}

Change Credit Note Status

Authorizations:
(accountidapikeycompany_vat)
query Parameters
name
string

Document Identification

document_id
string

Document Identification

status
required
string
Enum: "final" "canceled" "deleted"

The status you want to put your Document

cancelation_reason
string

The reason why you want to cancel your Document

Request Body schema: application/json
Any of
name
required
string
document_id
string
status
required
string
cancelation_reason
string

Responses

Request samples

Content type
application/json
{
  • "name": "string",
  • "document_id": "string",
  • "status": "string",
  • "cancelation_reason": "string"
}

Response samples

Content type
application/json
{
  • "response": "success",
  • "message": "Your document was successfully finalized"
}

Items

This segment provides comprehensive insights and guidelines on leveraging the invoicing capabilities of the Biziq API. Whether you’re initiating transactions, managing financial records, or enhancing your invoicing workflows, this section serves as your go-to resource. Endpoints for managing items under the Invoicing section.

Get Items

To successfully get company's items, users are required to furnish the relevant data within the request body, formatted in JSON. The body parameters integral to this request include:

Authorizations:
(accountidapikeycompany_vat)
query Parameters
code
string

To search for items with that code

type
string
Enum: "Product" "Service" "Other" "ST" "TPC"

To search for item of that type

Responses

Response samples

Content type
application/json
{
  • "response": "success",
  • "message": {
    }
}

Invoices

This segment provides comprehensive insights and guidelines on leveraging the invoicing capabilities of the Biziq API. Whether you’re initiating transactions, managing financial records, or enhancing your invoicing workflows, this section serves as your go-to resource. Endpoints for managing invoices under the Invoicing section.

Get Summary

To successfully get the invoicing summary, users are required to furnish the relevant data within the request body, formatted in JSON. The body parameters integral to this request include:

Authorizations:
(accountidapikeycompany_vat)
query Parameters
period
string
Enum: "today" "week" "month" "between_dates"

Period where the Summary takes place

start_date
string <Y-m-d>

Required if 'period' is 'between_dates', and defines the start date of the summary

end_date
string <Y-m-d>

Required if 'period' is 'between_dates', and defines the end date of the summary

Responses

Response samples

Content type
application/json
{
  • "response": "success",
  • "message": {
    }
}

Create Invoice

To successfully add a new invoice, users are required to furnish the relevant invoice data within the request body, formatted in JSON. The body parameters integral to this request include:

Authorizations:
(accountidapikeycompany_vat)
query Parameters
inv_date
string <Y-m-d>
Default: "Today's date"

Invoice Date

currency
string
Default: "€"

Invoice currency

due
string <Y-m-d>

Invoice due date

generateRefMB
boolean

If you want to generate a MB Reference to the document (only available to invoices)

is_receipt
string
Default: "invoice"

Type of document (“invoice” for invoices, “receipt” for invoice receipts, “simplified” for simplified invoices)

paybylink
boolean

If you want to generate a PayByLink link!

payment_method
string

The invoice payment method. If it exists it will use the existing one, if it is deactivated it will be activated and if it does not exist it will be created.

tax_exemption
string

Reason for exemption from fees

recurrence
string

Invoice recurrence

remarks
string

User notes

retention
number

Invoice retention

send_to_client
boolean

Whether the invoice was sent to the client

showIban
boolean

If you want to show Company's IBAN in the document (only available to invoices)

status
string
Default: "final"

Invoice status (final or draft)

required
object

Client identification number group

required
object

List of invoice line items

Responses

Response samples

Content type
application/json
{
  • "response": "success",
  • "message": {
    }
}

Update Invoice

To successfully update a invoice, users are required to furnish the relevant invoice data within the request body, formatted in JSON. The body parameters integral to this request include:

Authorizations:
(accountidapikeycompany_vat)
query Parameters
document_id
required
number

Invoice identification

inv_date
string <Y-m-d>
Default: "Today's date"

Invoice Date

currency
string
Default: "€"

Invoice currency

due
string <Y-m-d>

Invoice due date

generateRefMB
boolean

If you want to generate a MB Reference to the document (only available to invoices)

is_receipt
string
Default: "invoice"

Type of document (“invoice” for invoices, “receipt” for invoice receipts, “simplified” for simplified invoices)

paybylink
boolean

If you want to generate a PayByLink link!

payment_method
string

The invoice payment method. If it exists it will use the existing one, if it is deactivated it will be activated and if it does not exist it will be created.

tax_exemption
string

Reason for exemption from fees

recurrence
string

Invoice recurrence

remarks
string

User notes

retention
number

Invoice retention

send_to_client
boolean

Whether the invoice was sent to the client

showIban
boolean

If you want to show Company's IBAN in the document (only available to invoices)

status
string
Default: "final"

Invoice status (final or draft)

required
object

List of invoice line items

Responses

Response samples

Content type
application/json
{
  • "response": "success",
  • "message": {
    }
}

Get Invoice

Authorizations:
(accountidapikeycompany_vat)
query Parameters
name
string

Invoice Identification

document_id
string

Document Identification

Request Body schema: application/json
Any of
name
required
string
document_id
string

Responses

Request samples

Content type
application/json
{
  • "name": "string",
  • "document_id": "string"
}

Response samples

Content type
application/json
{
  • "response": "success",
  • "message": {
    }
}

Change Invoice Status

Authorizations:
(accountidapikeycompany_vat)
query Parameters
name
string

Document Identification

document_id
string

Document Identification

status
required
string
Enum: "final" "canceled" "deleted"

The status you want to put your Document

cancelation_reason
string

The reason why you want to cancel your Document

Request Body schema: application/json
Any of
name
required
string
document_id
string
status
required
string
cancelation_reason
string

Responses

Request samples

Content type
application/json
{
  • "name": "string",
  • "document_id": "string",
  • "status": "string",
  • "cancelation_reason": "string"
}

Response samples

Content type
application/json
{
  • "response": "success",
  • "message": "Your document was successfully finalized"
}

Send Invoices

Authorizations:
(accountidapikeycompany_vat)
query Parameters
names
required
Array of arrays

Invoices Identification

mail
mail

Email to send the Invoice, if not set the Invoice is sent to the clients email

Responses

Response samples

Content type
application/json
{
  • "response": "success",
  • "message": {
    }
}

Mass Importe

To successfully import data to mass create invoices, users are required to furnish the relevant invoice data within the request body, formatted in JSON. The body parameters integral to this request include:

Authorizations:
(accountidapikeycompany_vat)
query Parameters
company_vat
integer

company VAT number

required
Array of objects

This array can have multiple invoices to be created

Responses

Response samples

Content type
application/json
{
  • "response": "success",
  • "bash_id": "8a005421-77ee-44d3-a84c-cceef66c11a3",
  • "invalid": {
    }
}

Mass Import Status

Authorizations:
(accountidapikeycompany_vat)
query Parameters
hash
string

Mass import hash

page
int

Page number for pagination

Responses

Response samples

Content type
application/json
{
  • "response": "success",
  • "queued_count": 0,
  • "done_count": 191,
  • "data": {
    }
}

Proformas

This segment provides comprehensive insights and guidelines on leveraging the invoicing capabilities of the Biziq API. Whether you’re initiating transactions, managing financial records, or enhancing your invoicing workflows, this section serves as your go-to resource. Endpoints for managing proformas under the Invoicing section.

Create Proforma

To successfully add a new proforma, users are required to furnish the relevant invoice data within the request body, formatted in JSON. The body parameters integral to this request include:

Authorizations:
(accountidapikeycompany_vat)
query Parameters
date
string <Y-m-d>
Default: "Today's date"

Proforma Date

currency
string
Default: "€"

Proforma currency

due
string <Y-m-d>

Proforma due date

payment_method
string

The proforma payment method. If it exists it will use the existing one, if it is deactivated it will be activated and if it does not exist it will be created.

tax_exemption
string

Reason for exemption from fees

remarks
string

User notes

retention
number

Proforma retention

send_to_client
boolean

Whether the proforma was sent to the client

status
string
Default: "final"

Proforma status (final or draft)

required
object

Client identification number group

required
object

List of invoice line items

Responses

Response samples

Content type
application/json
{
  • "response": "success",
  • "message": {
    }
}

Update Proforma

To successfully update a Proforma, users are required to furnish the relevant invoice data within the request body, formatted in JSON. The body parameters integral to this request include:

Authorizations:
(accountidapikeycompany_vat)
query Parameters
document_id
required
number

Invoice identification

date
string <Y-m-d>
Default: "Today's date"

Proforma Date

currency
string
Default: "€"

Proforma currency

due
string <Y-m-d>

Proforma due date

payment_method
string

The proforma payment method. If it exists it will use the existing one, if it is deactivated it will be activated and if it does not exist it will be created.

tax_exemption
string

Reason for exemption from fees

remarks
string

User notes

retention
number

Proforma retention

send_to_client
boolean

Whether the proforma was sent to the client

status
string
Default: "final"

Proforma status (final or draft)

required
object

List of invoice line items

Responses

Response samples

Content type
application/json
{
  • "response": "success",
  • "message": {
    }
}

Get Proforma

Authorizations:
(accountidapikeycompany_vat)
query Parameters
name
string

Invoice Identification

document_id
string

Document Identification

Request Body schema: application/json
Any of
name
required
string
document_id
string

Responses

Request samples

Content type
application/json
{
  • "name": "string",
  • "document_id": "string"
}

Response samples

Content type
application/json
{
  • "response": "success",
  • "message": {
    }
}

Change Proforma Status

Authorizations:
(accountidapikeycompany_vat)
query Parameters
name
string

Document Identification

document_id
string

Document Identification

status
required
string
Enum: "final" "canceled" "deleted"

The status you want to put your Document

cancelation_reason
string

The reason why you want to cancel your Document

Request Body schema: application/json
Any of
name
required
string
document_id
string
status
required
string
cancelation_reason
string

Responses

Request samples

Content type
application/json
{
  • "name": "string",
  • "document_id": "string",
  • "status": "string",
  • "cancelation_reason": "string"
}

Response samples

Content type
application/json
{
  • "response": "success",
  • "message": "Your document was successfully finalized"
}

Quotations

This segment provides comprehensive insights and guidelines on leveraging the invoicing capabilities of the Biziq API. Whether you’re initiating transactions, managing financial records, or enhancing your invoicing workflows, this section serves as your go-to resource. Endpoints for managing quotations under the Invoicing section.

Create Quotation

To successfully add a new quotations, users are required to furnish the relevant invoice data within the request body, formatted in JSON. The body parameters integral to this request include:

Authorizations:
(accountidapikeycompany_vat)
query Parameters
date
string <Y-m-d>
Default: "Today's date"

Quotation Date

currency
string
Default: "€"

Quotation currency

due
string <Y-m-d>

Quotation due date

payment_method
string

The quotation payment method. If it exists it will use the existing one, if it is deactivated it will be activated and if it does not exist it will be created.

tax_exemption
string

Reason for exemption from fees

remarks
string

User notes

retention
number

Quotation retention

send_to_client
boolean

Whether the quotation was sent to the client

status
string
Default: "final"

Quotation status (final or draft)

required
object

Client identification number group

required
object

List of invoice line items

Responses

Response samples

Content type
application/json
{
  • "response": "success",
  • "message": {
    }
}

Update Quotation

To successfully update a Quotation, users are required to furnish the relevant invoice data within the request body, formatted in JSON. The body parameters integral to this request include:

Authorizations:
(accountidapikeycompany_vat)
query Parameters
document_id
required
number

Invoice identification

date
string <Y-m-d>
Default: "Today's date"

Quotation Date

currency
string
Default: "€"

Quotation currency

due
string <Y-m-d>

Quotation due date

payment_method
string

The quotation payment method. If it exists it will use the existing one, if it is deactivated it will be activated and if it does not exist it will be created.

tax_exemption
string

Reason for exemption from fees

remarks
string

User notes

retention
number

Quotation retention

send_to_client
boolean

Whether the quotation was sent to the client

status
string
Default: "final"

Quotation status (final or draft)

required
object

List of invoice line items

Responses

Response samples

Content type
application/json
{
  • "response": "success",
  • "message": {
    }
}

Get Quotation

Authorizations:
(accountidapikeycompany_vat)
query Parameters
name
string

Invoice Identification

document_id
string

Document Identification

Request Body schema: application/json
Any of
name
required
string
document_id
string

Responses

Request samples

Content type
application/json
{
  • "name": "string",
  • "document_id": "string"
}

Response samples

Content type
application/json
{
  • "response": "success",
  • "message": {
    }
}

Change Quotation Status

Authorizations:
(accountidapikeycompany_vat)
query Parameters
name
string

Document Identification

document_id
string

Document Identification

status
required
string
Enum: "final" "canceled" "deleted"

The status you want to put your Document

cancelation_reason
string

The reason why you want to cancel your Document

Request Body schema: application/json
Any of
name
required
string
document_id
string
status
required
string
cancelation_reason
string

Responses

Request samples

Content type
application/json
{
  • "name": "string",
  • "document_id": "string",
  • "status": "string",
  • "cancelation_reason": "string"
}

Response samples

Content type
application/json
{
  • "response": "success",
  • "message": "Your document was successfully finalized"
}

Receipts

This segment provides comprehensive insights and guidelines on leveraging the invoicing capabilities of the Biziq API. Whether you’re initiating transactions, managing financial records, or enhancing your invoicing workflows, this section serves as your go-to resource. Endpoints for managing receipts under the Invoicing section.

Create Receipt

To successfully add a new Receipt, users are required to furnish the relevant invoice data within the request body, formatted in JSON. The body parameters integral to this request include:

Authorizations:
(accountidapikeycompany_vat)
query Parameters
date
string <Y-m-d>
Default: "Today's date"

Receipt Date

document_id
number

Identifier of the invoice that is going to generate a Receipt

name
string

Identifier of the invoice that is going to generate a Receipt

payment_date
string <Y-m-d>
Default: "Today's date"

The date when the payment occurred

payment_method
required
string

Method used in the payment

remarks
string

User notes

send_to_client
boolean

Whether the transport guide was sent to the client

status
string
Default: "final"

Transport Guide status (final or draft)

Request Body schema: application/json
Any of
date
string
document_id
number
name
required
string
payment_date
string
payment_method
required
string
remarks
string
send_to_client
boolean
status
string

Responses

Request samples

Content type
application/json
{
  • "date": "string",
  • "document_id": 0,
  • "name": "string",
  • "payment_date": "string",
  • "payment_method": "string",
  • "remarks": "string",
  • "send_to_client": true,
  • "status": "string"
}

Response samples

Content type
application/json
{
  • "response": "success",
  • "message": {
    }
}

Get Receipt

Authorizations:
(accountidapikeycompany_vat)
query Parameters
name
string

Invoice Identification

document_id
string

Document Identification

Request Body schema: application/json
Any of
name
required
string
document_id
string

Responses

Request samples

Content type
application/json
{
  • "name": "string",
  • "document_id": "string"
}

Response samples

Content type
application/json
{
  • "response": "success",
  • "message": {
    }
}

Change Receipt Status

Authorizations:
(accountidapikeycompany_vat)
query Parameters
name
string

Document Identification

document_id
string

Document Identification

status
required
string
Enum: "final" "canceled" "deleted"

The status you want to put your Document

cancelation_reason
string

The reason why you want to cancel your Document

Request Body schema: application/json
Any of
name
required
string
document_id
string
status
required
string
cancelation_reason
string

Responses

Request samples

Content type
application/json
{
  • "name": "string",
  • "document_id": "string",
  • "status": "string",
  • "cancelation_reason": "string"
}

Response samples

Content type
application/json
{
  • "response": "success",
  • "message": "Your document was successfully finalized"
}

Transport Guides

This segment provides comprehensive insights and guidelines on leveraging the invoicing capabilities of the Biziq API. Whether you’re initiating transactions, managing financial records, or enhancing your invoicing workflows, this section serves as your go-to resource. Endpoints for managing transport guides under the Invoicing section.

Create Credit Note

To successfully add a new Transport Guide, users are required to furnish the relevant invoice data within the request body, formatted in JSON. The body parameters integral to this request include:

Authorizations:
(accountidapikeycompany_vat)
query Parameters
charge_date
required
string <Y-m-d>

Charge Date, also know as the date of the beggining of transport, must be equal or after today

charge_hours
required
number

Charge Hours, also know as the hour of the beggining of transport

charge_minutes
required
number

Charge Minutes, also know as the minute of the beggining of transport

charge_address
required
string

Address of where the transport begins

charge_city
required
string

City of where the transport begins

charge_postal_code
required
string

Postal Code of where the transport begins

charge_country
required
string

Country of where the transport begins

date
string <Y-m-d>
Default: "Today's date"

Proforma Date

currency
string
Default: "€"

Proforma currency

delivery_address
required
string

Address of where the transport ends

delivery_city
required
string

City of where the transport ends

delivery_postal_code
required
string

Postal Code of where the transport ends

delivery_country
required
string

Country of where the transport ends

delivery_address
required
string

Address of where the transport ends

tax_exemption
string

Reason for exemption from fees

remarks
string

User notes

registration
string

Transport Vehicle licence plates

send_to_client
boolean

Whether the transport guide was sent to the client

status
string
Default: "final"

Transport Guide status (final or draft)

required
object

Client identification number group

required
object

List of invoice line items

Responses

Response samples

Content type
application/json
{
  • "response": "success",
  • "message": {
    }
}

Update Transport Guide

To successfully update a Transport Guide, users are required to furnish the relevant invoice data within the request body, formatted in JSON. The body parameters integral to this request include:

Authorizations:
(accountidapikeycompany_vat)
query Parameters
document_id
required
number

Invoice identification

charge_date
required
string <Y-m-d>

Charge Date, also know as the date of the beggining of transport, must be equal or after today

charge_hours
required
number

Charge Hours, also know as the hour of the beggining of transport

charge_minutes
required
number

Charge Minutes, also know as the minute of the beggining of transport

charge_address
required
string

Address of where the transport begins

charge_city
required
string

City of where the transport begins

charge_postal_code
required
string

Postal Code of where the transport begins

charge_country
required
string

Country of where the transport begins

date
string <Y-m-d>
Default: "Today's date"

Proforma Date

currency
string
Default: "€"

Proforma currency

delivery_address
required
string

Address of where the transport ends

delivery_city
required
string

City of where the transport ends

delivery_postal_code
required
string

Postal Code of where the transport ends

delivery_country
required
string

Country of where the transport ends

delivery_address
required
string

Address of where the transport ends

tax_exemption
string

Reason for exemption from fees

remarks
string

User notes

registration
string

Transport Vehicle licence plates

send_to_client
boolean

Whether the transport guide was sent to the client

status
string
Default: "final"

Transport Guide status (final or draft)

required
object

List of invoice line items

Responses

Response samples

Content type
application/json
{
  • "response": "success",
  • "message": {
    }
}

Get Transport Guide

Authorizations:
(accountidapikeycompany_vat)
query Parameters
name
string

Invoice Identification

document_id
string

Document Identification

Request Body schema: application/json
Any of
name
required
string
document_id
string

Responses

Request samples

Content type
application/json
{
  • "name": "string",
  • "document_id": "string"
}

Response samples

Content type
application/json
{
  • "response": "success",
  • "message": {
    }
}

Change Transport Guide Status

Authorizations:
(accountidapikeycompany_vat)
query Parameters
name
string

Document Identification

document_id
string

Document Identification

status
required
string
Enum: "final" "canceled" "deleted"

The status you want to put your Document

cancelation_reason
string

The reason why you want to cancel your Document

Request Body schema: application/json
Any of
name
required
string
document_id
string
status
required
string
cancelation_reason
string

Responses

Request samples

Content type
application/json
{
  • "name": "string",
  • "document_id": "string",
  • "status": "string",
  • "cancelation_reason": "string"
}

Response samples

Content type
application/json
{
  • "response": "success",
  • "message": "Your document was successfully finalized"
}

SAFT

This segment provides comprehensive insights and guidelines on leveraging the invoicing capabilities of the Biziq API. Whether you’re initiating transactions, managing financial records, or enhancing your invoicing workflows, this section serves as your go-to resource. Endpoints for managing SAFT under the Invoicing section.

Get SAFT

Authorizations:
(accountidapikeycompany_vat)
query Parameters
start_date
required
string <Y-m-d>

Start Date, also know as the date of the beggining of the Billing Period, must be before End Date

end_date
required
string <Y-m-d>

End Date, also know as the date of the conclusion of the Billing Period, must be after Start Date

rebuild
boolean

If you want to build a new XML file.

Responses

Response samples

Content type
application/json
{}

Series

This segment provides comprehensive insights and guidelines on leveraging the invoicing capabilities of the Biziq API. Whether you’re initiating transactions, managing financial records, or enhancing your invoicing workflows, this section serves as your go-to resource. Endpoints for managing series under the Invoicing section.

Create Serie

To successfully create a new Serie, users are required to furnish the relevant invoice data within the request body, formatted in JSON. The body parameters integral to this request include:

Authorizations:
(accountidapikeycompany_vat)
query Parameters
name
required
string

Series Name

type
string
Default: "invoice"
Enum: "invoice" "invoice_simplified" "invoice_receipt" "transport_guide" "credit_note" "proforma" "quotation" "receipt"

Type of document the series belongs to

validation_code
string

Only necessary if with dont have a communication wuth Tax Authority

Responses

Response samples

Content type
application/json
{
  • "response": "success",
  • "message": {
    }
}

Get Series

Authorizations:
(accountidapikeycompany_vat)
query Parameters
type
string
Default: "invoice"
Enum: "invoice" "invoice_simplified" "invoice_receipt" "transport_guide" "credit_note" "proforma" "quotation" "receipt"

Type of document the series belongs to

Responses

Response samples

Content type
application/json
{
  • "response": "success",
  • "message": {
    }
}

SMS

This segment outlines various requests that users can execute to effectively manage their SMS interactions within the Biziq platform.

Create/Send SMS

In order to dispatch SMS messages, users must provide the necessary data within the request body, formatted in JSON. The essential body parameters for this request include:

Authorizations:
(accountidapikeycompany_vat)
query Parameters
message
required
string

The message that the user intends to send

mobile_num
string

Mobile number of the message recipient

sender
required
string

Identification of the message sender

sms_schedule
string

Schedule for sending the message on a specified day and hour

blk_Add
string

Enables users to send the same message to multiple numbers

mobile_num_blk
string

Identifies the numbers to which the user wants to send a message, separated by commas

template_Add
string

Allows the addition of an SMS template

template_name
string

Name of the SMS template

hh
string

Additional hour information

mm
string

Additional month information

Responses

Response samples

Content type
application/json
{
  • "response": "success",
  • "message": "SMS sent successfully."
}

Sender

This segment outlines various requests that users can execute to effectively manage their SMS interactions within the Biziq platform. Endpoints for managing Senders under the SMS section.

Create Sender

In order to create senders, users must provide the necessary data within the request body, formatted in JSON. The essential body parameters for this request include:

Authorizations:
(accountidapikeycompany_vat)
query Parameters
sender_name
required
string

The sender that the user intends to create

unlimited
boolean

Identifies whether the created sender has an unlimited expiration time

expire_on
date

Identification the expire date

Responses

Response samples

Content type
application/json
{
  • "response": "success",
  • "message": "Sender create successfully."
}

Template

This segment outlines various requests that users can execute to effectively manage their SMS interactions within the Biziq platform. Endpoints for managing Templates under the SMS section.

Create Template

In order to create templates, users must provide the necessary data within the request body, formatted in JSON. The essential body parameters for this request include:

Authorizations:
(accountidapikeycompany_vat)
query Parameters
name
required
string

The name of the template that the user intends to create

template
required
string

The template that the client intends to create

Responses

Response samples

Content type
application/json
{
  • "response": "success",
  • "message": "Template create successfully."
}

Contacts

This segment outlines various requests that users can execute to effectively manage their SMS interactions within the Biziq platform. Endpoints for managing Contacts under the SMS section.

Create Contacts

In order to create contacts, users must provide the necessary data within the request body, formatted in JSON. The essential body parameters for this request include:

Authorizations:
(accountidapikeycompany_vat)
query Parameters
name
required
string

The name the user intends to add to the contact

mobile_number
required
string

Mobile number of the contact

mobile_code_contact
required
string

The country identifier used in the contact to be saved

Responses

Response samples

Content type
application/json
{
  • "response": "success",
  • "message": "Contact successfully created."
}