Overview
Submit supported master and transaction payloads and inspect per-record results.
Before you begin
An operator must enable external capabilities, provision a valid integration token, and allow the target subsidiary. API authorization uses X-Integration-Token; a browser login does not substitute for it. Guest demos disable these APIs.
Main task
- Choose the subsidiary reference and supported injection endpoint.
- Send JSON with Content-Type: application/json and the X-Integration-Token header over HTTPS.
- Use stable external identities and valid assigned reference values; customer payloads require internalid or entityid and a company/personal name.
- Inspect the returned status and result for each record. Supported bulk envelopes/arrays can contain individual failures.
- Review Integration Monitoring and correct validation errors before retrying known failed records.
Check the result
Injected data follows the supported module service and subsidiary eligibility rules. An HTTP response alone is not evidence that every member of a bulk request succeeded.
If something goes wrong
403 indicates forbidden access, including token or capability restrictions. Other validation errors report invalid payload/reference data. A lost response should trigger identity/status review before retrying; do not assume uniform idempotency across all modules.
Supported endpoints
All paths begin with /api/integrations/subsidiaries/{subsidiary_ref}/ and use POST.
| Suffix | Purpose |
|---|---|
| customer-injection | Customer identity and assignment |
| vendor-injection | Vendor/employee identity payloads supported by the importer |
| bill-injection | Vendor bill input |
| expense-report-injection | Employee expense input |
| invoice-injection | Customer invoice input |
| bill-payment-injection | Vendor payment input |
Fictional customer request
Replace example.invalid with your ERP host, EXAMPLE-COMPANY with an allowed subsidiary reference, and the token placeholder with the privately supplied token. The example company must exist and be eligible in your instance; this request is not a universal seed operation.
POST /api/integrations/subsidiaries/EXAMPLE-COMPANY/customer-injection HTTP/1.1
Host: example.invalid
Content-Type: application/json
X-Integration-Token: YOUR_PRIVATE_TOKEN
{
"internalid": "EXAMPLE-CUSTOMER-100",
"entityid": "EXAMPLE-RETAIL",
"companyname": "Example Retail",
"isperson": false,
"subsidiary_name": "Example Company"
}
Customers accept a JSON array or a customers-array envelope for supported bulk input. Module-specific transaction payloads have different required header/line fields; use the configured integration mapping and inspect validation results before sending real financial data.