Skip to Content
GOTHAM ECF · API

Your system. Your invoices. One connection.

Connect your application to Gotham ECF, validate invoices, and follow their results. Start in Sandbox with your company credentials.

Examples in Python, JavaScript, PHP, cURL, C#, Java, and Go.

Connect in three stages

01

Prepare access

Request the company’s Sandbox username and token. Use the token from your server; the portal password is separate.

02

Validate a sample

Send JSON or XML containing invoice data and a test e-NCF. Review errors, simulate submission, and download XML, PDF, and responses.

03

Review and enable

Arrange the approved connector installation and review Certification or Production requirements. Changing a token alone does not enable live issuance.

Separate environments, verifiable results

https://gotham.felizhosting.net/api/sandbox/v1

Sandbox validates and simulates without sending to DGII or consuming production numbering. Certification uses authorized tests. Production requires review, a certificate, and an enabled connector; generic public API submission remains locked.

HTTP 200 or a TrackId does not prove acceptance. Retain the document, DGII response, signed XML, and PDF. Check the existing document before retrying a submission.

Good practices from the first request

  • Use HTTPS and a separate token for each company and environment. Never place it in links, public code, or browser applications.
  • Use a stable Idempotency-Key: preserve the key and identical bytes when recovering a creation to avoid duplicates.
  • General limit: 120 requests per minute per company and environment. On 429, honor Retry-After; do not poll in a continuous loop.
  • Upload the .p12 certificate and its password through the authorized private form, never in JSON samples or on this page.
  • Before production, verify totals, identity, invoice types, sequences, permissions, and error recovery.