Filify API Documentation

Programmatic access to Filify's trade execution layer — escrow state, KYC status, and compliance checks — so your systems stay in sync with the trade pipeline.

Authentication

All requests authenticate with an API key sent as a Bearer token. Keys are issued per integration from the Master Console and are rate-limited to 60 requests per minute.

Authentication header

curl https://api.filify.io/api/v1/trades \
  -H "Authorization: Bearer YOUR_API_KEY"

Endpoints

GET/api/v1/tradesList your trades with pipeline step, escrow state, and timestamps.

GET/api/v1/trades/:idFull trade detail including documents, audit log, and sync state.

POST/api/v1/trades/:id/escrow/fundInitiate Tazapay escrow funding for the contract's FOB value.

GET/api/v1/kyc/statusCurrent KYC/KYB verification status for your organization.

POST/api/v1/compliance/phytocheckRun a PhytoCheck AI validation for a commodity and destination port.

POST/api/v1/documents/verifySubmit an export document for AI Doc Verifier OCR cross-checks.

Example Request

Run a PhytoCheck AI validation

curl -X POST https://api.filify.io/api/v1/compliance/phytocheck \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "commodity": "dried_hibiscus",
    "hs_code": "1211.90",
    "origin": "NG",
    "destination_port": "ROTTERDAM"
  }'

# 200 OK
{
  "check_id": "phc_9f2e41",
  "status": "compliant",
  "readiness_score": 98,
  "required_treatments": ["fumigation"],
  "valid_until": "2026-12-14T00:00:00Z"
}

Webhooks

Subscribe to trade events — escrow.funded, inspection.verified, escrow.released — and Filify will POST signed payloads to your endpoint. Verify the X-Filify-Signature header (HMAC-SHA256) before processing.

API access is enabled per account. Contact your trade operations manager or reach us from the Master Console to have keys issued for your integration.