Skip to content
Skills Library
Programming · Building & coding

enterprise-integration-api-developer

/enterprise-integration-api-developer

Guides enterprise integration platforms and APIs—REST/GraphQL versioning, OpenAPI/AsyncAPI, event-driven integration (pub/sub, outbox, idempotency, sagas), canonical models and anti-corruption layers, iPaaS/ESB orchestration vs choreography, API gateways, OAuth2/OIDC, mTLS, B2B partner APIs, transformation, correlation IDs, DLQ patterns, compatibility and deprecation. Use for enterprise integration, API developer, integration architect, OpenAPI, event-driven integration, API gateway, canonical model, iPaaS, ESB, webhook, idempotent consumer, saga pattern, B2B API, API versioning, anti-corrupti

Licence
MIT
Last repository change
20.05.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
7
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 20.05.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Guides enterprise integration platforms and APIs—REST/GraphQL versioning, OpenAPI/AsyncAPI, event-driven integration (pub/sub, outbox, idempotency, sagas), canonical models and anti-corruption layers, iPaaS/ESB orchestration vs choreography, API gateways, OAuth2/OIDC, mTLS, B2B partner APIs, transformation, correlation IDs, DLQ patterns, compatibility and deprecation. Use for enterprise integration, API developer, integration architect, OpenAPI, event-driven integration, API gateway, canonical model, iPaaS, ESB, webhook, idempotent consumer, saga pattern, B2B API, API versioning, anti-corrupti

Original author description

Guides enterprise integration platforms and APIs—REST/GraphQL versioning, OpenAPI/AsyncAPI, event-driven integration (pub/sub, outbox, idempotency, sagas), canonical models and anti-corruption layers, iPaaS/ESB orchestration vs choreography, API gateways, OAuth2/OIDC, mTLS, B2B partner APIs, transformation, correlation IDs, DLQ patterns, compatibility and deprecation. Use for enterprise integration, API developer, integration architect, OpenAPI, event-driven integration, API gateway, canonical model, iPaaS, ESB, webhook, idempotent consumer, saga pattern, B2B API, API versioning, anti-corrupti

How it works

  1. When to Use
  2. When NOT to Use
  3. Related skills
  4. Core Workflows
  5. Outputs
  6. Principles
Original SKILL.md headings · 95 lines, 533 words
SKILL.md preview
---
name: enterprise-integration-api-developer
description: |
  Guides enterprise integration platforms and APIs—REST/GraphQL versioning, OpenAPI/AsyncAPI,
  event-driven integration (pub/sub, outbox, idempotency, sagas), canonical models and
  anti-corruption layers, iPaaS/ESB orchestration vs choreography, API gateways, OAuth2/OIDC,
  mTLS, B2B partner APIs, transformation, correlation IDs, DLQ patterns, compatibility and
  deprecation. Use for enterprise integration, API developer, integration architect, OpenAPI,
  event-driven integration, API gateway, canonical model, iPaaS, ESB, webhook, idempotent
  consumer, saga pattern, B2B API, API versioning, anti-corruption layer—not EDI X12/EDIFACT
  (edi-engineer), classified air-gapped only (classified-software-devsecops-engineer), OR
  solvers (operations-research-algorithm-developer), generic CRUD (senior-software-engineer).
---

# Enterprise Integration API Developer

## When to Use

- Design **enterprise integration platforms**—hub, mesh-adjacent services, or hybrid iPaaS patterns
- Specify **REST or GraphQL APIs** with versioning, pagination, filtering, and error contracts
- Author **OpenAPI** or **AsyncAPI** specifications and consumer-driven contract tests
- Implement **event-driven** flows—topics/queues, outbox, idempotent consumers, compensating actions
- Define **canonical models**, mappings, and **anti-corruption layers** between bounded contexts
- Stand up **API gateways**, B2B partner endpoints, webhooks, and transformation/routing rules
- Apply **OAuth2/OIDC**, API keys, mTLS, and scope models for internal vs external callers
- Plan **observability**—correlation IDs, trace propagation, structured errors, DLQ operations
- Manage **lifecycle**—deprecation headers, sunset policy, backward-compatible schema evolution

## When NOT to Use

- X12/EDIFACT segment mapping, 997/APERAK, AS2/VAN EDI transport → `edi-engineer`
- Classified air-gapped build, ATO evidence, cleared pipeline promotion only → `classified-software-devsecops-engineer`
- VRP, MIP, scheduling, or solver-based optimization → `operations-research-algorithm-developer`
- Generic application CRUD, UI, or single-service features without integration architecture → `senior-software-engineer`
- CI/CD pipeline YAML, GitOps, and deploy mechanics only → `devops`
- Landing zone, VPC, and managed cloud resource design → `cloud-engineer`
- Enterprise-wide cloud reference architecture and migration roadmap → `cloud-architect`
- Internal developer platform golden paths and portals → `platform-engineer`

## Related skills

