How can we help you?

API keys

Open Settings > Developers > API keys with Developers permission. Creation also depends on your plan including API keys.

1. Click Create key and give it a recognizable name of up to 50 characters.
2. Save and use Copy on the corresponding entry when you need to configure your integration.
3. Keep the key private. Although the list displays it masked, the button copies the complete key.

To remove access, select Revoke and confirm. Applications using that key will lose access; check dependencies first. The key is not presented as visible only once, and granular per-key permissions are not offered here.

Webhooks

In Settings > Developers > Webhooks, you need Developers permission and the webhooks capability to create or edit entries.

1. Add a name and the authorized receiver's HTTPS URL, without a username or password embedded in it.
2. Select at least one event from the list.
3. Review Active: it is initially checked for a new entry. Decide whether it should remain active before saving.
4. Generate a test event and view that webhook's logs.

You can edit events and status, or delete an entry with confirmation. If an existing configuration contains events the editor does not recognize, they are preserved; do not assume that unchecking every visible option removes every saved event.

The paginated logs show date, event, response status, sent body and the receiver's response. Review these details to diagnose deliveries, and avoid copying them to public locations: they may contain contact information.

This guide describes FROGED's controls. Receiver implementation must follow the official technical reference for format, authentication and security; do not infer guarantees about ordering, retries or exactly-once delivery from the logs.