npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

@zauto/api-connector

v0.0.3

Published

A NestJS-based API connector for managing integrations.

Readme

API Connector Package

A dynamic and flexible TypeScript-based API connector package designed to facilitate seamless integration between a local database and external APIs. The package includes features like dynamic field mapping, endpoint configuration, and robust authentication support.

Features

  • Dynamic API Configuration: Manage API settings like base URL, authentication, and headers dynamically.
  • Endpoint Management: Configure endpoints with methods, headers, and field mappings.
  • Field Mapping: Dynamically map request and response fields for six resources: Patient, Physician, Facility, Schedule, Slot, and Appointment.
  • Authentication: Supports multiple authentication types (BASIC, BEARER, API_KEY, or NONE).
  • Retry and Timeout Policies: Define retry strategies and request timeouts for robust communication.
  • Prisma Integration: Leverages Prisma for database interactions with models such as ApiConfig, EndpointConfig, and FieldMapping.

Installation

Install the package using npm:

npm install <package-name>

Database Design

Models

  • ApiConfig: Stores the top-level configuration for APIs.
  • EndpointConfig: Manages endpoint-specific configurations linked to an API.
  • FieldMapping: Handles request and response field mappings for endpoints.

Example Schema

model ApiConfig {
  id              String           @id @default(uuid())
  baseUrl         String
  authType        String
  infoForAuthType Json             @default("{}")
  defaultHeaders  Json             @default("{}")
  timeout         Int?
  environment     String?
  retryPolicy     Json             @default("{}")
  orgId           String?
  doneBy          String?
  createdAt       DateTime         @default(now())
  updatedAt       DateTime         @updatedAt
  endpoints       EndpointConfig[]
}

model EndpointConfig {
  id           String         @id @default(uuid())
  name         String
  method       String
  suburl       String
  headers      Json           @default("{}")
  createdAt    DateTime       @default(now())
  updatedAt    DateTime       @updatedAt
  apiConfigId  String
  apiConfig    ApiConfig      @relation(fields: [apiConfigId], references: [id])
  FieldMapping FieldMapping[]

  @@unique([name, apiConfigId])
}

model FieldMapping {
  id              String         @id @default(uuid())
  resourceType    ResourceType
  requestMapping  Json?
  responseMapping Json?
  createdAt       DateTime       @default(now())
  updatedAt       DateTime       @updatedAt
  endpointId      String
  endpoint        EndpointConfig @relation(fields: [endpointId], references: [id])
}

enum ResourceType {
  Patient
  Physician
  Facility
  Schedule
  Slot
  Appointment
}

Usage

API Configuration

Use saveApiConfig to save or update API configurations dynamically:

import { PrismaClient } from '@prisma/client';
import { saveApiConfig } from '<package-name>';

const prisma = new PrismaClient();

const apiConfig = {
  baseUrl: 'https://api.example.com',
  authType: 'BEARER',
  infoForAuthType: { token: 'your-token' },
};

const result = await saveApiConfig(prisma, apiConfig, { orgId: '123' });
console.log(result);

Endpoint Configuration

Save or update endpoint configurations linked to an API configuration:

import { saveEndpointConfig } from '<package-name>';

const endpointConfig = {
  name: 'getPatients',
  method: 'GET',
  suburl: '/patients',
  apiConfigId: 'api-config-id',
};

const result = await saveEndpointConfig(prisma, endpointConfig);
console.log(result);

Field Mapping

Configure dynamic mappings for request and response data:

import { saveFieldMapping } from '<package-name>';

const fieldMapping = {
  resourceType: 'Patient',
  requestMapping: { localField1: 'apiField1', localField2: 'apiField2' },
  responseMapping: { apiField1: 'localField1', apiField2: 'localField2' },
  endpointId: 'endpoint-id',
};

const result = await saveFieldMapping(prisma, fieldMapping);
console.log(result);

API Call with Dynamic Mapping

Make API calls with dynamic field mapping applied to request and response data:

import { callApiWithMapping } from '<package-name>';

const response = await callApiWithMapping(prisma, 'endpoint-id', {
  localField1: 'value1',
});
console.log(response);

Authentication Types

  • BASIC: Username and password authentication.
  • BEARER: Token-based authentication.
  • API_KEY: API key authentication.
  • NONE: No authentication.

Development

Directory Structure

/src
  /dto
    api-config.dto.ts
    endpoint-config.dto.ts
    field-mapping.dto.ts
  index.ts

Exported Functions

  • saveApiConfig
  • updateApiConfig
  • saveEndpointConfig
  • saveFieldMapping
  • callApiWithMapping

Contributing

Contributions are welcome! Submit issues or pull requests on GitHub.


License

MIT License


Let me know if there are additional details or changes you'd like to make!