Turn your e-OSCAR worklist into an API

What you can build on e-OSCAR

• Get ACDVs from the worklist

  Build this

  Reads the open ACDVs on the Data Furnisher Worklist, with each case's dispute code and Response Due Date.

  Takes

  Subscriber code (optional), due within N days (optional)

  Returns

  ACDV control number, case ID, subscriber code, account number, dispute code, response due date

• Get Block and DR Notifications

  Build this

  Reads the Block and Dispute Response (DR) Notifications received in a date range, with who performed each one.

  Takes

  Notification type, received from date, received to date

  Returns

  Control number, case ID, notification type, account number, received date, performed by

• Read the AUD archive for a date range

  Build this

  Reads the AUD Archive report for AUDs your registration submitted between two dates, with the DF Authorized Name on each.

  Takes

  Submitted from date, submitted to date

  Returns

  AUD control number, case ID, subscriber code, account number, submitted date, DF authorized name

• Submit an ACDV response

  Build this

  Opens one ACDV by control number, enters the response code and the account data you give, and submits the response.

  Takes

  ACDV control number, response code, updated account fields

  Returns

  ACDV control number, response code, submitted by, status

Automate e-OSCAR with a workflow

A workflow runs your methods as one process, with nobody at the screen. A schedule or a call from your own system starts it, the steps run in order, and the result arrives in your inbox or in the systems you already use.

• ACDVs within 5 days of their Response Due Date

  Build this

  Starts

  Every weekday at 7:00 Eastern Time

  Step 1

  Get the ACDVs on the Data Furnisher Worklist due within the next 5 days.

  Step 2

  Stop when there are none.

  Step 3

  Email you the list sorted by Response Due Date, with control number, dispute code and account number.

• New Block and DR Notifications, to your servicing system

  Build this

  Starts

  Every day at 8:00 Eastern Time

  Step 1

  Get the Block and DR Notifications received since yesterday.

  Step 2

  Keep the notifications that were not there on the last run.

  Step 3

  Post each one, with control number, type, account number and received date, to your webhook.

• Weekly AUD summary for compliance review

  Build this

  Starts

  Every Monday at 9:00 Eastern Time

  Step 1

  Read the AUD archive for the previous seven days.

  Step 2

  Group the AUDs by DF Authorized Name and subscriber code, with a count for each.

  Step 3

  Email you the summary with the full list below it.

You can run a workflow by hand on every plan, Free included. Schedules and webhook triggers come with the paid plans, from $29 a month.

Once built, one call from your code

Once you have built a method, it is one POST to /v1/runs from your backend, or a tool an AI agent calls over MCP. This is what “Get ACDVs from the worklist” would look like.

curl https://api.fous.com/v1/runs \
  -H "Authorization: Bearer $FOUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "e-oscar-web.net/get_acdv_worklist",
    "input": {
      "subscriber_code": "1234567",
      "due_within_days": 5
    }
  }'

{
  "status": "completed",
  "data": {
    "acdvs": [
      {
        "control_number": "A0000418273",
        "case_id": "CS-2026-0091842",
        "subscriber_code": "1234567",
        "account_number": "XXXXXX4821",
        "dispute_code": "001",
        "response_due_date": "2026-11-15"
      }
    ],
    "count": 1
  }
}

An example with invented data, not a ready-made endpoint. The method exists in your organization once you build it, and its name, inputs and fields follow your request.

E-OSCAR’s own options

Online Data Exchange offers Services by e-OSCAR, an API that receives ACDVs, submits ACDV responses, AUDs and BRRs, and reads archives and notifications. It needs a contract, a one-time setup fee and a monthly API service fee by usage tier, and many data furnishers connect through a middleware vendor. Everyone else works in the e-OSCAR web application.

Read on November 12, 2026: Services by e-OSCAR, e-OSCAR release notes, Getting started with e-OSCAR.

Signing in to e-OSCAR

Operators sign in to the e-OSCAR web application at e-oscar-web.net. A registration can switch on single sign-on through Okta or Azure Entra ID, and it then applies to every operator on that registration. With Fous you sign in once through e-OSCAR's own sign-in with your own operator account: the login is sealed with AES-256, and an expired session is signed back in.

Worth knowing

Email notices carry no case detail

The DNR Notice arrives once a day at 1:00 a.m. ET, 5 days before ACDVs are due, with no case detail such as control numbers. e-OSCAR says each company remains responsible for accessing the system regularly.

Viewing an ACDV through the API changes it

In Services by e-OSCAR, View ACDVRequest moves an ACDV from status 4 to 6 and marks its images as accessed. The archive call Get ACDVRequest reads the same ACDV without changing its status.

AUDs are for out-of-cycle corrections

An AUD corrects a consumer's file between regular reporting cycles. It may not be used to add or create a record, or in place of your in-cycle Metro 2 reporting.

Single sign-on is set for the whole registration

SSO covers every operator on a registration, costs a one-time $2,500 professional services fee and has no usage fees. e-OSCAR does not support SCIM provisioning.

More in Finance: payments, cards and lending

• U.S. Bank Access Online
• CareCredit Provider Center
• Synchrony Business Center
• Comdata iConnectData
• WEX Online
• NextGear Capital Account Portal
• Elavon Payments Insider
• Moneris Merchant Direct
• Portal Rede
• Site Cielo
• Worldpay iQ
• CAFS
• Paymode-X

Other industries: Edabu, EPFO Unified Portal (Employer), Travelport Smartpoint, ARCA - servicios con Clave Fiscal, eTIMS, EU Funding & Tenders Portal.