How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

e2open Bookings API

Ocean shipping booking management

e2open Bookings API is one of 6 APIs that E2open publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Bookings. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and a getting-started guide.

This API exposes 5 operations across 3 paths, and defines 10 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://api.inttra.com/v1.

5 operations 3 paths 10 schemas 2 GET2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.e2open.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

e2open Bookings API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Bearer token obtained from the INTTRA identity service

Paths & Operations 5

Across 3 paths, the API surfaces 5 operations — 2 GET, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Bookings 5

Ocean shipping booking management

GET
/bookings
List ocean bookings
listBookings 7 params → 200401
POST
/bookings
Create an ocean booking
createBooking body → 201400
GET
/bookings/{bookingId}
Get booking details
getBooking 1 param → 200404
PUT
/bookings/{bookingId}
Amend an existing booking
amendBooking 1 param body → 200
POST
/bookings/{bookingId}/cancel
Cancel a booking
cancelBooking 1 param body → 200

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are BookingRequest (9 properties), BookingSummary (8 properties), TradeParty (6 properties), Container (4 properties). Each schema is shown below with its type and property counts.

BookingRequest
object
9 properties 5 required
BookingList
object
3 properties
Vessel
object
3 properties
ContainerRequest
object
3 properties 2 required
BookingAmendment
object
3 properties
BookingSummary
object
8 properties
Error
object
3 properties
TradeParty
object
6 properties
Booking
Container
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

e2open-bookings-api-openapi.yml Raw ↑

Other APIs E2open publishes across the network.

E2open Supply Chain Platform API
E2open Transportation Management API
e2open Schedules API
e2open Shipping Instructions API
e2open Tracking API
Where this information came from

This is an independent, third-party profile of e2open Bookings API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.