api-integration

Name: api-integration
Availability: InStock
Author: Sihu

Connect external tender platform APIs to client workflows.

Updated Aug 27, 2026

Search Tags:#api #integration #sam #ted #g2b #tender

Ready to run

npx skills add https://github.com/sihu-dev/bidflow --skill api-integration-sihu-dev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: api-integration
Source: https://github.com/sihu-dev/bidflow/tree/main/.claude/skills/api-integration
Command: npx skills add https://github.com/sihu-dev/bidflow --skill api-integration-sihu-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

External tender platforms expose a variety of APIs with differing formats. This Skill provides structured connectors and normalization to simplify data retrieval and integration into downstream systems.

Core Features & Use Cases

API Connectors: TED, SAM.gov, and G2B clients with consistent interfaces.
Normalization & Storage: Unify disparate responses into a common model and store in a DB or data lake.
Use Case: A developer runs a script to fetch current EU tenders via TED and ingest them into a data warehouse for analysis.

Quick Start

Use the /api test ted command to validate connectivity, then /api fetch sam_gov --keyword "procurement".

Frequently Asked Questions about api-integration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I integrate multiple tender platform APIs like TED, SAM.gov, and G2B into my workflow?▼

API integration across tender platforms uses dedicated client connectors for each provider. This Skill provides TED, SAM.gov, and G2B clients with consistent interfaces, enabling you to fetch and normalize data from all three platforms through a unified command structure without building separate integrations.

Can I automate tender data retrieval and store results in a database?▼

Yes. The Skill normalizes disparate API responses into a common data model, allowing you to fetch tenders via command and ingest them directly into a data warehouse or database for downstream analysis and storage.

What authentication methods does this tender API integration support?▼

The Skill implements API key and entity ID authentication across providers, with per-provider client configuration. Each tender platform client handles its own credential model, so you configure once and authenticate transparently across TED, SAM.gov, and G2B.

How do I test connectivity to tender APIs before running production data fetches?▼

Use the command-driven /api interface to validate connections. Run /api test ted to verify TED connectivity, then execute /api fetch sam_gov with query parameters like --keyword to confirm each platform responds correctly before scaling to production workflows.

Do I need to write separate code for each tender platform's API format?▼

No. This Skill provides a shared base client layer with abstracted endpoints for BidPublicInfoService and ContractInfoService, eliminating format-specific code. The multi-provider HTTP client normalizes responses, so you work with unified data structures across all three platforms.