Issue2Web is a product of Ambition4Clients B.V. WordPress does not process the PDF itself. The plugin connects the site, sends the file plus publication settings to Issue2Web, shows status and then creates posts and media.
For more information, visit https://issue2web.com
Source strings are English. Translations are managed through translate.wordpress.org after the plugin is published on WordPress.org.
Settings sent to Issue2Web
- Post type (posts, pages or an existing public custom post type)
- Preview width
- Publication spread in days (0 = keep as draft)
- Publication time
- Maximum image width and format (JPG / PNG / WEBP)
- Number of existing/new tags and categories
- Number of SEO keywords and maximum meta title/keyphrase length
- Detected SEO plugin (Yoast, Rank Math, AIOSEO, SEOPress, The SEO Framework)
Connect
- Issue2Web Settings enter the API endpoint (HTTPS)
- Connect to Issue2Web
- Authorise in Issue2Web
- The plugin exchanges the one-time code server-to-server for site credentials
Laravel contract
Connect: GET {app}/pdf2cms/connect?site_url=&redirect_uri=&state=. Return query: code, state. Exchange: POST {app}/api/v1/site-connections/exchange (JSON: code, site_url) access_token, webhook_secret, site_id. Import: POST {app}/api/v1/imports (multipart: file, callback_url, edition_number, settings JSON). Status: GET {app}/api/v1/imports/{uuid}. Callback: POST /wp-json/issue2web/v1/imports/result with HMAC headers.