by Tony Harris • October 5, 2021
Frequent deployment of APIs can quickly create a software system that is like an overgrown garden, riddled with weeds, bugs, failed integrations, and ill-fitting use cases. Overloaded API collections prevent changes without causing failures. More commonly, they limit the visibility needed to recognize opportunities for feature optimization. Creating a successful API can go a long way to ensuring your organization can avoid many of these problems.
An appropriate API design does more than just prevent cumbersome integration – it can serve as the backbone for your business connectivity. The following guidelines are the best 7 tips for creating a successful API primarily intended for developers and architects who are already managing a diverse collection of implementations, methods, and languages dedicated to their APIs. From high-level conceptualization to interface standards to API testing, these tips will help you maintain your thriving garden of APIs.
Sign up for our free 14 day hosted trial to learn how.
A disturbing number of companies don’t have a central repository containing a catalogue of their current APIs, documentation on how to use them, and reports of versions and changes. Instead, each team maintains its own API repository, relying on developer knowledge and large corporate code bases.
Development managers should create a procedure for adding new APIs to some sort of centralized, editable system, such as a wiki. Create a mind map that lists API dependencies and add links to a wiki page describing the API for each node on the map. This information should use a standard format that describes the API, consumers, maintainers, its location in the code, and tests that serve as examples. For example, the OpenAPI open-source language and tool are commonly used to define and document APIs. A strict API definition includes associated commands, HTTP protocols, URLs, status, error codes, and payload structure.
You do not need to use the /getorder command if you are already using HTTP GET to make calls. This URL can be as simple as /order/54321 — the resulting payload will be the call information.
As a general rule, you will want to use these common HTTP requests:
You can also use PUT to create IDs if the client selects the ID number itself.
The Create, Read, Update, and Delete (CRUD) elements combine to allow developers to create new features and test them. However, it is common for an API not to require the full CRUD structure. For example, a mobile application may depend on the read functionality. Or a developer may add “create,” but think, “I’ll add the delete function later.” Sometimes the “later” never comes. Save time in the long run by implementing a full CRUD capability within the same deployment.
Some users may create their own account in a particular application but not have permission to delete it. Others may have permission to read but not to update, create, or delete a resource. Authentication proves that a person can log in, while permission indicates that they can access a resource. In general, RESTful services do this either through interaction with the Lightweight Directory Access Protocol (LDAP, for employees) or through a client profile object for software products with clients.
Aim for 100 milliseconds for internal services without HTTP dependencies and an upper limit of about one second for complicated services inside the data center. If a function call gets too time-consuming, such as creating an account, don’t just let it run for a long time. Instead, come back with an accountID, or at least a token that the customer can use later to view the account. Create guidelines for time limits and try to avoid a voting process that only records the time a process ends, not when it began.
You can implement sorting and filtering on the URL with query parameters. /products?name=”*testing*” gives all products that contain the word testing. The documentation shows what parameters are available. Use ?sort=ASC or ?sort=DESC to specify how to return the results, which can get more complex.
In essence, filtering implements the search, while sorting allows the query to change the order preference. These are two of the most common functions in e-commerce or any database. While extreme programming says “You Aren’t Gonna Need It” (YAGNI), at least think about how to build and publish URLs so that everyone can implement them later without changing their initial behavior.
This looks like sorting and filtering. The simplest way to do this might be /products?name=”*testing* “? limit=10?offset=10. This would give the second set of 10 results. This allows programmers to change the length of pages with parameters. Use filterNames whenever possible to simplify the creation of database queries.
To create successful APIs, developers must follow a set of best practices from design to implementation. In this article, we outlined the best 7 tips for creating a successful API. For similar updates, keep an eye on our DreamFactory Blog.
DreamFactory is an API management platform that helps you streamline everything while you focus on building your frontend application. DreamFactory can help you bring your API-as-a-product mindset to life and get more out of the solutions your business is creating. Start your 14-day free trial today and experience it for yourself.
5 Essential APIs for Application Integration
Join the DreamFactory newsletter list.