Libraries tagged by post data

The Bolt CMS extension allows upload files via POST multipart/form-data requests

Go to Download

Modify the Query to Multiple Dates in a post For Custom Field Suite 'Loop Field'.

Go to Download

Publish future post when the publication date has passed and WordPress fails.

Go to Download

Provides a Objected-Oriented API to create, draw and manipulate barcode data using DHL (Deutsche Post) standards

Go to Download

Easily add job posting structured data to your job posts.

Go to Download

An extension that posts Magento/Adobe Commerce data to Kustomer via webhooks

Go to Download

Convert WordPress posts to markdown files through database connection

Go to Download

WordPress Database Objects - Work with posts and taxonomies, including queries and custom type registration, using OOP style.

Go to Download

Quite simple, but at the same time a simple validation class. Can validate incoming POST/GET/custom array data

Go to Download

Add a command to seed post content with blocks and dummy data

Go to Download

Provides methods for managing entities that consist two database tables: main and meta. It allows for an indiscrete set of attributes by storing them as key-value sets in the meta table, while the most important attributes and indexes are in the main table. This structure is inspired by the post/postmeta structure in Wordpress databases.

Go to Download

A wrapper for running tasks with automatic exception logging and programmable post-run actions (like flushing to the database, logging an action).

Go to Download

React Checkout Pro is a fast, modern Magento 2 one step checkout (also known as a Magento 2 one page checkout) built for Hyvä-compatible storefronts. It’s designed to reduce friction, keep shoppers focused, and improve conversion—without sacrificing the security and data integrity that production Magento stores need. React-based checkout built for speed and performance Shopify-like autosave checkout with no manual save actions Single-page, step-unlocking checkout flow Guest-friendly with optional post-purchase account creation Fast, modern UI optimized for conversion Seamless Magento 2 integration without headless complexity Extensible architecture for custom logic and integrations Compatible with Hyvä and modern Magento storefronts

Go to Download

React Checkout Pro is a fast, modern Magento 2 one step checkout (also known as a Magento 2 one page checkout) built for Hyvä-compatible storefronts. It’s designed to reduce friction, keep shoppers focused, and improve conversion—without sacrificing the security and data integrity that production Magento stores need. React-based checkout built for speed and performance Shopify-like autosave checkout with no manual save actions Single-page, step-unlocking checkout flow Guest-friendly with optional post-purchase account creation Fast, modern UI optimized for conversion Seamless Magento 2 integration without headless complexity Extensible architecture for custom logic and integrations Compatible with Hyvä and modern Magento storefronts

Go to Download

**API Version**: 1.7 **Date**: 9th July, 2024 ## 📄 Getting Started This API is based on the REST API architecture, allowing the user to easily manage their data with this resource-based approach. Every API call is established on which specific request type (GET, POST, PUT, DELETE) will be used. The API must not be abused and should be used within acceptable limits. To start using this API, you will need not create or access an existing Segnivo account to obtain your API key ([retrievable from your account settings](https://messaging.segnivo.com/account/api)). - You must use a valid API Key to send requests to the API endpoints. - The API only responds to HTTPS-secured communications. Any requests sent via HTTP return an HTTP 301 redirect to the corresponding HTTPS resources. - The API returns request responses in JSON format. When an API request returns an error, it is sent in the JSON response as an error key or with details in the message key. ### 🔖 **Need some help?** In case you have questions or need clarity with interacting with some endpoints feel free to create a support ticket on your account or you can send an email ([[email protected]](https://mailto:[email protected])) directly and we would be happy to help. --- ## Authentication As noted earlier, this API uses API keys for authentication. You can generate a Segnivo API key in the [API](https://messaging.segnivo.com/account/api) section of your account settings. You must include an API key in each request to this API with the `X-API-KEY` request header. ### Authentication error response If an API key is missing, malformed, or invalid, you will receive an HTTP 401 Unauthorized response code. ## Rate and usage limits API access rate limits apply on a per-API endpoint basis in unit time. The limit is 10k requests per hour for most endpoints and 1m requests per hour for transactional/relay email-sending endpoints. Also, depending on your plan, you may have usage limits. If you exceed either limit, your request will return an HTTP 429 Too Many Requests status code or HTTP 403 if sending credits have been exhausted. ### 503 response An HTTP `503` response from our servers may indicate there is an unexpected spike in API access traffic, while this rarely happens, we ensure the server is usually operational within the next two to five minutes. If the outage persists or you receive any other form of an HTTP `5XX` error, contact support ([[email protected]](https://mailto:[email protected])). ### Request headers To make a successful request, some or all of the following headers must be passed with the request. | **Header** | **Description** | | --- | --- | | Content-Type | Required and should be `application/json` in most cases. | | Accept | Required and should be `application/json` in most cases | | Content-Length | Required for `POST`, `PATCH`, and `PUT` requests containing a request body. The value must be the number of bytes rather than the number of characters in the request body. | | X-API-KEY | Required. Specifies the API key used for authorization. | ##### 🔖 Note with example requests and code snippets If/when you use the code snippets used as example requests, remember to calculate and add the `Content-Length` header. Some request libraries, frameworks, and tools automatically add this header for you while a few do not. Kindly check and ensure yours does or add it yourself.

Go to Download