Blue Express Simulator CL
REST mock of Blue's SSO (/oauth2/token) and API (emission, /labels, Tracking Pull and
/search), built from the bodies captured against Blue's QA API.
Tracking-aware: each OS accumulates its own event history. Orders persist to blue.json; tokens and the failure mode are in memory.
Three things about Blue surprise people, and all are reproduced here.
(1) Auth errors are classified by the
x-amzn-errortype header: a bad or expired token is
a 403 AccessDeniedException (the only renewable one), a bad x-api-key a 403
ForbiddenException, a missing bearer a 401.
(2) eventDate, statusDate and emissionDate are Chile local time with a FAKE
Z; creationDate is real UTC.
(3) A Blue 500 does NOT create the OS; only create_then_timeout creates it and never answers.
Failure mode
current: none
Activate one failure mode at a time. /api/blue/debug/failure-mode.
Account
client_id:
simulator-client-id
· x-api-key: simulator-api-key
(override with BLUE_SIM_CLIENT_ID / BLUE_SIM_CLIENT_SECRET / BLUE_SIM_API_KEY)clientAccount:
76000000-1-1
· userName: SIMULATOR
(override with BLUE_SIM_CLIENT_ACCOUNTS / BLUE_SIM_USER_NAMES)Covered districts:
the whole Blue geo catalogue
(narrow with
BLUE_SIM_COVERED_DISTRICTS)Orders of service 0
No orders yet. Use
POST /api/blue/cmkin/customer/corp/emission/v1/emission from shipping-service or curl to create one.