ALalfredpay
Onboarding

Answer an RFI

Changed on

Send fields keyed by the names in that RFI's own requirements[], plus any documentIds from an earlier upload. The RFI moves to RECEIVED.

Works the same way for onboarding RFIs and transaction RFIs.

Wait on rfi.updated. See Webhooks and events.

post/v1/rfis/{rfiId}/evidence

Request

  • Base URL
    https://api.sandbox.alfredpay.io
  • URL
    https://api.sandbox.alfredpay.io/v1/rfis/{rfiId}/evidence
  • Auth
    • HTTP bearer
    • or API key in header api-key and API key in header api-secret

Headers

Idempotency-Keystring uuid required

Required on every state-changing POST, simulators included; the only exempt POST is …/verifications/preflight. Replay (same key, same body) returns the original response with Idempotent-Replayed: true; same key with a different body → 409 idempotency_conflict. Keys are UUIDs, scoped to the API key, retained for 24 hours.

Request body

fieldsobject
documentIdsstring[]

Response

OK

idstring
status'OPEN' | 'WAITING_ON_CUSTOMER' | 'WAITING_ON_PARTNER' | 'RECEIVED' | 'RESOLVED' | 'OVERDUE' | 'REJECTED'
requirementsstring[]
rfi_owner'CUSTOMER' | 'PARTNER'
rfi_slastring date-time

When this becomes OVERDUE. A missed SLA is a blocking condition.

openedAtstring date-time

Changes