Qintorava DocsProduct documentation
Integration profile

ERP integration · GENERIC API

Provider REST API integration with an explicit request/response mapping. A provider-specific API schema or approved adapter is required; selecting a product does not configure its API.

Demo baseline · November 13, 2026
Download PDF

Prerequisites

  • Protected HTTPS provider API
  • Secret Manager credential
  • Provider-approved purchase-order payload and response reference mapping

Configuration steps

  1. Configure a protected read-only test path
  2. Map purchase-order fields to the provider schema
  3. Run the real authenticated API test
  4. Submit an approved test order and reconcile its returned provider reference

Provider fields

FieldTypeRequirement and options
Authentication scheme
authScheme		selectRequired
bearer_token, api_key, basic, oauth2_client_credentials
Protected read-only API test path
testPath		textRequired
Purchase-order API path
submissionPath		textRequired
Provider reference response path
referencePath		textRequired
Dot-separated JSON path, for example data.orderNumber.
Read-only order lookup
reconciliationPath		textOptional
Optional HTTPS same-origin GET path. Include {orderId} in the path or query; it is replaced with the original idempotency key.
Response request key
reconciliationKeyPath		textOptional
Dot-separated path to the original request ID in the response. It must match exactly to confirm the delivery.
Provider request JSON mapping
requestTemplate		textareaRequired
JSON values can reference {{order.number}}, {{order.quantity}}, {{order.unitCost}}, {{order.currency}}, {{model.modelNumber}} and other saved order/model fields.
API-key header name
apiKeyHeader		textOptional
OAuth token URL
tokenUrl		urlOptional
OAuth scopes
scope		textOptional

Verify and troubleshoot

Test with the narrowest supported non-production scope. Confirm that the connection test reaches the expected provider and that the preview or receipt matches the intended scope. Check identity, credential references, network access and provider permissions before retrying. Record the failure stage and redact sensitive payloads when escalating.