Connector · REST
Connect to any API, from any flow.
ERP, carrier, bank or government portal — if it has an API, phaf can call it. Authenticate, map, send and read the response, without writing code.
Base URL
https://api.acme-erp.example/v2
Authentication
Bearer token
Token
•••••••• (vault)
Operation
POST /invoices
How it connects
A few settings and you're connected.
Base URL
Any HTTP or HTTPS endpoint — in the cloud or on your own network.
Authentication
API key, Basic or Bearer token, with OAuth 2.0 in development. Secrets stay encrypted in the phaf vault.
Method and path
GET, POST, PUT, PATCH or DELETE on any path, with headers and query parameters, then map the fields.
Operations
Every HTTP call, as a connector action.
| phaf action | API request | What it does |
|---|---|---|
| Query | GET /resource?filter&page | Bring records into the flow, with filters and paging. |
| Lookup | GET /resource/{id} | Enrich a message with one record, such as the customer. |
| Create | POST /resource | Create documents and master records. |
| Update | PUT | PATCH /resource/{id} | Change only the fields you mapped. |
| Upsert | GET → POST | PATCH | Checks whether it exists and decides on its own. |
| Delete | DELETE /resource/{id} | Remove records the API allows you to delete. |
| Call action | POST /any/endpoint | Run any operation the REST API exposes. |
| Receive | Webhook → phaf | Let the API push events into a flow (in development). |
Examples
Any API, through one connector.
The APIs below are fictional — they show the kinds of systems and calls phaf handles.
Customers, invoices and stock in a cloud ERP.
GET /v2/customers?status=active&page=2
Goods receipts, stock levels and dispatch confirmations.
POST /v1/receipts { "sku": "SKU-10045", "qty": 120 }
Vehicle positions, trips and fuel readings.
GET /fleet/vehicles/TRK-042/positions?since=2026-10-26
Payment requests, refunds and settlement reports.
POST /payments { "amount": 12500, "currency": "USD" }
Bookings, shipping labels and tracking.
POST /shipments { "origin": "WAW", "weightKg": 12.5 }
Submit invoices to a tax authority and get the validation code.
POST /einvoices/submit → { "validationCode": "…" }
Employees, payroll deductions and leave.
GET /employees?updatedSince=2026-10-01
Warehouse stock levels and movements.
PATCH /items/SKU-889 { "onHand": 140 }
Account balances and daily bank statements.
GET /accounts/ACC-01/statements?date=2026-10-26
Request & response
See what was sent and what the API replied.
Every request is stored with the transaction. Errors appear as readable text.
{
"customerId": "C-1001",
"currency": "USD",
"lines": [
{ "sku": "STORAGE-20FT", "qty": 3 }
]
}
Fictional APIs, shown as examples.
Reliability
Retries what it should. Stops where it must.
Retry with backoff
Timeouts, rate limits (429) or 5xx errors: it tries again, waiting longer each time.
Data errors stop
If the API rejects the data, the message goes to the error path.
Paging handled
Follows next-page links and cursors until every record is read.
Full trail
Request, response, attempts and timing for every call.
On the canvas
Any source, any API as the target.
Database, file, EDI or another API — map to the endpoint and send.
EDI
EDIFACT
TRANSFORM
Map_To_JSON
REST API
ERP_CreateOrder
Illustrative example.
Bring the API you need to connect.
We'll call it live from phaf in the demo.