Download the PHP package facta-dte/api without Composer

Facta DTE API client for PHP

PHP client for the Facta DTE API, El Salvador's electronic invoicing service. It talks to the API over HTTPS; it never signs a document and never computes tax. Signing, totals, IVA, correlatives and validation happen on the server.

Status: tier 1 (0.2.0-rc.3 is a release candidate; 0.1.0 is the stable release). Everything that needs only HTTP is implemented: issuing, prepare/sign, queries, downloads, invalidation, returns, delivery, managed storage, the catalog, the catalogue changes feed and webhooks (see Methods). The catalogue is always read through the API, also when the company keeps it encrypted and shares its data key with your API key. What needs local storage is not there yet: BYOS destinations and the restart-safe archive.

• Package: facta-dte/api, namespace Facta\Api, MIT licence.
• PHP 7.4 or later, clean on 8.0 to 8.5 (no deprecation notices).
• No required dependency and no required extension beyond PHP core (json, hash). ext-curl is used when present; otherwise PHP streams (allow_url_fopen, plus ext-openssl for HTTPS). A PSR-18 client can be injected.
• TLS verification is never disabled.

Install

With Composer

Without Composer (ZIP, FTP, cPanel)

Download facta-api-php-vX.Y.Z.zip from the GitHub Release, unzip it and upload the facta-api-php/ folder next to your script (or anywhere PHP can read):

No Composer, no extension to install. If you only have Composer on another machine, run composer require facta-dte/api there and upload the generated vendor/ folder.

Use

The server computes every amount, signs and transmits; the SDK only sends your request. Answers come back as plain associative arrays with the API's own field names and estado values. Requests are PHP arrays too: a list becomes a JSON array, an associative array a JSON object, and new \stdClass() is an empty object {}.

Discounts, several payments, VAT class and warnings

Facta::PRODUCTION_BASE_URL names the production endpoint and is the same value as the backward-compatible Facta::DEFAULT_BASE_URL. The client uses production by default; set baseUrl to Facta::STAGING_BASE_URL to opt in to staging, or provide a custom absolute HTTP(S) URL.

• montoDescu is the discount of one line in money, in the same VAT basis as precioUni.
• pagos takes 1 to 10 rows (01, 03, 11, 14), not together with formaPago, not on 05/06, not on credit. Pago is optional: plain arrays work too.
• tipoVenta (gravada default, exenta, no_sujeta) is yours to choose and valid in 01, 03, 05, 06.
• Unknown fields are always a warning, never an error. A request field Facta DTE does not know is ignored and is not part of the document; the answer says so in advertencias (campo_desconocido, with campo and sugerencia). The SDK also lists them in unknownFields and parses the Facta-Warning header into factaWarning (['code' => ..., 'count' => ...]), on issue(), prepare(), sign() and issueDraft(), only when there is something to report. On a failure, FactaError::getUnknownFields() and getFactaWarning() read them. Check the first answer of your integration: an ignored field is a discount or a payment the document does not carry.

Methods

Per-call options accepted by every method: timeoutMs, headers; the writing ones also idempotencyKey. An unknown option throws InvalidArgumentException, so a typo is not silently ignored.

The temporary copy and the storage confirmation

Facta keeps an encrypted temporary copy of every sealed document. It is a safety net, not your archive: it is deleted 2 days after the document is marked as stored, or 30 days after sealing if nobody marks it. The company owner is mailed from day one (production only). Once it is gone, reads that depended on it answer temporary_copy_expired (410), and retryDocumentStorage() answers nothing_to_repair_from (409). Look in your own storage.

Store the JSON where you keep your books and say so. The simplest way is to let the SDK drain the list daily:

Or confirm one document yourself, with the hash of the bytes you stored:

A document issued by the API is checked against the file Facta can rebuild (verificado => true; a wrong hash is storage_hash_mismatch (422) and nothing is recorded). One issued from the app cannot be checked and is kept as informado => true. Confirming twice is safe (yaConfirmado => true). A server that does not advertise capabilities.storageConfirmation makes confirmDocumentStorage() throw storage_unsupported without posting anything; such a server deletes no temporary copy.

Idempotency and retries

issue() mints one Idempotency-Key per call (or uses yours) and every retry resends the same bytes with the same key. Since 0.2.0 the SDK no longer sends X-Facta-Request-Fingerprint: it does not rewrite your request any more, so the server's own idempotency claim hashes the body.

prepare / sign

prepare() returns the plain members of the answer as an array, but documento is the decoded \stdClass tree, on purpose: an empty object {} inside it must not turn into [] when it goes back to sign(). Pass the array to sign() unchanged. If you store it between the two calls, use json_encode and json_decode($text) (objects), never json_decode($text, true).

Catalog references

customerId / productId in a request travel untouched and the server resolves them, in every catalogue mode (plain, readable, or encrypted at rest and shared with the key). An id that does not exist (or is deactivated) is not_found with details.reason catalog_unknown_id. Reads (listCustomers(), getProduct(), ...) always call the API; no unlockKey is needed.

Editing with a revision

On a company that shares its data key, a record you read carries revision. Pass it back as ifMatch to apply the edit only if nobody changed the record meanwhile; otherwise you get catalog_revision_conflict and details->revisionActual:

Without ifMatch the last write wins per field you send.

Changes feed and webhooks

A webhook is a hint to read, never the data (ids, a revision and a timestamp). Verify the RAW body with the secret you got once from createWebhook():

The retired sealed inbox (POST /v1/catalog/changes and /v1/catalog/changes/{id}) answers 410 inbox_retired.

Drafts

