Skip to main content

Keene Systems, Inc.

API Development Services: Custom APIs That Connect Your Business

Need your systems, customers or partners to exchange data without anyone retyping it? Start with a well-built API.

API development is the building of a secure, documented doorway into a business system, so that other software can read and update its data without a person in the middle. Keene Systems builds custom APIs on Microsoft ASP.NET Core and SQL Server: for your own applications, for your customers and partners, and around older systems that were never designed to share anything.

What custom API development means

Most business systems were built to be used by people sitting at a screen. An API lets other software use them as well. Once a system has one, a website can show live order status, a mobile app can submit work from the field, and a customer’s purchasing system can place orders with you directly.

Packaged products often come with an API of their own. Custom and older systems usually do not, and the APIs that packaged products offer rarely do exactly what your process needs. That is where a custom API comes in: it exposes the data and the actions you choose, to the people you choose, under the rules of your business. For a plain-language introduction, see what an API is on our application integration page.

Two developers working together in an office, discussing code on a screen

Signs you need a custom API

  • Staff copy data from one system into another by hand.
  • A customer or partner has asked to connect their system to yours.
  • You want a mobile app or portal on top of an existing system.
  • Systems exchange files overnight, so numbers are always a day old.
  • A key system has no way for other software to reach its data.
  • A connector you bought handles the simple cases and nothing else.

What we build

  • APIs for systems you already run. A dependable way for other software to read and update an existing application or database.
  • Customer and partner APIs. Let the companies you do business with place orders, check status and exchange documents without phone calls or re-keying.
  • The back end for a mobile app or portal. One set of data and rules serving your website, your mobile app and your internal software. See building a customer portal.
  • Integration APIs. The connecting layer between accounting, ERP, CRM and custom software, so data is entered once.
  • Replacements for aging interfaces. Older SOAP services, file drops and nightly batch jobs rebuilt as modern REST APIs.
  • Webhooks and notifications. Your system tells others the moment something happens, instead of waiting to be asked.

How we make an API safe and dependable

An API opens a door into your business data, so how it is built matters more than how quickly. Every API we deliver includes:

  • Sign-in for every caller. Each system or partner has its own credentials, which can be withdrawn without affecting anyone else.
  • Permissions by caller. A partner sees its own orders, not everyone’s.
  • Encryption in transit. Every request and reply travels over a secure connection.
  • Validation of everything received. Bad or incomplete data is rejected before it reaches your database.
  • A log of every request. Who asked for what, and when, which matters for audits and for troubleshooting.
  • Limits on use. One runaway program cannot overload the system for everyone else.
  • Versioning. The API can change without breaking the software that already depends on it.
  • Documentation and tests. Other developers can connect without calling us, and automated tests catch problems before a release.

An API around a legacy system

You do not have to replace an old system to connect it. In many cases we build an API around the existing database and business rules, so newer software can work with it while the old screens keep running. It is often the first step in a staged modernization: once other systems talk to the API instead of the old application, that application can be replaced later without disturbing them. See legacy application migration.

API integration at work: Neuco

New England Utility Constructors runs its field work, approvals, costing and invoicing on a platform we built. That platform exchanges data with SAP ERP and with Neuco’s other existing systems through APIs, and feeds Power BI reports. Billing that used to take one to three months now takes five days. Read the Neuco case study.

Custom API, or an off-the-shelf connector?

If both of your systems are popular packaged products and all you need is to copy standard records between them, a ready-made connector may be enough, and we will say so. A custom API earns its keep when one of the systems is custom or old, when your business rules decide what may be shared, when partners or customers need to connect to you, or when the same data has to serve a website, a mobile app and internal software together.

Two people analyzing business data on laptops with charts and graphs

How Keene Systems builds an API

  1. Understand the business need. We establish who needs which data, what they may do with it, and what must never be exposed.
  2. Design the API on paper first. Requests, replies, permissions and error handling are written down and agreed before any code is written.
  3. Build and test in stages. Working parts are delivered every two weeks, with automated tests and a test environment your partners can try.
  4. Document and launch. Other developers get clear documentation and examples, and we support the first connections as they go live.
  5. Keep developing it. The same team adds to the API as your business and your partners need more from it.

The next step is a short, no-pressure conversation. Schedule a project exploration call or use the form on this page.

Frequently asked questions

What are API development services?

They cover designing, building, securing, testing and documenting an API so that other software can work with a business system. The work usually includes sign-in and permissions, logging, documentation and continued development after launch.

What is the difference between API development and API integration?

API development is building an API for a system. API integration is using APIs, yours or someone else’s, to connect systems so data flows between them. Many projects involve both, and we do both.

Which technology do you use to build APIs?

Microsoft ASP.NET Core with C# and SQL Server. We build REST APIs as the standard choice, and we work with older SOAP services where a partner or an existing system requires them.

Can you build an API for a system that was never designed to have one?

Usually, yes. We build the API around the existing database and business rules, so other software can work with the system while its current screens keep running.

How do you keep an API secure?

Every caller signs in with its own credentials and sees only what it is permitted to see. Traffic is encrypted, incoming data is validated, every request is logged, and limits prevent any one caller from overloading the system.

Who owns the API you build for us?

You do. Our contract assigns the code and the intellectual property we write for you to your company, along with the documentation.

Tell us what your API needs to do

Why Keene Systems

Keene Systems has built custom business software since 1987. We are veteran-owned, and our 50+ professionals have delivered systems for companies including Hormel, McCormick, IBM and Dartmouth-Hitchcock. See our client list.

Schedule a project exploration call.

Schedule a Project Exploration Call

This free session is your fastest path to improved business productivity.