REST (BasicIntegrationApi) and optional e-Dispatch (DespatchApi)
Última actualización: Última actualización: 13 de julio de 2026
Convord talks to Uyumsoft using JSON requests to BasicIntegrationApi for e-Invoice / e-Archive and, optionally, DespatchApi for e-Waybill. Authentication matches the official samples: each request includes userInfo with Username and Password. There is no OAuth flow or separate API key; what you enter in the dashboard is exactly that pair.
The integration uses the REST userInfo object. The two fields in Convord map to Username and Password. There is no extra Bearer token or secret-key field.
Optionally set UYUMSOFT_USERNAME / UYUMSOFT_PASSWORD in the server .env as a tenant-wide fallback; company-specific values in the dashboard take precedence when present.
Hosting / DevOps should verify:
https://efatura.uyumsoft.com.tr/api or test https://efatura-test.uyumsoft.com.tr/api (combined with path settings in config).UYUMSOFT_INVOICE_API_URL, UYUMSOFT_DESPATCH_API_URL.php artisan uyumsoft:testA valid buyer tax ID is required for Uyumsoft submission. Convord validates before create/send and shows an explicit error; update the customer record and retry.
Local PDF/XML waybill mode does not require extra server flags. Real Uyumsoft / GİB e-waybill needs:
EINVOICE_PROVIDER=uyumsoftUYUMSOFT_DISPATCH_ENABLED=true — buyer VKN/TCKN is also required in this mode.Even with correct API wiring, your Uyumsoft project must have invoice <strong>series / prefix</strong> and account settings completed. Otherwise you may see errors such as missing series. Contact Uyumsoft support for account setup.
Use Uyumsoft documentation for test URLs and sample credentials. The uyumsoft:test Artisan command smoke-tests BasicIntegrationApi connectivity.
For broader integration context, see the Integration guide.