Download the PHP package bhaveshsoni26/laravel-postman-sync without Composer

Laravel Postman Sync

Turn your Laravel API routes into a complete, importable Postman Collection — docs, examples, tests, environments, and one-command push — with zero manual annotations.

📖 Documentation  ·  Packagist  ·  Issues

That's it. The package scans every API route, reads your controllers and FormRequest classes, and writes a Postman Collection v2.1 (with embedded docs and test scripts), per-stage environment files, and an OpenAPI document — then, with --push, syncs it straight to your Postman workspace.

📖 Full documentation, guides and examples: postman-sync.bhaveshdev.in

Why

Keeping a Postman collection in step with a growing API is tedious and always out of date. This package makes the collection a build artifact: re-run one command and your routes, request bodies, auth, examples, docs, and tests regenerate deterministically. Add 10 new endpoints and --push appends just those — without clobbering the manual edits your team made in Postman.

Features

• 🔎 Automatic route scanning — every GET/POST/PUT/PATCH/DELETE, apiResource, and resource; derives version, group, controller, and middleware.
• 🧬 Reflection-based analysis — finds each controller's FormRequest and reads its rules(); no annotations required.
• 🧾 Typed request bodies + examples — required|email|min:8|in:…|confirmed|nullable|file… mapped to types and realistic example values, including nested/wildcard keys.
• 🔐 Auth detection — auth:<guard> → Bearer {{guard_token}}; collection-level auth with per-request overrides; public routes set noauth.
• 📦 Postman Collection v2.1 — folder-grouped, fully variable-driven ({{base_url}}, :id path vars) — no hardcoded hosts or secrets.
• 📚 Docs in Postman — endpoint summary, field table, and example responses embedded in each request's Docs tab (plus folder/collection descriptions).
• 🧪 Generated test scripts — status / response-time / JSON assertions, login-token capture into the environment, and validation/CRUD stubs.
• 🌱 Environment files — one per stage (local/staging/production) with secret-typed guard tokens.
• 📜 OpenAPI 3.0.3 — openapi.json generated alongside.
• 🚀 One-command push — --push uploads to the Postman API with incremental merge (append new, regenerate changed, preserve unchanged + manual edits) or --fresh full replace.
• 🛟 Never breaks your build — closures, missing FormRequests, and bad controllers degrade gracefully with warnings; exits 0.

Requirements

Installation

The service provider auto-registers via package discovery. Publish the config:

Not on Packagist yet? Install from a local path repository — see INSTALLATION.md for the one-time repositories setup.

Quick start

Import storage/app/postman/collection.json and an environment file into Postman, fill in the token variables, and send.

What it generates

Command reference

Push to Postman

Incremental merge appends new routes, regenerates changed ones, and leaves unchanged requests — including manual edits to their docs/tests — untouched. Use --fresh to overwrite the whole collection.

Getting your Postman credentials

You only need the API key to push. The collection ID and workspace ID are optional (see notes below).

1. API key — POSTMAN_API_KEY (required)

1. Sign in to Postman and open go.postman.co/settings/me/api-keys (or: click your avatar, top-right → Settings → API keys).
2. Click Generate API Key, give it a name (e.g. laravel-postman-sync), and Generate.

3. Copy the key — it starts with PMAK- — and put it in .env:

   Treat it like a password. You can only see it once; regenerate if you lose it.

2. Collection ID — POSTMAN_COLLECTION_ID (optional)

Leave this empty the first time — --push creates a new collection and prints its ID:

Copy that ID into .env so future pushes update the same collection instead of creating duplicates:

To target a collection that already exists, fetch its exact API uid (not the short id shown in the app) — list them with your key:

Use the uid value from the response (looks like 12345678-...).

3. Workspace ID — POSTMAN_WORKSPACE_ID (optional)

Only used when creating a new collection, to place it in a specific workspace. Omit it to use your default workspace.

• From the app: open the workspace, then look at the browser URL: https://go.postman.co/workspace/My-Team~<workspace-id>/... — the ID is the part after the ~.
• Via the API: list your workspaces and copy the id:

After editing .env, run php artisan config:clear so Laravel picks up the new values, then php artisan postman:sync --push.

Configuration

Key options in config/postman-sync.php:

Full configuration reference and a multi-guard (CRM-style) example are in INSTALLATION.md.

How it works

A one-directional pipeline of immutable DTOs; each stage is interface-backed and independently tested.

Testing

All Postman API calls go through Laravel's Http facade and are mocked with Http::fake() — the test suite needs no real API key or network.

Contributing

Issues and PRs welcome. Please run composer test && composer stan && composer lint before submitting. New code uses declare(strict_types=1) and Sorbet-style full type hints; tests are written in Pest.

License

MIT.