generated: '2026-07-20'
method: searched
source: https://www.replicon.com/help/api-concepts/
docs:
  concepts: https://learning.deltek.com/bundle/Replicon/page/api-concepts.html
  filtering: https://www.replicon.com/help/filtering-data-with-the-api/
  errors: https://www.replicon.com/help/understanding-error-responses/
authentication:
  style: token (Api-token header) or HTTP Basic
  see: authentication/replicon-authentication.yml
transport:
  protocol: JSON over HTTPS
  style: operation/service endpoints (RPC-style), not resource REST
  spec: none published (no public OpenAPI/Swagger)
endpoint_discovery:
  swimlane: >-
    An instance's swimlane is the three characters preceding .replicon.com in
    its URL (e.g. sb1, na7, eu1). Resolve the tenant's swimlane via the global
    discovery service before calling service endpoints.
  discovery_service: https://global.replicon.com/DiscoveryService1.svc/GetTenantEndpointDetails
filtering:
  supported: true
  notes: The API supports filtering result sets; see the filtering-data-with-the-api guide.
idempotency:
  supported: false
  notes: >-
    Replicon does not document a client-supplied idempotency-key header. Some
    write operations accept a caller-generated Unit Of Work Id, but no
    published idempotent-retry contract exists.
error_envelope:
  root: error
  see: errors/replicon-error-codes.yml
request_tracing:
  correlation_id: Errors return error.correlationId for support tracing.
versioning:
  see: lifecycle/replicon-lifecycle.yml