canonical: https://jentic.com/apis/ejadtech.sa/emanifest

# Ejadtech Sa eManifest API

The eManifest API registers the transporter companies, producer entities, waste receivers, branches, drivers, and vehicles behind regulated waste transport, along with the reference data they depend on such as waste types, waste classifications, container types, units of measure, and handling methods. On top of that master data it creates eManifest requests for a waste movement and issues eManifest certificates for it, and it reads supporting lists such as states and process activities. A token endpoint issues the bearer credential each call carries.

## For AI agents

Register the companies, entities, drivers, and vehicles for regulated waste transport, define the waste reference data, then create eManifest requests and issue eManifest certificates.

## Scope

Does not calculate shipping rates, print carrier labels, or track live vehicle location. Use for registering waste-transport master data and filing eManifest requests and certificates only.

## Capabilities

- Register transporter companies, producer entities, and waste receivers
- Add drivers, vehicles, vehicle categories, and vehicle activities to the fleet
- Define waste types, waste classifications, container types, and handling methods
- Create eManifest requests for a waste movement
- Issue eManifest certificates for a completed manifest
- Read supporting reference lists such as states and process activities

## Use cases

### Agent-filed waste manifests

An AI agent files the paperwork for a waste movement. Through Jentic the agent confirms the transporter, producer, driver, and vehicle records exist, creates an eManifest request for the movement, and issues the eManifest certificate once it is ready. The waste type, classification, and handling-method reference data back each record.

Example prompt: Create an eManifest request for a waste movement and issue its eManifest certificate once the request is accepted

### Onboarding a transporter's fleet

Before a transporter can move waste, its fleet must be on record. The API registers the transporter company, its branches, drivers, and vehicles, and ties them to vehicle categories and activities, so an onboarding workflow can stand up a new transporter's data in sequence rather than through a manual portal.

Example prompt: Register a transporter company, then add its branches, drivers, and vehicles with their vehicle categories

### Setting up waste reference data

A new deployment needs its catalogs populated first. The API defines waste types, waste classifications, container types, units of measure, and handling methods, and reads lists such as states and process activities, so the reference data every manifest depends on is in place before any request is created.

Example prompt: Create the waste types, classifications, and handling methods, then read back the process activities list

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/api/emanifest/create_transporter_companies` | Register a transporter company |
| POST | `/api/emanifest/create_drivers` | Add a driver |
| POST | `/api/emanifest/create_vehicles` | Add a vehicle |
| POST | `/api/emanifest/create_emanifest_requests` | Create an eManifest request |
| POST | `/api/emanifest/create_emanifest_certificates` | Issue an eManifest certificate |
| POST | `/api/emanifest/create_waste_types` | Define a waste type |
| GET | `/api/emanifest/get_states` | Get the list of states |
| GET | `/api/emanifest/get_process_activities` | Get the process activities list |

## Key resources

- **Entities** — Transporter companies, producer entities, waste receivers, and branches
- **Fleet** — Drivers, vehicles, vehicle categories, and vehicle activities
- **Waste reference data** — Waste types, classifications, container types, units of measure, and handling methods
- **Manifests** — eManifest requests and the certificates issued for them
- **Lookups** — Reference lists such as states and process activities

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 52 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 74 / 100
  - Developer Experience & Jentic Compatibility: 78 / 100
  - AI-Readiness & Agent Experience: 34 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 30 / 100
- **View full report:** https://jentic.com/apis/ejadtech.sa/emanifest/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the eManifest API by hand means obtaining a bearer token from its token endpoint, choosing between its production and test hosts, and populating a chain of master data before a manifest will file. Through Jentic you install once, import eManifest from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** The eManifest API carries each record in the request body rather than a URL path, so a rule bounds your agent to the operations it needs: it can register drivers and vehicles and create manifest requests while issuing certificates stays out unless you add it. Rules bound which operations the agent may call, not which record.
- **Credential handling:** Your eManifest token is stored once, encrypted, by your own Jentic One instance and injected when a call runs. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'register a transporter company' or 'create a waste manifest', and Jentic returns the matching eManifest operation with its input schema so the agent calls the right endpoint without reading the reference docs.

## Related APIs

- **Shippo** — Generates shipping labels and tracks parcel shipments across carriers
- **AfterShip** — Tracks shipments across carriers after they leave
- **Samsara** — Manages fleet vehicles and driver telematics

## FAQ

### What authentication does the eManifest API use?

The eManifest API authenticates with a bearer token per its OpenAPI spec: you obtain a token from its token endpoint and send it as `Authorization: Bearer ...` on each operation. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's context.

### Is there an eManifest MCP server?

You don't need an MCP server to give your agent the eManifest API. Jentic connects it directly from the API Directory: import it, store your token once, and your agent calls the registration and manifest operations on demand without loading another server's tool definitions into its context.

### Can I file a waste manifest with the eManifest API?

Yes. After the producer entities, waste receivers, transporter companies, drivers, and vehicles are registered, you create an eManifest request for the movement and then issue an eManifest certificate for it. Reference lists such as states, waste types, and handling methods back those records.

### What are the rate limits for the eManifest API?

The OpenAPI spec does not state rate limits. Check with the Saudi eManifest system operator at https://mwan.gov.sa for the limits that apply to your integration before running bulk registration.

### Can I limit what my agent is allowed to do with the eManifest API?

Yes. Write a rule that allows only the operations your agent needs, such as registering drivers and vehicles and creating manifest requests, and leave certificate issuance out of the allowed set unless the agent must issue them. Every call it makes is logged.

### How do I create a waste manifest with the eManifest API through Jentic?

Search Jentic for 'create a waste manifest request' and it returns the request operation with its input schema; your agent supplies the movement details and then issues the certificate. To run it on your own infrastructure, install Jentic One from its GitHub repo.