Systems that Talk

API Integration 101 for ERP Teams

Project Overview

A 15-minute training deck that explains how an ERP exchanges data with banks, marketplaces, couriers, and tax systems, written for people who work with an ERP but don't write code. Instead of starting from theory, it starts from a familiar problem: orders copied by hand every morning, where one typo means wrong stock and a wrong invoice. From there it builds three practical skills: explaining what an API is, reading a request and its reply, and knowing where to look first when an integration breaks.

What It Covers

• An API is a waiter

  A restaurant analogy that makes the idea stick, then maps it straight onto an ERP asking a bank.

• The four parts of a request

  Method, endpoint, key, and body, each with an everyday comparison and a real Postman example.

• Read the first digit

  Four methods and three status code groups, and how the first digit tells you whose side the problem is on.

• One order, six steps

  A marketplace order followed across every system, showing the API call behind each step.

• A troubleshooting order

  Four checks to run in sequence when an integration breaks, before blaming the other system.

• Built to be interactive

  Questions and a quick check throughout, so the room answers instead of just listening.

How the Session Runs

1. 1

   Why integrate

   Start from a daily manual job, then ask which apps your own teams could connect.

2. 2

   What an API is

   The waiter between two systems, and why you don't get to walk into the kitchen.

3. 3

   How it talks

   Read a request part by part, then test yourself on methods and status codes.

4. 4

   In real life

   Follow one order through the ERP, courier, bank, and tax system with no re-typing.

5. 5

   When it breaks

   Work through a real scenario: marketplace orders stopped arriving this morning.

6. 6

   Recap

   Three things to take home, and one last question to test them.

A Look Inside