Source: https://quadevs.com/windows-web-services/

Title: API development, REST and SOAP web services | quadevs

[Home](https://quadevs.com/)/ API development, web services and Windows services

# API development, web services and Windows services

REST and SOAP APIs, WCF services and background Windows services that other systems call every day.

[Tell us about your project](https://quadevs.com/contact/)  [or email us](mailto:hello@quadevs.com)

**API development** is half of system integration. The other half is the background work behind the API: Windows services that pull from queues, retry failed calls and record what happened. We build both in .NET, for systems that other teams and partners depend on.

## Services and APIs we build

Partner, regulator and clearing systems connect through adapters to REST and SOAP endpoints, queue workers and alerts that carry context.

- ### REST API development

  ASP.NET Core endpoints versioned by schema, each consumer with a typed client.
- ### SOAP and WCF services

  Upkeep and new endpoints for partners that still call SOAP.
- ### Windows services

  Queue workers, schedulers and intake services that run unattended.
- ### System integration services

  Partner, regulator and clearing systems connected through adapters.
- ### Retries and incidents

  Retry queues that separate transient from permanent failures, and alerts that carry context.

## Services other systems call

- [HEDIS measurement pipeline](https://quadevs.com/case/hedis-pipeline/)

  Transient and permanent failures go to separate retry queues in the HEDIS engine we built, and on-call staff get a Slack message with the order attached.
- [Clinical data aggregation hub](https://quadevs.com/case/clinical-data-hub/)

  Request budgets in our clinical aggregation hub stop one consumer from starving the others.
- [FHIR · TEFCA · USCDI integration](https://quadevs.com/case/fhir-tefca-uscdi/)

  Payer-to-payer Member Match on our FHIR server issues a short-lived signed JWT for each Patient/$match call.
- [HIPAA audited file proxy](https://quadevs.com/case/hipaa-file-proxy/)

  Every read, download and expiry in our clinical file proxy goes into an audit dataset that compliance can query directly.
- [Energy billing system](https://quadevs.com/case/energy-billing/)

  Billing software we built for energy distributors exchanges data with national clearing pipelines.
- And many more projects

  [All case studies](https://quadevs.com/cases/) [Ask about your project](https://quadevs.com/contact/)

Language and runtime: [.NET development](https://quadevs.com/dotnet-development/). Desktop software on the same machines: [Windows desktop applications](https://quadevs.com/windows-app-development/).

## How service work starts

1. ### Callers and load

   Tell us who calls the service, what it processes, where it runs and what fails.
2. ### Contract first

   We write the API contract or WSDL and agree it with the teams that call it.
3. ### Parallel run

   The new service answers part of the real traffic before the old one is switched off.

**And much more.** [Ask about your project](https://quadevs.com/contact/)

## Common questions

Can you keep our SOAP services running?

Yes. Upkeep and new endpoints for SOAP and WCF are part of this work, for partners that still call them. We retire a SOAP endpoint only when you decide to.

## Which systems call your services?

Describe the service, its callers and the servers it runs on.

### Your project brief
