QualityPost Simulator MX
REST mock ofguia_request_filelabel + consultas_vlcode.
Tracking-aware: each guide accumulates its own timeline. State is in-memory and resets on simulator restart.
QualityPost answers HTTP 200 to everything — a failure is encoded in the body, never in a
status code. That is why the failure modes below (except the rate limit) still come back as 200. The carrier
emits two error shapes, both observed against the live API: the documented
{ id_request: null, error: '<texto>' } and the real
{ error: true, mensaje: '<texto>' }. Both are reproduced here, with the carrier's own wording —
ERROR_FRAGMENT_CLASSIFIERS matches on that text, so a paraphrase silently downgrades the
classification.
An unknown guide answers [], indistinguishable from a guide QualityPost has not scanned yet.
Failure mode
current: none
Activate one failure mode at a time. /api/qualitypost/debug/failure-mode.
postal_code_not_covered only affects the create; tracking_not_available only the
timeline read; the other two affect every authenticated request.
Guides 0
No guides yet. Use
POST /api/qualitypost/guia_request_filelabel from shipping-service or curl to create one.