Turn eSupplierConnect into an API

What you can build on eSupplierConnect

• Check requests on my user ID

  Build this

  Reads the table in Self Service > Requests on my user ID, with the supplier codes behind each application request.

  Takes

  Status (optional), submit date from and to (optional)

  Returns

  Request ID, type, application name, supplier codes, status, in charge to, submit date, last update, requester ID, target ID

• List my applications and supplier codes

  Build this

  Reads Self Service > User Application Manager: each application granted to your user ID, with its role and the supplier codes it covers.

  Takes

  Nothing

  Returns

  Application name, role, supplier codes

• Get my security administrators

  Build this

  Reads Self Service > User Info: your Administration Group and the Own and Root Supplier Security Administrators listed for it.

  Takes

  Nothing

  Returns

  Administration group, own administrators, root administrators

• Request an application for supplier codes

  Build this

  Opens Applications > Request Applications in a region, selects an application under My Organization Applications, picks the role and supplier codes and submits.

  Takes

  Region, application name, role (if the application has roles), supplier codes

  Returns

  Application name, supplier codes, request ID, status

Automate eSupplierConnect 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.

• Application requests that moved, every weekday

  Build this

  Starts

  Every weekday at 8:00

  Step 1

  Check Requests on my user ID for requests submitted in the last 30 days.

  Step 2

  Keep the requests whose status changed since the last run.

  Step 3

  Email you each one with its application name, supplier codes, status and who it is in charge to.

• Weekly check of applications and supplier codes

  Build this

  Starts

  Every Monday at 7:00

  Step 1

  List the applications, roles and supplier codes in User Application Manager.

  Step 2

  Keep what was added, removed or changed since the last run.

  Step 3

  Post the changes to your access-review system's webhook.

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 “Check requests on my user ID” would look like.

curl https://api.fous.com/v1/runs \
  -H "Authorization: Bearer $FOUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "fcagroup.esupplierconnect.com/get_requests_on_my_user_id",
    "input": {
      "status": "Pending",
      "submit_date_from": "2026-10-01"
    }
  }'

{
  "status": "completed",
  "data": {
    "requests": [
      {
        "request_id": "R-0048213",
        "type": "Application request",
        "application_name": "GST - Global Sourcing Tool",
        "supplier_codes": "1500012345, 1500012346",
        "status": "Pending",
        "in_charge_to": "Supplier Security Administrator",
        "submit_date": "2026-11-06",
        "last_update": "2026-11-09",
        "requester_id": "ACME0042",
        "target_id": "ACME0042"
      }
    ]
  }
}

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.

ESupplierConnect’s own options

eSupplierConnect is the Stellantis supplier portal: a single sign-in that opens the applications granted to your supplier codes. Its manuals describe no supplier API. All FCA US suppliers and carriers must set up an electronic connection, and Stellantis publishes EDI guides for schedules, ship notices, purchase orders, invoices and remittances.

Read on November 12, 2026: eSupplierConnect general end user manual, FCA US electronic commerce requirements, FCA US production parts supplier EDI guides-Parts-Supplier---Summary-.aspx).

Signing in to eSupplierConnect

eSupplierConnect signs you in with a user ID and password, and one sign-in opens every application granted. Only users of MyDocs with authority to manage bank details add a second step, a code from an authenticator app. With Fous you sign in once through eSupplierConnect's own sign-in with your own account: the login is sealed with AES-256, and a password-only account is signed back in when its session expires.

Worth knowing

One application request at a time

eSupplierConnect will not take a new application request until your previous one has been completed. A method that requests applications should check Requests on my user ID first.

Applications follow supplier codes and regions

Each application is granted for chosen supplier codes and opened from a region: Enlarged Europe, LATAM, North America or APAC. All of a company's supplier codes sit in its ROOT Administration Group.

Who approves new users

The first user at a new supplier is approved by an eSupplierConnect administrator at Stellantis. Later users are approved by that supplier's own Supplier Security Administrator.

Schedules and ship notices travel by EDI

For FCA US, material releases (830), shipping schedules (862) and advance ship notices (856) are EDI transactions. All FCA US suppliers and carriers must set up an electronic connection.

More in Manufacturing: OEM supplier portals

• Exostar
• RTX Supply Chain Platform
• GE Aerospace Supplier Portal
• Net-Inspect
• SupplyOn
• IMDS
• Covisint Supplier Portal
• BMW Group Partner Portal
• GM SupplyPower
• Mercedes-Benz Supplier Portal
• ONE.Konzern Business Plattform
• Lockheed Martin Procure to Pay
• Cummins Supplier Portal
• TWX-21
• Daimler Truck Supplier Portal
• Volvo Group Supplier Portal

Other industries: ILSmart, PF Expert, myCintas, Lowe's Vendor Gateway, Asda Supplier Portal, T-Mobile for Business Account Hub.