Third-Party API Sync
Pull invoices, receipts, and items from vendor APIs through the EGKits sync proxy — vendor contract and provider configuration.
Where do I configure providers?
Third-party providers are registered from your tenant workspace under Settings → Third-Party API Integrations. Calls to the sync proxy authenticate with a Migration API key created under Settings → Migration API Keys.
How It Works
LegacyMigrator → EGKits sync proxy (/api/v1/migration/third-party-apis) → your vendor API
Register the vendor API (base URL, credentials, endpoints). Credentials are encrypted server-side and never returned — only a tp_****xxxx fingerprint is shown.
EGKits then pulls data from the vendor on demand and returns normalized batches to the caller.
Calls to the sync proxy authenticate with a Migration API key (egk_mig_*) in X-Api-Key (or Authorization: MigrationKey <key>).
Rate limit: 120 requests/minute per key. Use the Test action on a provider card to validate connectivity before syncing.
Quick test (cURL / Postman)
curl "https://<your-server>/api/v1/migration/third-party-apis" \
-H "X-Api-Key: egk_mig_4f2a91c07d3e.q8PzR5tWvYxA1bC3dE6fG9hJ2kM4nP7sT0uVwXyZabc"
Error envelope
TPA_VAL_001 (400) — provider disabled, endpoint not enabled, or bad parameters. TPA_HTTP_001 (502) — the vendor API call failed.
{
"errorCode": "TPA_VAL_001",
"category": "validation",
"reason": "Provider is disabled or the Invoice endpoint is not enabled."
}