Programming and software development · ENGLISH
Service page for projects serving Medellin. Define API contracts, permissions and error responses before exposing data. For Medellin, catalogue and enquiry journeys should keep their context from search to detail and contact.
01 · CONTEXT
For Medellin, catalogue and enquiry journeys should keep their context from search to detail and contact.
02 · PRACTICAL BRIEF
Implementation, architecture and maintenance
Describe the problem, intended users, what exists today, technology constraints and one example of the expected result. Do not share passwords; arrange temporary access only when needed. Before finalising the brief for Medellin, confirm with the people involved: For Medellin, catalogue and enquiry journeys should keep their context from search to detail and contact.
An API contract covering schemas, authentication, permissions and error responses.
Verify responses and role permissions, along with limits and failure cases.
03 · METHOD
Implementation, architecture and maintenance
04 · ANSWERS
Define API contracts, permissions and error responses before exposing data. An API contract covering schemas, authentication, permissions and error responses.
Share expected behaviour, users, rules, existing technology and constraints. Do not send passwords; arrange access only if needed.
Verify responses and role permissions, along with limits and failure cases.