Skip to main content

​
Overview

The Issuer endpoint manages the company’s tax information used for generating electronic tax documents (DTE). Each tenant has a single issuer configuration that stores the company’s legal and tax details required by Chilean SII.
The issuer is a singleton per tenant. There can only be one issuer configuration per tenant schema.

​
Get Issuer

​
Response

​
id
integer
Unique identifier for the issuer
​
rut
string
Chilean RUT (tax ID) of the company
​
razon_social
string
Legal business name
​
giro
string
Line of business (commercial activity description)
​
acteco
string
Primary ACTECO code (Chilean economic activity code)
​
direccion
string
Street address
​
comuna
string
Municipality/commune
​
ciudad
string
City
​
telefono
string
Contact phone number
​
email
string
Contact email address
​
website
string
Company website (optional)

​
Example Request

cURL
curl -X GET http://localhost:8000/issuer/ \
  -H "X-Tenant-ID: 1" \
  -H "Authorization: Bearer YOUR_JWT_TOKEN"

​
Example Response

{
  "id": 1,
  "rut": "76123456-7",
  "razon_social": "Mi Tienda SpA",
  "giro": "Venta al por menor de productos alimenticios",
  "acteco": "522900",
  "direccion": "Av. Providencia 1234",
  "comuna": "Providencia",
  "ciudad": "Santiago",
  "telefono": "+56 2 2345 6789",
  "email": "[email protected]",
  "website": "https://mitienda.cl"
}

​
Error Responses

{
  "detail": "Emisor no configurado. Use PUT /issuer/ para registrarlo."
}
This error occurs when no issuer has been configured for the tenant. Use the PUT endpoint to create the initial configuration.

​
Configure Issuer

​
Request Body

​
rut
string
required
Chilean RUT (tax ID) of the company in format XX.XXX.XXX-X
​
razon_social
string
required
Legal business name
​
giro
string
Line of business description
​
acteco
string
Primary ACTECO economic activity code
​
direccion
string
Street address
​
comuna
string
Municipality/commune
​
ciudad
string
City
​
telefono
string
Contact phone number
​
email
string
Contact email address
​
website
string
Company website URL

​
Example Request

cURL
curl -X PUT http://localhost:8000/issuer/ \
  -H "X-Tenant-ID: 1" \
  -H "Authorization: Bearer YOUR_JWT_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "rut": "76123456-7",
    "razon_social": "Mi Tienda SpA",
    "giro": "Venta al por menor de productos alimenticios",
    "acteco": "522900",
    "direccion": "Av. Providencia 1234",
    "comuna": "Providencia",
    "ciudad": "Santiago",
    "telefono": "+56 2 2345 6789",
    "email": "[email protected]",
    "website": "https://mitienda.cl"
  }'

​
Example Response

{
  "id": 1,
  "rut": "76123456-7",
  "razon_social": "Mi Tienda SpA",
  "giro": "Venta al por menor de productos alimenticios",
  "acteco": "522900",
  "direccion": "Av. Providencia 1234",
  "comuna": "Providencia",
  "ciudad": "Santiago",
  "telefono": "+56 2 2345 6789",
  "email": "[email protected]",
  "website": "https://mitienda.cl"
}

​
How Issuer Data is Used

The issuer configuration is automatically included in all DTE (electronic tax documents) generated by the system:
  • Invoices (DTE 33) - Issuer information appears in the document header
  • Receipts (DTE 39) - Company details printed on receipts
  • Credit/Debit Notes - Referenced in document metadata
  • SII Submissions - Issuer RUT used for authentication and document signing
When you update the issuer via the global tenant management API (PATCH /saas/tenants/{id}), the system automatically synchronizes changes to the local issuer table for that tenant’s schema.

​
Tenant Synchronization

The issuer data is synchronized between two locations:
  1. Global tenant record (public.tenants table) - Master data
  2. Local issuer record ({tenant_schema}.issuers table) - Used for DTE generation
When you update a tenant’s business information through the SaaS API, the system automatically updates the corresponding issuer record. This ensures DTE generation always uses the latest company information.

​
Best Practices

1

Configure during tenant provisioning

Set up issuer information immediately after creating a new tenant. This ensures all DTEs have correct company information from the start.
2

Validate RUT format

Ensure the RUT follows Chilean format with verification digit (XX.XXX.XXX-X). Invalid RUTs will cause SII submission errors.
3

Use official ACTECO codes

Reference the official SII ACTECO catalog. You can search codes using GET /saas/actecos?q=search_term.
4

Keep information current

Update issuer data whenever company information changes to maintain DTE compliance.

Tenants

Manage tenant provisioning

Sales

Generate DTEs with issuer info

Build docs developers (and LLMs) love

Get started for freeTalk to us