Api Engineer

by postmanlabs67cff8f385d8No licenseListed Oct 8, 2026Updated Oct 8, 2026

Default entry point for API engineering work — designing, implementing, mocking, testing, monitoring, documenting, or deploying an API.

Instructions onlySoftware Development
AI-generated overview

Guides API engineering work from contract design through implementation, mocking, testing, documentation and deployment.

What it does
This skill acts as a default entry point for API engineering tasks. It lays out principles for putting the API contract first, capturing it with an OpenAPI spec or Postman collection, and validating changes against that contract. It points to related activities such as mocking, testing, documentation, discovery and CI-based deployment, and it recommends proposing next steps rather than jumping straight into implementation.
When to use it
Use it when starting or coordinating API engineering work, such as designing, implementing, mocking, testing, monitoring, documenting or deploying an API. It is suited to situations where a contract-first workflow and staged next steps are wanted.
Requirements
No scripts are shipped; it is an instructions-only skill. It references tools and practices such as Postman collections, OpenAPI specs, Postman workspace push and CI integration, but does not itself require credentials or network access.

API Engineer

Foundations

  1. Contract comes first. Establish and document the contract before starting implementation.
  2. A Postman collection and/or an OpenAPI spec is a very good option to capture the API contract - see api-documentation.
  3. Always validate the change against the contract you started with. Running a Postman collection is a very easy way to do this - see api-testing.
  4. Always propose next steps. Example: contract -> implementation -> testing -> pushing to cloud -> sharing with others.
  5. Don't jump straight into implementation. Consider whether you should first set up a mock to unblock the API consumer even before implementation is done - see api-mocking. This also helps when the user doesn't want the backend fully functional yet and just wants the responses mocked.
  6. Don't push to the cloud workspace (postman workspace push) without user consent. The recommended way to push to the cloud is a CI step on PR merge - see ci-integration.
  7. For high-quality API search results, use api-discovery.
  8. No is an acceptable answer. Asked whether to do something, invited to add scope, or shown an approach, reply with your real judgment.

Dos

  1. Prove it works - validate the task against the contract. See api-testing.
  2. Just do it - never block on the human. When tempted to ask "should I do X?" on reversible work, proceed, present the result, and let the human course-correct.
  3. Fight for good API design. See api-documentation.

Source and attribution

Source:postmanlabs/postman-plugininskills/api-engineerat commit67cff8f

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

More from postmanlabs/postman-plugin

Performance Testing

postmanlabs

Runs Postman collection load tests with virtual users, load profiles, and pass/fail thresholds.

Software DevelopmentOct 8, 2026

Flows

postmanlabs

Operate Postman Flows from the CLI: list, run, trigger, deploy, update, and debug flows and their runs.

DevOps & CloudOct 8, 2026

Ci Integration

postmanlabs

Adds Postman CLI checks as separate pass/fail gates in a CI pipeline.

DevOps & CloudOct 8, 2026

Api Testing

postmanlabs

Runs tests against an API from the command line — a single ad-hoc request, a full collection of pm.test assertions, or matching real captured app traffic against a collection contract. Use when the user asks to "test this endpoint," "run this collection," "check the API still works," or "verify my app's requests match the contract." Covers `postman request`, `postman collection run`, and `postman application test`. Depends on bootstrap when the target is a cloud collection or workspace-bound environment; a bare URL or local collection needs nothing from bootstrap.

Awaiting classificationOct 8, 2026

Api Monitoring

postmanlabs

Creates, schedules, and manages Postman Monitors — recurring checks against a live API — triggers ad hoc runs, inspects job/run history to diagnose failures, and hosts self-hosted execution runners for monitors on a private network. Use when the user asks to "set up a monitor," "run this monitor now," "check monitor results," "pause/resume a monitor," or "set up a runner for our internal APIs." Covers `postman monitor` (create, update, delete, list, get, pause, resume, run, jobs, runs) and `postman runner` (start, list, regions).

Awaiting classificationOct 8, 2026

Api Mocking

postmanlabs

Creates and runs fake API backends locally or in the cloud, with scenario and status-code overrides for testing.

Software DevelopmentOct 8, 2026