WordPress
WordPress is a popular content management system (CMS) that powers millions of websites. The WordPress REST API enables developers to interact with WordPress sites remotely, allowing you to retrieve posts, pages, comments, and other content. The WordPress connector enables you to access WordPress REST API endpoints to extract content, retrieve posts and pages, and integrate WordPress data with other systems. This connector is particularly useful for applications that need to extract blog content, integrate WordPress with analytics systems, build content aggregation solutions, or automate content management workflows.
Power end-to-end data operations for your WordPress API with Nexla. Our bi-directional WordPress connector is purpose-built for WordPress, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to WordPress or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your WordPress workflows fast, secure, and fully governed.
Features
Type: API
- Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
- Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
- API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
- Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
Prerequisites
Before creating a WordPress credential, you'll need to obtain authentication credentials from your WordPress site. WordPress REST API supports multiple authentication methods, including Basic Authentication with Application Passwords (recommended) or no authentication for public endpoints.
To obtain WordPress API credentials:
-
Log in to your WordPress admin dashboard. Navigate to your WordPress site's admin panel (typically at
https://yoursite.com/wp-admin). -
For Basic Authentication with Application Passwords (recommended for secure access):
- Navigate to Users > Profile or Users > All Users and select your user account.
- Scroll down to the Application Passwords section.
- Enter a name for the application password (e.g., "Nexla Integration").
- Click Add New Application Password.
- Copy the generated application password immediately, as it will only be displayed once. This is a 24-character password that you'll use along with your username.
-
Note your WordPress Site URL. This is the full URL to your WordPress site, including the protocol (https://), such as
https://yoursite.com. -
Note your WordPress Username. This is the username you use to log in to your WordPress admin dashboard.
-
Note your WordPress API Version. The default API version is typically
v2, but this may vary depending on your WordPress version. The WordPress REST API is available at/wp-json/wp/{version}/.
WordPress REST API supports multiple authentication methods. For secure access to protected endpoints, use Basic Authentication with Application Passwords. Application Passwords are more secure than regular passwords and can be revoked individually. For public endpoints (like reading public posts), you may not need authentication. However, for most operations, Basic Authentication with Application Passwords is recommended.
For detailed information about WordPress REST API authentication and Application Passwords, refer to the WordPress REST API Handbook and WordPress Application Passwords Documentation.
Authenticate
Credentials required
- Basic Authentication
- No Authentication
WordPress Basic Authentication via Application Passwords
| Field | Required | Secret | Description |
|---|---|---|---|
| WordPress Site URL | Yes | No | Full URL to your WordPress site. |
| Username | Yes | No | The username you use to login on your Wordpress Site. |
| Password | Yes | Yes | The password you use to login on your Wordpress Site. |
| Version | Yes | No | The Version of Wordpress API. |
No Authentication only for reading publicly posts/pages.
| Field | Required | Secret | Description |
|---|---|---|---|
| WordPress Site URL | Yes | No | Full URL to your WordPress site. |
| Version | Yes | No | The Version of Wordpress API. |
Create a credential in Nexla
- After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
New Credential Overlay – WordPress

-
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
-
In the WordPress Site URL field, enter the full URL to your WordPress site, including the protocol (https://). For example,
https://yoursite.com. Do not include a trailing slash. -
If using Basic Authentication (recommended for secure access):
- In the Username field, enter your WordPress username. This is the username you use to log in to your WordPress admin dashboard.
- In the Password field, enter your WordPress Application Password (not your regular WordPress password). This is the 24-character application password you generated in your WordPress user profile.
-
In the Version field, enter the WordPress API version. The default value is
v2, which is the standard version for WordPress REST API.If you're using Basic Authentication, use an Application Password (not your regular WordPress password) for security. Application Passwords can be revoked individually and are more secure for API access. If you're only accessing public endpoints, you may not need authentication, but Basic Authentication is recommended for most operations.
-
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.
Use as a data source
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the WordPress connector tile, then select the credential that will be used to connect to the WordPress API, and click Next; or, create a new WordPress credential for use in this flow.
Endpoint templates
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common WordPress REST API endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Manual configuration
WordPress data sources can also be manually configured to ingest data from any valid WordPress REST API endpoint, including endpoints not covered by the pre-built templates, custom post types, or custom query parameters. WordPress REST API endpoints typically follow the pattern {site_url}/wp-json/wp/{api_version}/{resource}, where {site_url} is your WordPress site URL and {api_version} is typically v2. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
For WordPress REST API responses, common paths to data include $ for the entire response array (which contains posts or pages), or $[*] for all array elements. The Authorization header for Basic Authentication is automatically included from your credential if configured, so you do not need to add it manually as a request header.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new WordPress data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.