API standards
A style guide covering naming, errors, pagination, versioning and deprecation, with linting in the pipeline.
Service offering
API platform engineering
One way for your teams to design, publish and secure APIs, with a portal that lets developers start on their own.
We set up the platform your teams use to design, publish and run APIs: a style guide with versioning rules, gateway policies for keys and rate limits, and a developer portal with documentation and sandbox access. Contract tests run in every pipeline, so a change that would break a consumer is caught before release.
In financial services, the platform can follow the CBUAE open finance framework in the UAE and the SAMA open banking framework in Saudi Arabia; for government APIs, it can follow the integration standards of TDRA and Digital Dubai or of the Digital Government Authority, as context for your own policy.
What the work involves
Gateway and security
Key management, OAuth scopes, rate limits and quotas configured as code on the API gateway.
Developer portal
Documentation, sandbox keys and onboarding steps, so internal and partner developers can start without raising a ticket.
Engineering in your repositories
Code, pipelines and documentation live in your repositories from the first commit.
Security and performance
Security checks and performance budgets run in every build, not as a review at the end.
When an API platform is due
The need shows once APIs are shared outside the team that built them, and each team secures and documents them differently.
- Partners or other departments wait weeks for access.
- APIs break their consumers because versioning rules are not written down.
- Keys, rate limits and documentation are handled differently by each team.
Talk to us about API platform engineering
Tell us what you need to achieve and by when. We will propose a scope, a team and an itemised quotation.