sflwa

This plugin enhances Gravity Forms by providing the ability to export individual form entries as a <code>.json</code> file directly from the entries list. It allows you to define a custom JSON structure using a template editor within each form’s settings, where you can insert Gravity Forms merge tags and even utilize conditional logic shortcodes. A live preview feature helps you validate your JSON template before export.
<h3>Instructions</h3>
<ol>
<li>Activate the plugin.</li>
<li>Go to Forms > Forms, then select ‘Settings’ for the desired form.</li>
<li>Click on the ‘JSON Export’ tab.</li>
<li>Enable JSON Export Link: Check the box to display the “Download JSON Export” link on individual entry pages for this form.</li>
<li>Custom JSON Output Template: Enter your desired JSON structure in the textarea.
<ul>
<li>Use standard Gravity Forms merge tags (e.g., <code>{field_id}</code>, <code>{entry_id}</code>, <code>{date_created:format:Y-m-d}</code>).</li>
<li>Merge tags will be automatically formatted as <code>"key":"{merge_tag}"</code> when inserted from the dropdown.</li>
<li>You can also use Gravity Forms conditional shortcodes (e.g., <code>[gravityforms action='conditional' merge_tag='{Name (First):1.3}' condition='isnot' value='Philip']"custom_field":"conditional_value"[/gravityforms]</code>) to include dynamic content.</li>
</ul>
</li>
<li>Preview JSON Export: Click the ‘Preview JSON Export’ button to see a live preview of your generated JSON based on the latest entry for that form. This helps in validating your template.</li>
<li>Save Settings: Click ‘Save Settings’ to apply your changes.</li>
<li>To export an entry, go to Forms > Entries, hover over an entry, and click the ‘Download JSON Export’ link.</li>
</ol>

Custom JSON Export for Gravity Forms

A plugin to export individual Gravity Forms entries to a customizable JSON file.

Daniel Bachhuber

Ryan McCue

Joe Hoyle

Jonny Harris

Rachel Baker

This plugin uses the OAuth 1.0a protocol to allow delegated authorization; that is, to allow applications to access a site using a set of secondary credentials. This allows server administrators to control which applications can access the site, as well as allowing users to control which applications have access to their data.
This plugin only supports WordPress >= 4.4.
The latest stable version is also available from the <a href="https://wordpress.org/plugins/rest-api-oauth1/" rel="ugc">WordPress Plugin Directory</a>.
<h3>New to OAuth</h3>
We strongly recommend you use an existing OAuth library. You’ll be best off if you understand the authorization process, but leave the actual implementation to well-tested libraries, as there are a lot of edge cases.
Start reading from <a href="docs/introduction/README.md" rel="nofollow ugc">the Introduction</a> to get started!
<h3>For OAuth Veterans</h3>
If you already know how to use OAuth, here’s the lowdown:
<ul>
<li>The plugin uses OAuth 1.0a in</li>
<li>We use the three-legged flow</li>
<li>To find the REST API index, apply the <a href="http://v2.wp-api.org/guide/discovery/" rel="nofollow ugc">API autodiscovery process</a></li>
<li>The endpoints for the OAuth process are available in the REST API index: check for <code>$.authentication.oauth1</code> in the index data.
<ul>
<li>The temporary credentials (request token) endpoint is <code>$.authentication.oauth1.request</code> (typically <code>/oauth1/request</code>)</li>
<li>The authorization endpoint is <code>$.authentication.oauth1.authorize</code> (typically <code>/oauth1/authorize</code>)</li>
<li>The token exchange (access token) endpoint is <code>$.authentication.oauth1.access</code> (typically <code>/oauth1/access</code>)</li>
</ul>
</li>
<li>Your callback URL must match the registered callback URL for the application in the scheme, authority (user/password) host, port, and path sections. (Subpaths are not allowed.)</li>
<li>The only signature method supported is HMAC-SHA1.</li>
<li>OAuth parameters are supported in the Authorization header, query (GET) parameters, or request body (POST) parameters (if encoded as <code>application/x-www-form-urlencoded</code>). OAuth parameters are not supported in JSON data.</li>
</ul>

WP REST API – OAuth 1.0a Server

Hello, I have made an adapter for Parse Server under Node.js with which you can link the login of any installation of wordpress in Parse Server, for that I have used your plugin, which is the one that gives us access_token and allows us to verify the authenticity Of the user registered in the server.

https://github.com/enriquecerda/parse-server-wordpress-login

Links with Parse-server Node.js

Got this working after some good amount of work! Thanks for bringing this and making API calls secure.

Worked like a charm!

Really Useful And Good Plugin
But Please
1- Reply on The Support Forum
2- Update it To Work Good With Last WordPress Verison
3 – No Clear Docs
4 - not work with localhost

Good But

Connect applications to your WordPress site without ever giving away your password.

Custom JSON Export for Gravity Forms vs WP REST API – OAuth 1.0a Server