| Need | Skill |
|---|---|
| EDI standards, segments, partner certification | `edi-engineer` |
| Application services and code quality | `senior-software-engineer` |
| CI/CD, GitOps, integration service deploy | `devops` |
| Cloud messaging, networking, IAM for integrations | `cloud-engineer` |
| Cloud reference architecture and landing zones | `cloud-architect` |
| IDP, golden paths, paved-road templates | `platform-engineer` |
| Classified DevSecOps and promotion boundaries | `classified-software-devsecops-engineer` |
| OR models, routing, allocation solvers | `operations-research-algorithm-developer` |
| Enterprise architecture ADRs and cross-system review | `senior-system-architecture` |
| Pipeline security and supply chain | `devsecops` |

## Core Workflows

### 1. Scope and integration boundaries

Define systems of record, sync vs async boundaries, partner vs internal surfaces, and non-goals.

**See `references/enterprise_integration_api_scope.md`.**

### 2. API design and contracts

Model resources, errors, versioning, and publish OpenAPI/AsyncAPI with contract tests.

**See `references/api_design_and_contracts.md`.**

### 3. Event-driven reliability

Choose messaging patterns, idempotency keys, outbox, sagas/choreography, and failure handling.

**See `references/event_driven_and_reliability.md`.**

### 4. Canonical models and transformation

Define canonical schemas, ACLs, mapping rules, and validation at ingress/egress.

**See `references/canonical_models_and_transformations.md`.**

### 5. Security, gateways, and governance

Configure gateways, auth, rate limits, partner onboarding, and policy enforcement.

**See `references/security_governance_and_gateways.md`.**

### 6. Operations, observability, and lifecycle

Instrument traces and metrics, operate DLQs, and execute deprecation and compatibility plans.

**See `references/operations_observability_and_lifecycle.md`.**

## Outputs

- **Integration context diagram** — systems, channels, sync/async, trust zones
- **Contract artifacts** — OpenAPI/AsyncAPI, JSON Schema, example payloads, error catalog
- **Mapping spec** — canonical fields, transforms, validation rules, idempotency strategy
- **Runbook** — replay, DLQ drain, partner cutover, rollback, compatibility matrix
- **ADR or decision log** — orchestration vs choreography, versioning, auth model

## Principles

- Prefer **contracts and schemas** over tribal knowledge; test consumers in CI
- Make **idempotency and deduplication** explicit at every external boundary
- Separate **partner (B2B) surfaces** from internal mesh traffic—different auth, SLOs, and change windows
- Design for **observable failures**—correlation ID end-to-end, structured errors, actionable DLQs
- Ship **backward-compatible** changes; document sunsets and give consumers migration time
Files in this package (7)
  • SKILL.md 5 KB
  • references/api_design_and_contracts.md 3 KB
  • references/canonical_models_and_transformations.md 3 KB
  • references/enterprise_integration_api_scope.md 3 KB
  • references/event_driven_and_reliability.md 3 KB
  • references/operations_observability_and_lifecycle.md 3 KB
  • references/security_governance_and_gateways.md 3 KB

Versions

The database has no other skills named enterprise-integration-api-developer.

Database snapshot: 13.11.2026 · package version bbfe2b6c9e09 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100api-design-and-evolution
    Design, govern, document, review, and evolve consumer-facing APIs and event interfaces. Use when choosing REST/HTTP, GraphQL, RPC, events, webhooks, or streaming; writing OpenAPI or AsyncAPI contracts; assessing an API landscape, ownership, duplication, lifecycle,…
  • 90event-driven-architecture
    Guides event-driven systems—pub/sub, point-to-point, event sourcing, CQRS, schema versioning (Avro/JSON Schema), ordering, partitioning, delivery guarantees, idempotency, exactly-once tradeoffs, transactional outbox/inbox, choreography vs orchestration, sagas, dead-letter…
  • 80alpha-core:api-design
    Designs REST, GraphQL, gRPC, tRPC, WebSocket, SSE, and AsyncAPI/event-driven APIs. Covers OpenAPI 3.1, API gateways, GraphQL Federation, BFF pattern, contract testing, API mocking, versioning, rate limiting, webhooks, and HATEOAS maturity model. Use when designing new APIs,…
  • 95api-integration
    Designs event-driven architectures, webhook systems, API chaining flows, ETL pipelines, and integration patterns between services. Use whenever the user asks about webhooks, event streaming, API composition, connecting two or more APIs, building pipelines, Pub/Sub, Kafka topics,…
  • 95qe-middleware-testing-patterns
    Enterprise middleware testing patterns for message routing, transformation, DLQ, protocol mediation, ESB error handling, and EIP patterns. Use when testing middleware layers, message brokers, ESBs, or integration buses.
  • 100api-design-ops
    API design patterns for REST, gRPC, and GraphQL. Use for: api design, REST, gRPC, GraphQL, protobuf, schema design, api versioning, pagination, rate limiting, error format, OpenAPI, API authentication, JWT, OAuth2, API gateway, webhook, idempotency.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.