A draft is an invoice your program leaves for a person of the company to review and issue in the Facta DTE app. No control number is spent until somebody issues it (or you do, with issueDraft()). Bodies and answers use the API's own member names.

drafts_not_ready (409): the owner has not opened Facta with their vault since the company began sharing its data key; ask them to open it once and repeat. version_mismatch, draft_claimed, draft_issuing, draft_issued, draft_not_issuable, item_final (409) are about the draft's state and are never retried (draft_issuing / draft_claimed spent nothing).

Production keys and companies still in test

A production key (facta_live_) is refused with environment_not_allowed (403) on emission and on the company-level routes (customers, products, webhooks, the change feed, drafts, destinations, templates) while the company is still in the test environment; a test key is always allowed. A read-only key hears forbidden_scope before catalog_encrypted, and details.hint of catalog_encrypted says whether the key lacks access to the shared data or the catalogue is not shared.

Options

Errors and retries

Every failure is a Facta\Api\FactaError. Branch on getErrorCode() (the strings are the same as in the TypeScript SDK: mh_rejected, validation_failed, idempotency_key_reuse, network_error, ...), never on the message. The client retries exactly the codes the TypeScript SDK retries: idempotency_in_flight, mh_unreachable, service_unavailable, correlative_unavailable, storage_unavailable, data_grant_unavailable, data_epoch_stale and network_error (a connection failure or timeout), up to maxRetries extra attempts, waiting for Retry-After when the server sends it. Every attempt resends the same bytes with the same Idempotency-Key, so a retry cannot issue twice. When the attempts run out the last error is thrown; any other code is final.

Secrets (API key, sign key, unlock key) are removed from messages and details.

Old servers and TLS

If HTTPS fails because the server's certificate store is outdated, pass the path of a current CA bundle (for example the one published by curl) in caBundle. Verification is never turned off.

Fingerprint and JSON helpers

Facta\Api\Json\Jcs is a dependency-free RFC 8785 implementation (numbers follow ECMAScript Number::toString, independent of serialize_precision; keys sort by UTF-16 code units). It is validated against the conformance vectors shared with the TypeScript SDK.

Live test against staging

.github/workflows/sdk-live-integration.yml ("PHP SDK live integration (staging API, test environment)") runs php scripts/live-integration.php against the staging API in environment 00 on every pull request that is ready for review, and by hand (workflow_dispatch: emit-test-fe, or emit-enabled-dte-fixtures). It issues one FE of $0.01 (more with the fixture matrix), replays it, queries and lists it, downloads the Archivo DTE, PDF and ticket, checks the managed copies byte for byte and, if an inbox is configured, the e-mail delivery. The result is a sticky comment on the pull request ("PHP SDK staging live test"). Steps that need local storage are listed as "Not in this SDK version".

Configuration, in the repository's staging-live-test environment (or as organization secrets with the same names):

The API URL is fixed in the workflow. If a secret is missing the run fails with "Required integration input is unavailable: NAME"; it never passes silently. The guards (test key, exact staging URL, known mode, run younger than the 22 h idempotency window) and the report renderer are covered by offline unit tests, and the whole script is exercised against a fake API.

Development

See CLAUDE.md for the rules of this repository.

En español

Cliente PHP para la API de Facta DTE (facturación electrónica de El Salvador). No firma ni calcula impuestos: eso lo hace el servidor.

• Requisitos: PHP 7.4 o superior. No necesita extensiones especiales ni dependencias; usa curl si está disponible y, si no, los flujos nativos de PHP.
• Con Composer: composer require facta-dte/api y require 'vendor/autoload.php';.
• Sin Composer (hosting compartido, cPanel, FTP): descargue facta-api-php-vX.Y.Z.zip de la página de versiones, descomprímalo, suba la carpeta facta-api-php/ y use require_once 'facta-api-php/autoload.php';.
• Estado: nivel 1. Todo lo que solo necesita HTTP está implementado: emitir (issue(), prepare()/sign()), consultar, descargar el Archivo DTE y el PDF, invalidar, eventos de retorno, envío por correo y WhatsApp, almacenamiento de Facta y catálogo. Aún no están los destinos propios (BYOS) ni el archivo local: necesitan la clave de desbloqueo y llegan en una versión posterior. Desde 0.2.0 el catálogo se lee siempre por el API (también cifrado y compartido con su llave), customerId/productId los resuelve el servidor, y hay lectura de cambios (listCatalogChanges) y webhooks con verificación de firma.
• Copia temporal: Facta guarda una copia temporal cifrada de cada documento sellado y la borra 2 días después de que usted lo marque como guardado, o 30 días después de sellarlo si nadie lo marca. Guarde el JSON en su almacenamiento y avise con confirmDocumentStorage(), o deje que storeAndConfirmUnconfirmed() lo haga cada día con su función store. listUnconfirmedDocuments() muestra qué falta y cuándo se borra.
• Prueba en vivo: el flujo de GitHub Actions sdk-live-integration.yml emite una factura de prueba de $0.01 en el ambiente 00 del API de staging en cada pull request listo para revisión. Usa los secretos STAGING_FACTA_API_KEY, STAGING_FACTA_SIGN_KEY y STAGING_FACTA_UNLOCK_KEY (opcionales: STAGING_FACTA_DTE_FIXTURES_JSON y STAGING_FACTA_DELIVERY_EMAIL) del entorno staging-live-test; si falta uno, la ejecución falla en lugar de pasar en silencio.
• Si el servidor tiene certificados desactualizados, indique la ruta de un paquete de certificados en la opción caBundle. La verificación TLS nunca se desactiva.

Licence

MIT. See LICENSE.