canonical: https://jentic.com/apis/injection-api.futurefulfilmentsoftware.com/future-fulfilment

# Injection Api Futurefulfilmentsoftware Future Fulfilment Direct Injection - v3.1

The Future Fulfilment Direct Injection API books and manages parcel shipments for fulfilment in Australia. It returns shipping rates, validates a shipment request against carrier rules, creates shipments with their labels, voids bookings, and manifests parcels for carrier handover. Each request carries the sender's account number so bookings are attributed to the right fulfilment account.

## For AI agents

Get shipping rates, validate and create parcel shipments, retrieve labels, void bookings, and manifest parcels for Australian fulfilment.

## Scope

Does not handle order management, inventory, or payment collection. Use for parcel shipment creation and label generation only.

## Capabilities

- Retrieve shipping rates for a parcel before booking
- Validate a shipment request against carrier rules before creating it
- Create a shipment and generate its carrier label
- Void a previously created shipment by its id
- Manifest one or more shipments for carrier handover

## Use cases

### AI Agent Shipment Booking

An AI agent connected through Jentic books outbound parcels end to end: it fetches a rate, validates the shipment request, creates the shipment, and retrieves the label ready to print. Because the agent calls each operation directly, order-management systems can trigger fulfilment without a human stepping through the carrier portal.

Example prompt: Fetch a rate for a 2 kg parcel, validate and create the shipment, and retrieve its label

### Rate Shopping Before Fulfilment

Before committing a booking, a merchant's system queries the rate operation to price a parcel and decide whether to ship. Validation then confirms the shipment request is acceptable, so the create call rarely fails for avoidable reasons.

Example prompt: Request a rate for a parcel to a Sydney postcode and validate the shipment request before creating it

### End-of-Day Manifesting

At the close of fulfilment, the manifest operation groups the shipments created during the day into a single carrier handover document. This closes out bookings in one call rather than per parcel.

Example prompt: Manifest all shipments created today so they are ready for carrier pickup

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/rates` | Get a shipping rate for a parcel |
| POST | `/shipments/validate` | Validate a shipment request |
| POST | `/shipments/create` | Create a shipment and its label |
| GET | `/labels/{shipmentId}` | Get a shipment label |
| POST | `/shipments/{shipmentId}/void` | Void a shipment |
| POST | `/manifests/create` | Manifest shipments for handover |

## Key resources

- **Shipments** — Validate, create, and void parcel shipments
- **Rates** — Retrieve shipping rates for a parcel
- **Labels** — Retrieve the carrier label for a shipment
- **Manifests** — Manifest shipments for carrier handover

## 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:** 63 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 75 / 100
  - Developer Experience & Jentic Compatibility: 91 / 100
  - AI-Readiness & Agent Experience: 58 / 100
  - Agent Usability: 94 / 100
  - Security: 30 / 100
  - AI Discoverability: 73 / 100
- **View full report:** https://jentic.com/apis/injection-api.futurefulfilmentsoftware.com/future-fulfilment/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 Future Fulfilment Direct Injection API by hand means setting up HTTP Basic authentication, attaching your account number header to every call, and sequencing validation before create yourself. Through Jentic you install once, import it from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** The API carries shipment details in the request body, so rules bound which operations your agent may call, not which shipments it can touch. You choose the operations it may use, such as fetching rates and creating shipments, so voiding a booking is not included unless you add it.
- **Credential handling:** Your Future Fulfilment account number and Basic auth credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get a shipping rate' or 'create a shipment', and Jentic returns the matching Future Fulfilment operation with its input schema so the agent calls the right endpoint without reading the reference docs.

## Related APIs

- **Shippo** — Shippo is a multi-carrier shipping API for rates, labels, and tracking.
- **ShipEngine** — ShipEngine provides rate shopping and label generation across many carriers.
- **AfterShip** — AfterShip tracks parcels and sends delivery updates after a shipment is booked.

## FAQ

### What authentication does the Future Fulfilment Direct Injection API use?

It uses HTTP Basic authentication and also requires your account number in the `accountNumber` request header, as declared in its OpenAPI spec. Both are sent on each request. Through Jentic these credentials are stored encrypted by your own Jentic One instance and injected at call time, so they never appear in the agent's prompt or logs.

### Can I get a shipping rate before creating a shipment with this API?

Yes. The rate operation returns pricing for a parcel, and you can validate the shipment request first and then create the shipment and its label once you are ready to book.

### What are the rate limits for the Future Fulfilment Direct Injection API?

The OpenAPI spec does not specify rate limits for the Future Fulfilment Direct Injection API. Check the limits documented in your Future Fulfilment account before scaling automated bookings.

### Can I limit what my agent is allowed to do with the Future Fulfilment Direct Injection API?

Yes. Write a rule that allows only the rate-lookup and shipment-create operations, so the agent can quote and book shipments but cannot void them, and every call it makes is logged. Voiding and manifesting stay out of reach until you add them to the rule.

### How do I create a shipment with this API through Jentic?

Search Jentic for 'create a shipment', add the Future Fulfilment Direct Injection API from the directory, and store your Basic credentials and account number once. Your agent then validates the request, creates the shipment, and retrieves the label. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### Is there a Future Fulfilment Direct Injection API MCP server?

You don't need an MCP server to give your agent the Future Fulfilment Direct Injection API. Jentic connects it directly from the API Directory: import it, store your credentials once, and your agent calls the rate, shipment, label, and manifest operations. That keeps extra tool definitions out of the agent's context.