You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Analyse impact of new guidelines on partial success responses #389
Problem description
Commonalities has updated section 3 of CAMARA-API-Design-Guide.md, with new guidelines fo the format of success responses when the result is negative, partial, or unknown
Device Location APIs already had cases when the result is unknown or partial, and they return 422 errors in such situations.
Possible evolution
Analyse the guidelines and decide whether we should update any of the current APIs responses
Alternative solution
Keep the current behaviour
Additional context
Take into consideration the Versioning and Migration Guidance:
New APIs and new MAJOR versions SHOULD follow this guidance.
Existing stable APIs MAY adopt it in a future MAJOR version where behavior or response semantics would otherwise change.
Where possible, APIs MAY introduce contextCode and contextMessage as additive, backward-compatible changes.
From Orange our preference is to keep existing pattern leveraging 422 and not switch to contextCode and contextMessage use.
We think that status code is more straightforward for the developer as for the operator to understand & log API result.
Activity
bigludo7 commentedon Jun 16, 2026
From Orange our preference is to keep existing pattern leveraging 422 and not switch to
contextCodeandcontextMessageuse.We think that status code is more straightforward for the developer as for the operator to understand & log API result.
jlurien commentedon Jul 14, 2026
Telefónica's position is also to continue with the current design and keep the 422 errors defined.
jlurien commentedon Jul 27, 2026
No further preferences submitted before the deadline to create RC snapshot, so we keep the current design