Condixia – REST Gateway
| 开发者 | |
|---|---|
| 更新时间 | 2026年9月28日 23:35 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
Condixia – REST Gateway provides authenticated and controlled REST access to WordPress content and selected WooCommerce data for external applications.
It is designed for developers building applications such as Laravel dashboards, headless frontends, mobile applications, internal tools, reporting systems, and SaaS integrations that use WordPress as a backend.
Condixia uses its own API client and credential system. External applications do not need WordPress user passwords, login cookies, Application Passwords, WooCommerce consumer keys, JWT plugins, or OAuth plugins.
Core Features
- Secure Condixia API clients and Bearer credentials.
- API credentials are stored as hashes rather than reusable plaintext secrets.
- API secrets are displayed only when initially created.
- Per-client scopes and permissions.
- Credential expiration, disabling, and revocation.
- Versioned REST namespace using
condixia/v1. - Read access to posts, pages, and supported public custom post types.
- Explicitly controlled create and update access for supported WordPress content.
- Write operations are disabled by default per resource.
- Read-only WooCommerce product access.
- Read-only WooCommerce order access.
- WooCommerce HPOS-compatible order access using supported WooCommerce APIs.
- Pagination, searching, filtering, sorting, and field selection where supported.
- Basic per-client rate protection.
- Resource schemas that prevent unrestricted field and metadata exposure.
- Endpoints documentation inside WordPress Admin.
- API client management inside WordPress Admin.
- No DELETE operations in the Free edition.
Authorization: Bearer cxi_v1_<client-id>.<secret>
The plaintext secret is shown only when the API client is created.
Store API credentials securely in your external application.
Production API requests should use HTTPS.
Example Request
Retrieve WordPress posts:
GET /wp-json/condixia/v1/resources/posts
Example cURL request:
curl -H "Authorization: Bearer <your-api-key>" "https://example.com/wp-json/condixia/v1/resources/posts"
Retrieve a specific post:
GET /wp-json/condixia/v1/resources/posts/123
Retrieve WooCommerce products:
GET /wp-json/condixia/v1/resources/products
Retrieve WooCommerce orders:
GET /wp-json/condixia/v1/resources/orders
Available resources depend on the active WordPress post types, installed plugins, WooCommerce availability, resource configuration, and the API client's assigned scopes.
安装:
- Upload the
condixia-wp-rest-gatewaydirectory to/wp-content/plugins/, or install the plugin through the WordPress Plugins screen. - Activate Condixia – REST Gateway.
- Open Condixia REST > API Keys.
- Create an API client.
- Assign only the scopes required by the external application.
- Copy the generated API credential immediately. It cannot be retrieved again.
- Open Condixia REST > Endpoints to inspect available resources and routes.
- If WordPress content writes are required, explicitly enable the appropriate resources under Condixia REST > Settings.
常见问题:
Does Condixia require a WordPress user account for API authentication?
No. Condixia API clients authenticate independently from WordPress user accounts.
Does it use WordPress Application Passwords?
No. Condixia has its own API credential system.
Does it require JWT or OAuth?
No. The Free edition uses secure opaque Bearer credentials.
Are API secrets stored in plaintext?
No. Reusable API secrets are stored as secure hashes. The original credential is displayed only when it is created.
Can an API client access everything after authentication?
No. Authentication and authorization are separate. Each client must have the required scope for the requested resource or operation.
Does Condixia expose all post metadata?
No. Resources use explicit schemas and do not expose arbitrary metadata by default.
Can external applications create and update WordPress content?
Yes, for supported WordPress content resources when write access has been explicitly enabled and the API client has the required create or update scope.
Are write operations enabled automatically?
No. WordPress resource writes are disabled by default.
Can the API delete WordPress content?
No. DELETE operations are not included in the initial Free edition.
Does Condixia support WooCommerce?
Yes. When WooCommerce is active, Condixia provides read-only product and order resources.
Can the API modify WooCommerce orders?
No. WooCommerce access in the Free edition is read-only.
Does it support WooCommerce HPOS?
Yes. WooCommerce orders are accessed using WooCommerce CRUD and query APIs rather than assuming orders are stored as WordPress posts.
Does Condixia send usage information to Condixia?
No hidden telemetry is included.
更新日志:
0.1.0
- Initial development release.
- Added Condixia API client authentication.
- Added hashed API credential storage.
- Added API scopes and authorization.
- Added WordPress resource discovery.
- Added authenticated REST resource reads.
- Added controlled WordPress create and update operations.
- Added read-only WooCommerce product and order resources.
- Added WooCommerce HPOS compatibility.
- Added basic per-client rate protection.
- Added Dashboard, Endpoints, API Keys, and Settings administration screens.
- Added public resource and provider extension contracts.