This message queue service simplifies message management with an intuitive API. Users can easily create messages and track their lifecycle with timestamps for both creation and last access. The service also offers optional callback URLs that trigger automatically upon successful message creation, ensuring a seamless and efficient way to manage, retrieve, and respond to messages.
To read a queue entry using a specific token and optional callback URL
curl -X POST https://mqueue.reverse.rocks/api/read/ \
-H "Content-Type: application/json" \
-d '{"token": "queue_token", "callback_url": "http://example.com/callback"}'
Return Queue message and status of the callback
{
"callback_status":"success",
"generation_date": "YYYY-MM-DD HH:MM:SS",
"last_access": "YYYY-MM-DD HH:MM:SS",
"message": "your-queue-message-here",
"revision": 1,
"token": "your-token-here",
}
FAQ
Q: How do I retrieve a message from the queue?
A: To retrieve a message, send a POST request to the read endpoint with the required token in the request body. The service will return the stored message, along with metadata such as the generation date, last access time, and revision number.
Q: Is there a limit on how often I can read from a queue?
A: Yes, there is a rate limit in place to prevent abuse. You can only read from a queue 5 times per minute per client IP. This is enforced to ensure fair use of the service.
Q: Can I trigger an action after successfully reading from the queue?
A: Yes, you can provide a callback_url in your request. If the read operation is successful, the service will send the queue's token to the callback URL.
Q: What happens to the last access time when I read from a queue?
A: The last_access timestamp is updated each time you read from the queue, reflecting the most recent access.
Q: Is the queue protected?
A: Yes, the queue is protected in terms of data access. The service does not read or analyze the content of the messages inside the queue; it only handles metadata such as timestamps. For additional security, we recommend encrypting your data before sending it to the queue. This ensures that even if someone gains access to the queue, they cannot read or interpret the contents without the decryption key.
To generate a new queue entry with a payload and optional callback URL.
curl -X POST https://mqueue.reverse.rocks/api/generate/ \
-H "Content-Type: application/json" \
-d '{"message": "This is a test message.", "callback_url": "http://example.com/callback"}'
Return Queue token and status of the callback
{
"token": "generated_token",
"callback_status": "success" or "error"
}
Overwrite Queue with Token
curl -X POST https://mqueue.reverse.rocks/api/generate/ \
-H "Content-Type: application/json" \
-d '{"message": "updated message.", "callback_url": "http://example.com/callback", "token": "queue_token"}'
FAQ
Q: What does the Generate endpoint do?
A: The Generate endpoint creates a new message entry in the queue with a specified payload. It returns a unique token for this entry and can trigger a callback URL if provided.
Q: How do I handle the token returned by the Generate endpoint?
A: The token returned in the response is used to identify the message entry. You should store this token securely as it will be needed to reference or update the message later.
Q: What is the message limit?
A: The message limit is 250 characters per message for the free version. If you need more, consult with RudeNet for customized solutions that fit your needs.
Q: Is the queue protected?
A: Yes, the queue is protected in terms of data access. The service does not read or analyze the content of the messages inside the queue; it only handles metadata such as timestamps. For additional security, we recommend encrypting your data before sending it to the queue. This ensures that even if someone gains access to the queue, they cannot read or interpret the contents without the decryption key.
Q: How long does the queue exist?
A: The queue is automatically deleted if it has not been accessed for the last 24 hours. This helps manage storage and ensures that obsolete data does not remain in the system.
Business Support
For businesses requiring advanced queue management solutions to synchronize applications and processing, our service offers scalable options tailored to meet complex needs. You can benefit from:
- Larger Queue Capacities: Create and manage extensive queues to handle high volumes of messages efficiently.
- No Limitations on Queue Creation: Generate multiple queues without constraints on message sizes or time access limits.
- Large-Scale Broadcasting: Implement robust broadcasting features to disseminate messages across multiple systems or applications seamlessly.
For more information and to discuss how our solutions can be customized for your business needs, contact RudeNet for personalized support and advanced configurations.
