Puente Factura
Back to Puente

DOCUMENTATION · INITIAL OVERVIEW

One API. The whole journey.

We’re building our own Dominican electronic invoicing infrastructure. The business dashboard, accountant workspace and integrations share the same core.

The platform is in development. This guide describes the product direction and local proof. There is no public production API or fiscal issuance available yet.

Start with the way you work

Business

Prepare drafts, invite your accountant and review each invoice before continuing. Fiscal status, delivery and payment are tracked separately.

Accountant

Work with businesses that have granted you access. Review documents and outstanding work within each client’s context.

Developer

Integrate the same journey from your software. The design includes business-scoped permissions, validation, tracking and document retrieval.

LOCAL EXAMPLE · FICTIONAL DATA

Start with one request.

Customer and line items together. Amounts are calculated on the server and the initial result is a draft to review.

Send a unique Idempotency-Key and keep the same key for retries.

For one-step test issuance, action: issue requires approvalTotal matching the exact amount you authorized. Signing and the result are tracked on the original operation.

POST /api/v1/invoices
{
  "mode": "test",
  "issuerId": "empresa-a",
  "externalId": "venta-ejemplo-001",
  "action": "draft",
  "customer": {
    "name": "Cliente Ficticio",
    "taxId": "DEMO-EJEMPLO",
    "email": "cliente@ejemplo.test"
  },
  "items": [
    {
      "description": "Servicio ficticio",
      "unitPrice": "1000.00",
      "tax": 18
    }
  ],
  "dueDate": "2026-11-01"
}

The local contract today

These routes belong to the local proof with fictional data. They are a working reference, not public endpoints or a stable production contract.

POST/api/v1/invoices

Customer and line items in one request

POST/api/invoices/{id}/review

Request review

POST/api/invoices/{id}/approve

Approve a version

POST/api/invoices/{id}/submit

Start simulated issuance

GET/api/operations/{id}

Check the result

GET/api/invoices/{id}/documents/{format}

Retrieve the test document

GET/api/webhooks

Inspect events and deliveries

POST/api/webhooks

Pause, resume or replay an event

An interruption should not mean starting over.

In the local proof, events are stored with the invoice change. Three failed deliveries pause the connection; resume or replay retains the same event. Delivery may repeat: the receiver must deduplicate by ID.

event.created→retry→paused→replay

What should be clear from the first integration

01

Access per business

Each person or integration needs permission for the business they work with. Signing in does not grant access to every invoice.

02

Retries without duplicates

The local proof uses an idempotency key and an approved version when requesting issuance. A pending response is checked before repeating the operation.

03

States that explain what happened

A received request, fiscal acceptance, delivery and payment are distinct events. Puente keeps them separate.

04

Documents and history

The goal is to retain original documents and results, link corrections and make information easy to retrieve.

What remains before public access

Complete and verify the fiscal engine, direct DGII connection, operating requirements, public test environment and stable documentation. Local tests do not establish fiscal authorization.

Want to integrate Puente?

Tell us what software you develop and which workflow you need to support.

Discuss an integration
Puente Factura · A Super Intelligence Group product, developed by Applied SI.@puente.factura