Contents
Can I change my API?
You can change your API secret using the Nexmo Secret Management API. Once that’s done, you can revoke the existing API secret until you need to rotate your credentials again. We also support customers to create/remove API secrets in the Customer Dashboard Setting page https://dashboard.nexmo.com/settings.
How do you version an API?
There are four common ways to version a REST API.
- Versioning through URI Path.
- Versioning through query parameters.
- Versioning through custom headers.
- Versioning through content negotiation.
- Summary.
Are API easy?
Relax. While the way people talk about APIs sounds horribly complex, in reality they are very easy to understand. That said, if you run a website or supervise people who do web development, you do need to understand what an API is – and why they are mission critical to your business.
What does it mean to break an API?
As the name might suggest, a breaking change to an API is any change that can break a client’s application. Usually, breaking changes involve modifying or deleting existing parts of an API. With the latter, deletion, it’s inevitable that applications break.
What happens when an API change is made?
Source-level quiet semantics change – an API change that results in existing code written to compile against older version of the API quietly change its semantics, e.g. by calling a different method. The code should however continue to compile with no warnings/errors, and previously compiled assemblies should work as before.
What kind of change is not a breaking change?
In most cases, a change that adds to an API is not a breaking change. This type of change, called an additive change, may involve new resources or methods, new response fields, and even new query parameters. Since these changes don’t affect existing flows, they shouldn’t break applications — but more on that in a second.
Is it bad to remove APIs from a library?
Removing APIs is a binary breaking change. Considering keeping obsolete types and methods if maintaining them is low cost and doesn’t add lot of technical debt to your library. Not removing types and methods can help avoid the worst-case scenarios mentioned above.