Libraries tagged by user content

Provides the ability for anonymous (not logged in) users to comment on public content and for that content to be moderated by the owner.

Go to Download

Allows users to create folders and content trees

Go to Download

Extension loads content only if the user agrees.

Go to Download

RedKiteCms is an Open Source Content Management System Application, built on top of Symfony2 components and TwitterBootstrap frameworks, providing an easy an intuitive user-interface, to improve the website's content management experience

Go to Download

This BadgeOS Add-on adds a shortcode to show or hide content depending on if the user has earned a specific achievement.

Go to Download

User interface to manage a website's content

Go to Download

This package provides a simple and effective way to lock an application behind a password, ensuring that unauthorized users cannot access any routes or content without first entering the correct password.

Go to Download

Provides a number of methods of getting rss feeds of non-public content as a logged in user

Go to Download

Allows users to comment on and discuss published content.

Go to Download

Shariff-Plus enables website users to share and like their favorite content without compromising their privacy.

Go to Download

Open Source Content Management. Yanzicms is the mobile-ready and user-friendly way to build your website.

Go to Download

Lets users select a responsive style OR a image style to place images in the content.

Go to Download

Builds a profile of a site user in their browser, to be used for content personalisation

Go to Download

This package contains APIs used to fetch and update content posted from the backend to the user interface

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