PopoOpenPlatform Api icon

PopoOpenPlatform Api

POPO OpenPlatform API

消息卡片(旧) → 配置回调地址

AI-generated

Overview

This node interacts with the POPO OpenPlatform API, specifically supporting the resource '消息卡片(旧)' and the operation '配置回调地址'. It allows users to configure callback URLs for message cards, including setting parameters such as the request URL, token, AES encryption key, and a custom routing key. This is useful for scenarios where automated systems need to receive and handle push notifications securely from the POPO platform, such as integrating message card events into workflows or external systems.

Use Case Examples

  1. Configuring a callback URL to receive message card push notifications with optional encryption for data security.
  2. Setting a token for authentication of incoming push requests to ensure only authorized sources can send data.
  3. Defining a custom routing key to manage different callback routes for message cards.

Properties

Name Meaning
requestUrl The URL to receive push notifications, with a length limit of less than 256 characters.
token The token used to authenticate requests sent to the requestUrl, with a length limit of less than 256 characters.
aesKey Optional 32-character key used to encrypt push data for security. If set, data is pushed in encrypted format {"encrypt":"xxx"}.
configKey Custom routing key for the callback, with a length limit of less than 64 characters.

Output

JSON

  • * - Response data from the POPO OpenPlatform API after configuring the callback address.

Dependencies

  • Requires an API key credential for POPO OpenPlatform API authentication.

Troubleshooting

  • Ensure the requestUrl is a valid and reachable URL to receive push notifications.
  • Verify the token matches the expected value on the receiving server to avoid authentication failures.
  • If using aesKey, ensure it is exactly 32 characters and that the receiving system can decrypt the data properly.
  • Check for network connectivity issues or API permission errors if the configuration request fails.

Links

Discussion