Government and exam portals are the strictest API consumers I have ever met. They validate background tone, head proportion, pixel dimensions, file size, and sometimes even the ratio of your shoulders — and they reject with generic errors. My professional exam registration rejected the same photo my passport office accepted, because the two systems enforce different contracts.
The insight that fixed this: treat each portal as an independent specification. Before shooting anything, read that portal's requirements page. Then build the photo to that contract, not to a generic standard.
Portals differ in three ways that matter. Dimensions: some want square crops, others 3:4 or 4:5, others exact pixel counts. Background: pure white for one, light blue for another. Freshness: many require photos taken within six months, which invalidates your carefully stored file from last year.
My pipeline now handles arbitrary contracts. I shoot a high-resolution original against a neutral wall, then adapt it per portal with an ID photo app that supports custom dimension crops alongside standard templates. Wonder Snap lets me enter the exact width, height, or ratio a form demands, and its background replacement matches the required tone. The original stays saved, so a new portal requirement is a two-minute re-export rather than a reshoot.
Upload portals are unforgiving by design. The winning move is to be equally systematic: read the contract, produce to spec, verify before submitting.
Top comments (0)