hopheartsceo/laravel-postman-exporter
Composer 安装命令:
composer require hopheartsceo/laravel-postman-exporter
包简介
Automatically generate Postman v2.1 collections from your Laravel application routes, controllers, and FormRequest validations.
README 文档
README
Automatically generate Postman Collection v2.1 files and OpenAPI 3.0 specifications from your Laravel application routes, controllers, and FormRequest validations — complete with hierarchical folder grouping and response examples.
✨ Features
- 🔍 Route Scanning — Automatically reads all registered API routes
- 📝 Request Analysis — Extracts validation rules from FormRequest classes and inline
$request->validate()calls - 🎯 Smart Example Data — Generates realistic sample values based on validation rules and field names
- 🔐 Authentication Detection — Automatically adds auth headers based on middleware (Sanctum, Passport, etc.)
- 📁 Hierarchical Grouping — Organizes requests into nested folders based on route prefixes
- 📋 Response Examples — Extracts response structures from PHPDoc, API Resources,
response()->json(), and Eloquent models - 📄 OpenAPI Support — Export your API as a valid OpenAPI 3.0.3 specification
- 🚀 Postman Upload — Optionally upload collections directly via the Postman API
- ⚡ Artisan Command — Beautiful CLI with progress indicators and colored output
📦 Installation
You can install the package via composer:
composer require hopheartsceo/laravel-postman-exporter --dev
Installation from GitHub (Development)
If you haven't published to Packagist yet, add this to your composer.json:
"repositories": [ { "type": "vcs", "url": "https://github.com/hopheartsceo/laravel-postman-exporter" } ], "require": { "hopheartsceo/laravel-postman-exporter": "dev-main" }
Publish the configuration file:
php artisan vendor:publish --tag=postman-exporter-config
🚀 Usage
Artisan Command
# Export as Postman Collection (default) php artisan postman:export # Export as OpenAPI 3.0 specification php artisan postman:export --format=openapi # Custom output path php artisan postman:export --output=./docs/api-spec.json # Group routes by prefix (works for both formats) php artisan postman:export --group-by-prefix # Include response examples (Postman only currently) php artisan postman:export --with-responses
Facade API
use Hopheartsceo\PostmanExporter\Facades\PostmanExporter; // Generate Postman Collection (default) $collection = PostmanExporter::generate(); // Generate OpenAPI spec $openapi = PostmanExporter::generate('openapi'); // Generate and save to file $path = PostmanExporter::save('/path/to/collection.json'); // Generate and upload to Postman $result = PostmanExporter::upload('your-api-key');
⚙️ Configuration
After publishing, edit config/postman-exporter.php:
| Option | Type | Default | Description |
|---|---|---|---|
base_url |
string | env('APP_URL') |
Base URL for all requests |
default_headers |
array | Accept + Content-Type JSON | Default headers on every request |
output_path |
string | storage/app/postman-collection.json |
Default output path |
collection_name |
string | App name + " API Collection" | Name of the Postman collection |
grouping |
array | (see below) | Folder grouping configuration |
responses |
array | (see below) | Response examples configuration |
include_web_routes |
bool | false |
Include non-API routes |
postman_api_key |
string | '' |
Postman API key for uploads |
enable_upload |
bool | false |
Auto-upload after generation |
Folder Grouping
Routes are grouped into flat, single-level folders by the first segment of the URI. No nesting is created — every route belongs to exactly one top-level folder.
'grouping' => [ 'enabled' => true, 'strategy' => 'prefix', // Only 'prefix' strategy supported 'fallback_folder' => 'general', // Folder for unprefixed / root routes ],
How it works:
| URI | Folder |
|---|---|
api/users |
api |
api/users/{id} |
api |
auth/login |
auth |
auth/logout |
auth |
status |
general (fallback) |
/{id} |
general (fallback) |
- The first segment of the URI (
explode('/', $uri)[0]) becomes the folder name. - Routes whose first segment is empty or a parameter (e.g.
{id}) go to the fallback folder. - There are no root-level requests — every request lives inside a folder.
- There are no nested folders — the structure is always flat.
Response Examples
Response examples are extracted automatically from your controller methods and attached to each Postman request item.
'responses' => [ 'enabled' => true, 'fallback_status' => 200, 'fallback_body' => ['message' => 'Success'], ],
Or enable at export time with the --with-responses flag:
php artisan postman:export --with-responses
Extraction priority (highest to lowest):
-
PHPDoc
@response— Parses@responsetags with optional status codes:/** * @response 200 {"id": 1, "name": "John Doe"} * @response {"data": []} */ public function index() { ... }
-
API Resource — Detects
return new UserResource(...)patterns and reads the Resource's$fillable/$visiblefields. -
response()->json()— Parses inlineresponse()->json([...], 200)calls to extract the body and status code. -
Eloquent Model — Detects
return User::find(...)patterns and generates example data from the model's$fillablefields. -
Fallback — Uses the configured
fallback_statusandfallback_body.
Generated response format in Postman:
{
"response": [
{
"name": "Success Response",
"originalRequest": { "method": "GET", "url": { ... } },
"status": "OK",
"code": 200,
"_postman_previewlanguage": "json",
"header": [
{ "key": "Content-Type", "value": "application/json" }
],
"body": "{\"id\": 1, \"name\": \"John Doe\"}"
}
]
}
Route Filters
'route_filters' => [ 'include_prefixes' => [], // Only include these prefixes 'exclude_prefixes' => ['_ignition'], // Exclude these prefixes 'include_middleware' => [], // Only include routes with these middleware 'exclude_middleware' => [], // Exclude routes with these middleware ],
Middleware to Headers Map
'middleware_to_headers_map' => [ 'auth:sanctum' => [ 'Authorization' => 'Bearer {{token}}', ], 'auth:api' => [ 'Authorization' => 'Bearer {{token}}', ], ],
📄 Example Output
The generated collection follows the Postman Collection v2.1 schema. Folders are flat (single-level) and each request includes response examples:
{
"info": {
"name": "My App API Collection",
"schema": "https://schema.getpostman.com/json/collection/v2.1.0/collection.json"
},
"item": [
{
"name": "api",
"item": [
{
"name": "users.index",
"request": {
"method": "GET",
"url": {
"raw": "{{base_url}}/api/users",
"host": ["{{base_url}}"],
"path": ["api", "users"]
},
"header": [
{ "key": "Accept", "value": "application/json" },
{ "key": "Authorization", "value": "Bearer {{token}}" }
]
},
"response": [
{
"name": "Success Response",
"originalRequest": {
"method": "GET",
"url": {
"raw": "{{base_url}}/api/users",
"host": ["{{base_url}}"],
"path": ["api", "users"]
}
},
"status": "OK",
"code": 200,
"_postman_previewlanguage": "json",
"header": [
{ "key": "Content-Type", "value": "application/json" }
],
"body": "{\"data\": [{\"id\": 1, \"name\": \"John Doe\"}]}"
}
]
}
],
"description": "Routes for api"
},
{
"name": "general",
"item": [
{
"name": "GET Status",
"request": {
"method": "GET",
"url": {
"raw": "{{base_url}}/status",
"host": ["{{base_url}}"],
"path": ["status"]
}
},
"response": [
{
"name": "Success Response",
"originalRequest": {
"method": "GET",
"url": {
"raw": "{{base_url}}/status",
"host": ["{{base_url}}"],
"path": ["status"]
}
},
"status": "OK",
"code": 200,
"_postman_previewlanguage": "json",
"header": [
{ "key": "Content-Type", "value": "application/json" }
],
"body": "{\"message\": \"Success\"}"
}
]
}
],
"description": "Routes for general"
}
],
"variable": [
{ "key": "base_url", "value": "http://localhost" },
{ "key": "token", "value": "your-auth-token-here" }
]
}
See
examples/sample-collection.jsonfor a full example with multiple folders and response examples.
🧪 Testing
composer test # or vendor/bin/phpunit
🏗️ Architecture
| Service | Responsibility |
|---|---|
RouteScannerService |
Scans Laravel routes via the Router; extracts return types, PHPDoc, and API Resource usage |
RequestAnalyzerService |
Extracts FormRequest/inline validation rules |
ValidationParserService |
Parses validation rules into structured format |
ExampleDataGeneratorService |
Generates realistic sample values |
FolderOrganizerService |
Groups routes into flat, single-level folders by first URI segment |
ResponseExtractorService |
Analyzes controller methods to extract response structures (PHPDoc → API Resource → JSON → Model → Fallback) |
ExampleResponseGeneratorService |
Converts extracted response data into Postman-formatted response arrays |
PostmanCollectionBuilderService |
Builds Postman v2.1 JSON structure with folders and response examples |
PostmanUploaderService |
Uploads collections to Postman API |
📋 Requirements
- PHP 8.1+
- Laravel 10, 11, or 12
📝 License
MIT License. See LICENSE for details.
hopheartsceo/laravel-postman-exporter 适用场景与选型建议
hopheartsceo/laravel-postman-exporter 是一款 基于 PHP 开发的 Composer 扩展包,目前已累计 28 次下载、GitHub Stars 达 2, 最近一次更新时间为 2026 年 03 月 08 日, 在 PHP 生态内属于活跃度较高的组件。
它主要适用于以下技术方向: 「generator」 「api」 「routes」 「laravel」 「collection」 「exporter」 等业务场景。在实际项目中,围绕这些方向常见需要落地的问题包括:接口对接、性能调优、并发安全、与既有框架(Laravel / ThinkPHP / Yii / Webman 等)的兼容适配,以及生产环境的日志埋点与稳定性保障。
我们在过去多个企业项目中使用过 hopheartsceo/laravel-postman-exporter 或与其功能相近的方案,如果你在选型或落地过程中遇到问题,例如 版本兼容、二次改造、私有化封装、与内部系统对接、生产 BUG 排查,欢迎联系我们协助评估。
基于 hopheartsceo/laravel-postman-exporter 在你已有业务上做功能扩展、字段裁剪、UI 适配、与内部账号 / 权限 / 日志系统的深度对接。
线上偶发问题、内存泄漏、慢查询、并发异常等排查修复;针对高流量场景做缓存、队列、索引层面的调优。
承接完整的项目从需求 → 设计 → 开发 → 上线 → 长期运维;也可按月提供技术保姆服务。
与 hopheartsceo/laravel-postman-exporter 相关的其它包
同方向 / 同关键字的高下载量 PHP Composer 包推荐,方便对比选型:
Memio's PrettyPrinter, used to generate PHP code from given Model
Generates a Blade directive exporting all of your named Laravel routes. Also provides a nice route() helper function in JavaScript.
Block routes by IP
Provides caching methods which can be easily used for caching routes.
A PSR-7 compatible library for making CRUD API endpoints
End-to-end type-safe APIs for Laravel. Like tRPC, but for Laravel + TypeScript.
统计信息
- 总下载量: 28
- 月度下载量: 0
- 日度下载量: 0
- 收藏数: 3
- 点击次数: 35
- 依赖项目数: 0
- 推荐数: 0
其他信息
- 授权协议: MIT
- 更新时间: 2026-03-08