---
name: api-integration-development
description: "Design an API integration from official contracts and test its data and error handling. Use when the user requests api integration development. Select relevant methods for the requested outcome; unrelated tasks do not require this skill."
metadata:
  version: "1.0.0"
---

# API Integration Development

Design an API integration from official contracts and test its data and error handling.

## OLLIE Runtime integration

Use this capability under the active OLLIE Operator. Read live Workspace Context and tenant bindings for client facts and required inputs. This generic package contains no client configuration. Consume ask-ollie-authority-core for authority, outloop-access-fallback for access and recovery, email-lifecycle-core for communication, and the bootstrapper Runtime Contract for ownership, scheduling and completion. Preserve domain constraints; this Skill creates no competing execution path. Use one method, combine skills, or fill missing steps with authorized tools as the task requires.

External access uses the active Workspace’s approved Outloop capabilities. Never request, read, embed or expose credentials. A service named in a method is a possible dependency, not an access grant. Local file and application work uses the host’s authorized tools.

## Required inputs

- Provider documentation
- Approved capability
- Input/output contract
- Example non-sensitive responses

## Methods

### Confirm the provider contract

Confirm the documented version, pagination, rate limits and resource identity model. Keep authentication host-side through Outloop; do not embed credentials in code or examples.

### Map business fields

Map provider fields to the intended business contract, preserving identifiers and distinctions between absent, null and zero values.

### Model asynchronous states

Model asynchronous jobs, file uploads/downloads and terminal states explicitly. Validate response content instead of treating every successful HTTP status as a completed task.

### Test partial and uncertain results

Test pagination, malformed data, partial success, permission denial and uncertain writes using synthetic fixtures. Record unsupported operations rather than inventing endpoints.

## Completion

Verify findings against source evidence and read back the resulting artifact or authorized change. Report inputs used, methods selected, output location, assumptions and unresolved dependencies. Do not report a plan, queue entry, draft, test fixture or accepted request as a completed external action. Use the task’s requested format; if a tool is unavailable, finish independent work and identify the exact unfulfilled deliverable.

## Test before relying on it

Read [the synthetic evaluation cases](references/evaluation.md) for activation, output and isolation checks. These cases are test instructions, not evidence that a host or provider test has passed.